GIS Operations & Maintenance Manual (MAN-0001)
This information was originally published as MAN-0001, GIS Operations and Maintenance Manual.
DANGER
Failure to follow the procedures detailed in this manual can result in death or serious injury.
Only authorized persons may perform the procedures detailed in this manual.
NOTICE
Failure to follow the procedures detailed in this manual can result in damage to equipment.
Only authorized persons may perform the procedures detailed in this manual.
- 1 Introduction
- 2 Overview
- 3 Emergency Stop System
- 4 Trapped Key System
- 5 Human Machine Interface (HMI)
- 6 Procedures
- 7 Normal Operations
- 8 Emergency Operations
- 9 Connecting a Computer
- 10 Repair
- 11 8 Testing
- 11.1 8.1 Functional Testing
- 11.2 8.2 Verification and Validation
- 11.2.1 8.2.1 Verification
- 11.2.2 8.2.2 Validation
Introduction
The Global Interlock system protects the personnel and equipment of our observatory from death, serious injury or damage. Access to the controller is restricted; only certain trained and authorized personnel can make changes that may affect system safety. Personnel policies will be in place and enforced with regard to such changes.
Intended Audience
There are two groups of people that will use different sections of this manual—operators and maintenance personnel. For the purposes of this manual, “operator” is used to describe personnel qualified to operate systems and subsystems of the facility not necessarily a job title. “Maintenance personnel” refers to technical staff qualified to diagnose and repair equipment malfunctions.
Only personnel who have been specifically trained and authorized shall perform the procedures detailed in this manual.
Related Documents
Operational Concepts
Reference Documents
Many of the components of the GIS are covered by manufacturer’s user manuals.
Safety Symbols
Standardized safety alerts are used to denote procedures or activities that are potentially hazardous.
Overview
Emergency Stop System
Trapped Key System
Trapped keys prevent unauthorized entry into hazardous areas and prevents unexpected start-up of equipment when persons are in hazardous areas.
Only one key exists for each device. This is by design and essential to maintaining a safe system. Trapped keys must never leave the facility.
Human Machine Interface (HMI)
Procedures
Cold Start up
When power is first applied or re-applied to the system, it will likely cause the system to generate a large number of faults. This is mainly due to the fact that the EtherNet switches of the safety system take substantially longer to boot than the PLCs themselves.
If the safety system was working properly prior to the loss of power and the reason for the loss of power is understood, the quickest way to restore the safety system to normal operations is to cycle the individual LICs power or perform a RUN-PROG-RUN reset by turning the keyswitch from ‘run’ to ‘program’ and back to ‘run’ (This can also be done remotely if the keyswitch is in the ‘remote’ mode).
Functional test of Guard Locking Switch
Guard Locking switches if tripped require that both the fault be cleared AND a functional test of the Guard Lock.
Ensure door is closed.
Reset GIS.
Verify that no fault is present. Diagnostic code will remain.
Lock door (if necessary).
Unlock door.
Open door.
Close door
Verify that no fault is present and there are no diagnostic codes.
Lock door (if necessary).
Normal Operations
During normal operations, the GIS does not require any operator interaction. Operator intervention is required only when the GIS enters a tripped or faulted state.
Logging
The GIS logs various events for troubleshooting purposes. Events to be logged include trips and faults in the system. The logs are timestamped in UTC synchronized to the observatory-wide TRADS system. The logs are kept on the a FactoryTalk Historian module located in the GIC rack. This module can be remotely accessed. The HMI also stores a number of alarms.
Resetting an tripped Interlock
In most cases, trips of the GIS can be reset by using the HMI (Human Machine Interface) to access password-protected screens. Certain trips may be more serious than others and may require higher authorization before proceeding.
Procedures require that the reason for all trips be investigated and understood before proceeding with a reset. The reset does not cause hazardous motion to resume; rather it allows the subsystem that tripped to be restarted.
Hazardous Area Access
Hazardous areas may be entered for various routine reasons. Personnel doing so must ensure that all personnel have left the hazardous area before securing it.
Hazardous areas may also be entered during an emergency. For example, the doors leading to the external ladders may be used to evacuate the building. By their vary nature they cannot be locked with trapped key or must be equipped with an override device.
These two types of tripped interlocks are very different. Normal access using a trapped key may be reset by personnel returning the trapped key in the proper sequence. In the second non-routine case, it would be necessary to inspect the hazardous area and ensure no personnel or other hazards are present prior to attempting to reset this type of tripped interlock.
Muting an Interlock
Periodically it may be required to mute an interlock. Interlock designed to be muted will be designated after a Job Hazard Analysis identifies a routine task that requires an interlock to be ignored.
An example of interlock to be muted would be the manlift stowed interlock. During operations it is foreseen that the manlift may be removed from the observing chamber. Rather than defeating the interlock mechanically or electrically the HMI will allow for a time-limited password-protected bypass to programmatically ignore the interlock.
The purpose of this is to prevent a situation where a jumper is left in place to defeat an interlock. Even if the operator does not manually restore the muted interlock the controller will programmatically restore the interlock after a designated timeout period.
Another example of muting an interlock occurs when the Enclosure Azimuth axis is required to used (albeit at a safely-limited speed) when the Bridge Crane is in use. In this case, the connection of the Enclosure Pendant mutes the interlock when it is connected.
Emergency Operations
Certain operations may be required and interlocks may need to be bypassed to allow emergency operations, such as freeing personnel entrapped in a pinch/crush hazard. [TRW2]
Unlocking Guardlocking Switches
The hazard access guard locking switches are designed to require power to unlock them. In the event of a power failure all guards will lock in place. If personnel are in the hazardous access area they may exit by using the emergency release mechanism installed on the inside of each door or use a monitored only exit door.
If no personnel are inside the hazardous area but entry is required, then entry must be gained through a monitored only exit door. This requires a building key. Once inside the guard locked door may be unlocked using the emergency release mechanism.
Connecting a Computer
Specific steps must be taken to ensure that any computer that is connected to the GIS does not pose a potential hazard to the system. The network configuration of the GIS is to allow only a limited set MAC addresses to be connected. Two maintenance computers will be configured for use on the GIS network. They will have the OS and application programs updated regularly.
Up-to-date anti-virus software must be installed. The computer will also be scanned for viruses prior to connecting to the GIS network. No removable media is to be used without being scanned prior to insertion in the maintenance computers.
Patch Management
From time to time the manufacturer will likely release updates to the firmware used in the various components of the GIS. It is not the intention to upgrade firmware with each new release that is made available. Firmware will only be upgraded when the update is required due to a safety or security concern with the existing firmware or additional capabilities are required for changes to the GIS.
Prior to deploying any software patch, whether it is to the firmware of any component or to the operating system of a host computer, the patch will be qualified by Rockwell Automation for compatibility. After a firmware update the GIS will require a function test to verify proper operation before being returned to service.
Updates to Firmware
Updates to Operating System
Updates to Programming Environment
By-passing an Interlock
In the event of an interlock requiring a bypass due to some unforeseen circumstance, alternate means must be taken to ensure the safety of personnel and the facility.
To ensure that while a bypass is in place that it can be easily tracked; interlocks will not be bypassed by using electronic or mechanical means. Rather, the appropriate tags will be forced in the controller. By forcing the tags in the controller it will be easier to view which interlock(s) have been bypassed and the controller itself will indicate that I/O is in the forced condition.
Since access to the controller is restricted, only certain trained and authorized personnel can make changes that may affect system safety. Personnel policies will be in place and enforced with regard to such changes.
To force data the software project will have to be safety-unlocked and the safety task signature deleted.
Because this results from an unforeseen circumstance a specific Job Hazard Analysis must be performed and approved before bypassing an interlock by forcing controller I/O.
Periodic Maintenance
Battery Replacement
The only regular maintenance required for the L6-series of GuardLogix Controllers is periodic replacement of the battery that backups volatile memory. The battery should be replaced at least every 3 years. The L7 GuardLogix Controllers have replaced the Lithium battery with a capacitor-based energy storage module that does not require period replacement.
Functional Operation Testing
As it is possible that some safety devices (such as e-stop switches) may not be actuated for extended periods of time, the various components of the GIS, while highly reliable, will be examined and functionally tested on an annual basis to reduce the probability that an undetected fault exists that could lead to a hazardous condition.
Repair
The GIS is designed to be maintained and repaired with standard hand tools (Appendix A) and standard test equipment (Appendix B).
No special tools are needed to install, service, maintain, or operate the GIS.
Emergency Replacement of failed trapped key
In the event of trapped key being broken or the barrel failing there are two emergency replacement kits available. Each kit consists of a single key and two replacement barrels.
Replacing a Failed Component
Because of the various security measures in place to prevent changes to the system, specific steps must be taken prior to replacing a failed component. The replacement module will have to be configured with the IP address and Safety Network Number off-line prior to installation. Firmware revision level will be set to the same revision level of the failed component.
After replacement of a failed component the safety functions that are affected by that component will require a functional test see section 7.
8 Testing
There are three basic types of testing, functional testing, verification, and validation. Functional testing is actuating an interlock device (such as a limit switch) and observing that the safety system sees normal operation of the device itself. Verification is similar to a functional test but this test the entire safety-related function by observing that activating the device does in fact cause the subsystem under test to enter a safe state. Validation is testing a safety-related control function by injecting a fault and observing that the subsystem under test enters a safe state.
8.1 Functional Testing
When a fault occurs with the GIS, the system will default to a safe state, to return to normal operations a functional test may be required. Functional tests are required when the system detects a hardware fault such as a two channel discrepancy.
A functional test is performed by causing the unit under test to change from the active state to the non-active state and back again. For example if a hardware fault requires a functional test of an emergency stop push button, the button has to be depressed then pulled back out to ensure that it is functioning properly.
This testing is done without the actually enabling the function.
8.2 Verification and Validation
Verification and validation are required by IEC 62061 and must follow the requirements of that standard.
Verification of the GIS shall include design qualification, installation qualification, operational qualification, and performance qualification.
Design qualification shall consist of a review of the design by qualified reviewers at the final design review.
Installation qualification shall consist of a thorough inspection and test of each circuit to ensure that the installation meets quality standards and is correct according to the schematic drawings and documentation. Any changes found necessary during installation shall be red-lined and corrections to the final document set shall be made.
Operational qualification includes the testing of each circuit for correct response including testing for shorts across circuits, shorts to ground, and shorts to the power bus. For each of these tests, the verification is that the response is to fail to the safe state. These tests shall be documented. These tests shall be repeated for all the subsystems that could be affected whenever a hardware or wiring change is made.
Performance qualification shall be performed on the finished installed system and on the installed system whenever a significant addition or change is made (such as adding a new hardware module or updating firmware or programming). Performance qualification includes testing against specifications for response speed and error-free packet delivery.
8.2.1 Verification
Verification is checking to make sure the function works as intended. This is a simple functional test of the system.
An example would be adding an emergency stop switch. Verification would be pressing the button and checking to see if all systems trip to a safe state.
8.2.2 Validation
Validation is checking to make sure the function works in the event of a failure. In the case of the GIS, this refers to a single failure. The system is designed so that a single failure will be detected before or when a demand is placed on the function. Multiple failures are not considered.
An example of validation would be adding an emergency switch would be shorting each of the two inputs to ground, shorting both inputs together, shorting both inputs to 24VDC and checking to see if all systems fault to a safe state.
[1] IEC 61508-4 3.6.1
[TRW1]http://manualise.com/en/blog/law-and-legislation/ansi-z535-6/
[TRW2]GISFRR-22
[t3]GISFRR-112