text:
API RP 584 Integrity Operating Windows Table of Contents 1. Purpose and Scope .......................................................................... 2 2. Introduction to Integrity Operating Windows ............................................... 3 3. Terms, Definitions, Acronyms and Abbreviations ........................................... 6 4. Parameters That May Require Different Types of IOW's .................................... 8 5. IOW Work Process......................................................................... 11 6. IOW Risk Ranking .......................................................................... 16 7. Examples of IOW's......................................................................... 19 8. IOW Development ......................................................................... 23 9. General Considerations for Establishing IOW's and Their Limits .......................... 26 10. Documenting, Implementing and Training on Established IOW's ......................... 28 11. Monitoring and Measuring IOW Parameters.............................................. 31 12. Updating IOW's ............................................................................ 32 13. Roles, Responsibilities and Accountabilities for IOW's .................................... 32 14. Integrating IOW's with Other Related Work Processes ................................... 34 Appendix A: Examples of Potential Process Parameters for IOW's ............................. 36 Appendix B: Sample Format for Recording IOWs ............................................... 40 Appendix C: Example of an IOW Development for a Heat Exchanger .......................... 41 September 23, 2011 Page 1 API RP 584 Integrity Operating Windows Purpose and Scope 1.1. The purpose of this RP is to explain the importance of IOW's for process safety management and to guide users in how to establish and implement an IOW program for refining and petrochemical process facilities for the express purpose of avoiding unexpected equipment degradation that could lead to loss of containment. It is not the intent of this document to provide a complete list of specific IOW's or operating variables that might need IOW's for the numerous types of hydrocarbon process units in the industry (though some generic examples are provided in the text and in Appendix A); but rather to provide the user with information and guidance on the work process for development and implementation of IOW's for each process unit. 1.2. The scope of this standard includes: - Definitions of IOW's and related terminology, - Creating and establishing IOW's, - Data and information typically needed to establish IOW's, - Descriptions of the various types of IOW's needed for process units, - Risk ranking IOW's, - Documenting and implementing IOW's, - Monitoring and measuring process variables within established IOW's, - Communication of IOW exceedances, - Reviewing, changing and updating IOW's, - Integrating IOW's with other risk management practices, - Roles and responsibilities in the IOW work process, and - Knowledge transfer to affected personnel. 1.3 This recommended practice outlines the essential elements in defining, monitoring and maintaining Integrity Operating Windows (IOW's) as a vital component of corrosion management (materials degradation control) and inspection planning, including RBI. Other PSM systems may be affected by or involved with the IOW program, including Management of Change (MOC), Process Safety Information (PSI) and Training. For purposes of this RP, these systems are only addressed to the extent of mentioning the integration aspects that are needed with the IOW program. 1.4 This RP does not cover operating windows established for normal process control for the purposes of maintaining product quality and other operating factors that do not relate to control for the purpose of maintaining equipment integrity and reliability. September 23, 2011 Page 2 API RP 584 Integrity Operating Windows 2. Introduction to Integrity Operating Windows 2.1. In today's operating environment, it is not enough to base future inspection plans only on prior recorded/known history of equipment condition. A fundamental understanding of the process/operating conditions and resulting damage mechanisms are required in order to establish and maintain an inspection program that yields the highest probability of detecting potential damage. Inspection plans should be dynamic and account for changing process conditions and current equipment condition. A fundamental step is to frequently rationalize and align the developed degradation knowledge base of the materials of construction with the operation of the equipment, its inspection history, measured corrosion rates and known industry problems. With the move to risk based inspection programs, it is even more vital to identify and track process information that validates or might cause changes to existing inspection plans. 2.2. In order to maintain the integrity and reliability of pressure equipment in the refining and petrochemical industry, several process safety management systems are necessary. Many of those management systems are oriented toward having a rigorous inspection program, as well as all the supportive engineering activities, to maintain pressure equipment integrity and reliability. The Inspection, Corrosion/Materials, and Atmospheric Storage Tank Subcommittees of the API Committee on Refinery Equipment have produced a variety of codes, standards and recommended practices to guide owner-users in maintaining pressure equipment integrity and reliability, including: - API 510 Pressure Vessel Inspection Code - API 570 Piping Inspection Code - API RP 571 Damage Mechanisms Affecting Fixed Equipment in the Refining Industry - API RP 572 Inspection Practices for Pressure Vessels - API RP 573 Inspection of Fired Heaters and Boilers - API RP 574 Inspection Practices for Piping System Components - API RP 575 Methods for Inspection of Atmospheric and Low Pressure Storage Tanks - API RP 576 Inspection of Pressure Relieving Devices - API RP 577 Welding Inspection and Metallurgy - API RP 578 Material Verification Program for New and Existing Alloy Piping Systems - API RP 579 Fitness for Service - API RP 580 Risk-Based Inspection - API RP 581 Risk-Based Inspection Technology - API RP 582 Welding Guidelines for the Chemical, Oil and Gas Industries - API RP 583 Corrosion Under Insulation (pending publication) - API RP 585 Pressure Equipment Integrity Incident Investigation (pending publication) - API STD 653 Tank Inspection, Repair, Alteration and Reconstruction - API Pub 932A A Study of Corrosion in Hydroprocess Reactor Effluent Air Cooler Systems September 23, 2011 Page 3 API RP 584 Integrity Operating Windows - API Pub 932B Design, Materials, Fabrication, Operation and Inspection Guidelines for Corrosion Control in Hydroprocessing Reactor Effluent Air Cooler (REAC) Systems - API RP 939C Guidelines for Avoiding Sulfidation Corrosion Failures in Oil Refineries - API RP 941 Steels for Hydrogen Service at Elevated Temperatures and Pressures in Petroleum Refineries and Petrochemical Plants - API RP 945 Avoiding Environmental Cracking in Amine Units 2.3. In addition to the application of industry codes, standards and recommended practices, a number of other process safety management (PSM) systems are vital to support a rigorous inspection and mechanical integrity program in order to predict / avoid /prevent pressure equipment damage/corrosion, leaks and failures and improve reliability. Three key elements of those supporting PSM programs include: 184.108.40.206. The establishment, implementation and maintenance of Integrity Operating Windows (IOWs), 220.127.116.11. An effective transfer of knowledge about unit specific IOW's to all affected personnel, and 188.8.131.52. An effective management of change (MOC) program to identify any changes to the process or the physical hardware that might affect the integrity of pressure equipment. 2.4. In order to operate any process unit, a set of operating ranges and limits needs to be established for key process variables, to achieve the desired results (i.e. product within specification, safe operation, reliability, etc.). These limits are generally called operating limits or operating envelopes. IOW's are a specific subset of these key operating limits that focus only on maintaining the integrity or reliability of process equipment. Typically IOW's address issues that involve process variables that, when not adequately monitored or controlled, can impact the likelihood and rates of damage mechanisms, which may result in a loss of containment. 2.5. For purposes of this document, maintaining the integrity of the process unit means avoiding breaches of containment, and reliability means avoiding malfunctions of the pressure equipment that might impact the performance of the process unit (meeting its intended function for a specified time frame). In that sense, integrity is a part of the larger issue of pressure equipment reliability, since most breaches of containment will impact reliability. Integrity operating windows (IOWs) are those preset limits on process variables that need to be established and implemented in order to prevent potential breaches of containment that might occur as a result of not controlling the process sufficiently to avoid unexpected or unplanned deterioration or damage to pressure equipment. Operation within the preset limits should result in predictable and reasonably low rates of degradation. Operation outside the IOW limits could result in unanticipated damage, accelerated damage and potential equipment failure from one or more damage mechanisms. September 23, 2011 Page 4 API RP 584 Integrity Operating Windows 2.6. Pressure equipment is generally fabricated from the most economical materials of construction to meet specific design criteria based on the intended operation and process conditions. The operating process conditions should then be controlled within preset limits (IOW's) in order to avoid unacceptable construction material degradation and achieve the desired economic design life of the assets. 2.7. One of the simplest examples of IOWs is the establishment of furnace tube temperature limits to avoid premature rupture or unplanned replacement of the tubes. For example, a furnace tube designed for 950 °F operation would have a shortened service life if operated at 1000 °F, so when this limit (950 °F) is exceeded, operators would be directed to adjust furnace controls to get the tube temperature back to below 950 °F within a preset amount of time. That limit of 950 °F would be an IOW limit for those furnace tubes. At an even higher temperature, say 1025 °F, the operator might be directed to take more immediate actions to regain control or even shut down the furnace. As such there may be more than one IOW limit for the same process parameter (in this case furnace tube temperature), for tracking/trending or to gain control prior to reaching a critical limit. In addition, there may be more than one predefined response, depending upon the degree of exceedance of the process parameter limit. 2.8. A properly structured and effective inspection program depends on IOW's being established and implemented to avoid unanticipated negative impacts on pressure equipment integrity. Inspection programs are designed to look for damage mechanisms that are expected and are not generally designed to look for unanticipated damage resulting from inadequately controlled processes/ operation. Inspection programs generally assume that the next inspection interval (calculated based on prior damage rates from past operating experience) should be scheduled on the basis of what is already known and predictable about equipment degradation from previous inspections. Without effective process control, based on a high quality and complete list of IOW's, inspections might need to be scheduled on a frequent time-based interval just to look for anything that might potentially occur from lack of adequate process control. 3. Terms, Definitions, Acronyms and Abbreviations 3.1. Alarms – Primary method of communication for Critical IOW exceedances and some higher level Standard IOW's. Typically would be an audible sound (e.g. horn, buzzer, beep, etc.) along with a visual signal (e.g. flashing light), in the control room that alerts operators to a potential deviation in a process condition that may need immediate attention. 3.2. Alerts – A secondary level of communication to key stakeholders (i.e. Operations, Technical SME's) that signifies a condition that will need resolution to avoid a potential operating September 23, 2011 Page 5 API RP 584 Integrity Operating Windows condition that could lead to process safety or reliability impacts. Generally, alerts can be addressed over a longer time period than alarms. Alerts may include visual signals and/or audible sounds and/or other real-time process tracking charts/graphs with limits identified, e-mail notifications, etc. For this RP, alerts are related primarily to Standard IOW exceedances, but may also be implemented for Informational IOW's. 3.3. CCD: Corrosion Control Document –Documents that contain all the necessary information to understand materials degradation issues in a specific type of operating process unit 3.4. CLD: Corrosion Loop Diagram – drawings of portions of process units showing areas of similar corrosion mechanisms, similar operating conditions, and similar materials of construction. 3.5. CMD: Corrosion Materials Diagram – A modified process flow diagram (PFD) showing equipment and piping corrosion mechanisms, operating conditions, and materials of construction in each portion of a process unit, as well as the usual PFD information. 3.6. IOW: Integrity Operating Window – Established limits for process variables (parameters) that can affect the integrity of the equipment if the process operation deviates from the established limits for a predetermined amount of time (includes Critical, Standard and Informational IOW's). 3.7. IOW Critical Limit–An established IOW level which, if exceeded, rapid deterioration could occur such that the operator must take immediate predetermined actions to return the process variable back within the IOW to prevent significant defined risks of potential equipment damage or hazardous fluid release could occur in a fairly short timeframe. Other terminology has been used in place of Critical Limit, such as Safe Operating Limit. 3.8. IOW Standard Limit–An established IOW level defined as one that if exceeded over a specified period of time could cause increased degradation rates or introduce new damage mechanisms beyond those anticipated. Since the timing of the impact from an exceedance of a Standard IOW Limit can vary significantly, the notification and response to an exceedance can also vary. For higher risk exceedances, alarms or alerts are potentially needed and the operator may have some predetermined actions to take. For lower risk exceedances, alerts may only be needed for eventual interaction with operating supervisors or appropriate other technical personnel (SME's). NOTE: Other terminology for standard limits has been used such as Key Operating Limit or Reliability Operating Limit. 3.9. IOW Information Limit (IIL) – An established limit or standard operating range for other integrity parameters that are used primarily by SME's (e.g. process engineer, inspector, corrosion specialist, etc.) to predict and/or control the longer term integrity/reliability of the equipment. These "Informational" IOW's are typically only tracked by the appropriate SME's and may or may not have alarms or alerts associated with their September 23, 2011 Page 6 API RP 584 Integrity Operating Windows exceedances. In some cases the Informational IOW's are used for parameters that cannot be directly (or indirectly) controlled by operators, whose primary duty would be to make sure any exceedances are communicated to the designated SME for attention and corrective action, if any. NOTE: Other terminology can be used in place of an Informational Limit, such as Corrosion Control Limit or Reliability Limit. 3.10. MOC: Management of Change – A documented management system for review and approval of changes in process, equipment or piping systems prior to implementation of the change. For purposes of this RP, MOC may apply to making changes to or creating IOW's. 3.11. MI: Mechanical Integrity–The management systems, work practices, methods and procedures established in order to protect and preserve the integrity of operating equipment i.e. avoid loss of containment due to the effect of equipment damage mechanisms. 3.12. Notifications – A message to an operator / SME that an IOW exceedance has occurred which may not necessarily have an alarm associated with it, but may require a specific required action and response from an operator or SME. 3.13. PFD: Process Flow Diagram – A simplified diagram of a process unit showing the main pieces of equipment and piping, with limited details of process design parameters. 3.14. PHA: Process Hazards Analysis – A work process to assess and document the hazards and risks associated with operating a process unit, and to make recommendations on what actions may be necessary to mitigate unacceptable risks. 3.15. Process Variables: Parameters of the process fluids (chemical and physical) that need to be controlled. 3.16. PSM: Process Safety Management –The implementation of all the work practices, procedures, management systems, training, and process safety information that are necessary in order to prevent the release of hazardous substances from process equipment. 3.17. Pressure Equipment – Stationary or fixed equipment for containing process fluids under pressure, not including rotating equipment. EXAMPLES: Pressure equipment includes, but is not limited to such items as piping, vessels, heat exchangers, reactors, tanks, pressure relief devices, columns, towers, heater tubes and filters. 3.18. RBI: Risk-Based Inspection – A risk assessment and management process that is focused on loss of containment of pressurized equipment in processing facilities, due to material deterioration. These risks are managed primarily through equipment inspection. September 23, 2011 Page 7 API RP 584 Integrity Operating Windows 3.19. SME: Subject-Matter-Expert – One who has in-depth knowledge and experience on a specific subject as it relates to IOW's, Various types of SME's are necessary in order to establish IOW's for each process unit e.g. corrosion/materials SME; process SME; operations SME, equipment type SME, etc. 3.20. Stakeholder - Any individual, group or organization that may affect, be affected by, or perceive itself to be affected by the IOW issue. 3.21. TAN: Total Acid Number – A measure of potential corrosiveness of hydrocarbon feed steams containing various organic acids 3.22. Work Process – A series of activities or steps aimed at achieving a set objective, with inputs and outputs e.g. the IOW work process to establish IOW limits on operating parameters. 4. Parameters that May Require Different Types of IOW's 4.1. Typically IOW process parameters that may influence the mechanical integrity or reliability of the equipment fall into two categories, chemical and physical. The parameters noted below are not all inclusive, but provide examples of the potential process parameters that may need IOW's established in order to control degradation rates and/or avoid the onset on new degradation mechanisms that might eventually lead to breaches of containment. 4.1.1. Chemical parameters are those that relate to the chemistry and fluid content of the process. Examples of chemical parameters include: pH, water content, acid gas loading, sulfur content, salt content, NH4HS limits, NH3 content, TAN, acid strength, amine strength, inhibitor concentration, chloride contamination levels, oxygen content, etc. 4.1.2. Physical (mechanical, operational) parameters are those that are not chemical in nature, but include all other aspects of a process design that are vital to maintaining control within established design parameters. Examples of physical parameters include: various pressure and temperatures including such as design, operating, partial pressures, dew points, dry points, heating and cooling rates, delta P, etc., In addition, there are flow rates, injection rates, inhibitor dosage, amperage levels for contactors, slurry contents, hydrogen flux, vibration limits, corrosion probe measurements, etc. 4.2. IOW's should be classified into different levels, distinguished by risk, in order to set priorities on notifications (including; alarms, alerts and/or other notifications) and timing of actions to be implemented when IOW's are exceeded. In this standard, three primary levels of IOW's, "Critical", "Standard" and "Informational", are described based upon the predicted damage rate to pressure equipment during an exceedance and the ability of the operator to take corrective action. September 23, 2011 Page 8 API RP 584 Integrity Operating Windows 4.2.1. A standard IOW level is defined as one that if exceeded over a specified period of time, requires predetermined operator intervention or some other corrective action by an SME in order to bring the process back within the IOW limits in order to avoid one or more of the following to occur: Eventual loss of containment, A release of hydrocarbons or hazardous fluids, Unscheduled or non-orderly shutdown, A negative impact to the long term unit performance and its ability to meet turnaround run length, or Unacceptable financial risk. 4.2.2. A critical IOW level is defined as one at which the operator must urgently return the process to a safe condition and, if exceeded, could result in one of the following in a fairly short timeframe: Larger and/or quicker loss of containment, A catastrophic release of hydrocarbons or other hazardous fluids, Emergency or rapid non-orderly shutdown, Significant environmental risk, or Excessive financial risk Other unacceptable risk. 4.2.3. A third level of IOW's may be established that are "Informational Limits". Most parameters that have defined IOW's are controllable, especially for Critical and Standard Limits, but some are not and may not have an immediate designated operator intervention assigned to them. Deviations from mechanical or process design conditions could eventually lead to accelerated corrosion or other damage over a longer period of time. These parameters which may not be controlled by operators still may need to be reported to, reviewed by and trended by designated technical personnel (SME's). For example, these Informational parameters may provide secondary or circumstantial indication of active corrosion/erosion such as in an atmospheric overhead tower where the primary process control parameter for corrosion in the reflux may be the pH of the condensate, but a secondary informational parameter may be the iron content measured periodically by laboratory sampling. When exceedances of these informational parameters are reported, the appropriate SME's in turn may then specify that some type of engineering, process or inspection activities be planned or adjusted in order to control the rate of deterioration and prevent unacceptable equipment deterioration over the longer term. These informational IOW's do not normally have alarms or alerts associated with exceedances. In most cases, the limits for informational parameters would be established to provide a point where the operator (or implemented software) would initiate a notification to the appropriate SME that some September 23, 2011 Page 9 API RP 584 Integrity Operating Windows informational parameter has exceeded a limit. Informational IOW's would typically be associated with the following situations: Would not be directly related to a potential loss of containment within the near term, Provides for an secondary indication of operational performance or corrosion control issue, and/or, Used to track parameters that are not necessarily controllable by operators. 4.3. The primary difference between a Critical and a Standard limit is in the reaction time allowed to return the process to within the IOW limits. For Critical limits, there will typically be visual and audible alarms for the operators and typically all Critical Limits would require specific predetermined actions to be taken by the operator to urgently return the process to within the IOW limits. In some cases there may also be instrumented shutdown systems that automate a sequence of steps to regain control of the process. For some Standard limits, there may also be visual and/or audible alarms, depending upon the level of risk and required response time associated with the IOW. A risk assessment process such as that outlined in sections 5.8 and 6.0 can be used to determine the need for what alerts/alarms are appropriate for each IOW. Standard limits can in many cases be just more conservative limits set for operating parameters prior to reaching Critical limits in order to provide the operator with more time and options to bring the process back within the IOW limit before the more urgent measures required for exceeding a Critical limit must be implemented. 4.4. In addition to the predetermined operator intervention required for Critical limits and potentially Standard limits that are exceeded, notifications to designated SME's should be designed into the system, so that appropriate investigations and corrective actions can be implemented to prevent further exceedances and plan for necessary follow-up testing / inspection. These notifications should include designated inspection and corrosion specialists in case inspection plans need to be adjusted, depending upon the magnitude of the exceedance or in case corrosion management strategies may need to be adjusted. 4.5. Figure 3 below illustrates visually how various types of operating limits might create boundaries for any specific operating window. The middle zone between the standard limits (high and low), is the zone designated for achieving operational targets. Outside of those limits, operator intervention is generally required to return the process into this zone. Some limit ranges may not have an upper or lower boundary, depending on the variable. For example, tube-skin temperatures generally have upper limits, but most times has no lower limit. September 23, 2011 Page 10 API RP 584 Integrity Operating Windows Figure 1. Zones of operation including target ranges with standard and critical limits. 5. IOW Work Process 5.1. In this section a general work process is outlined for identifying IOW's and setting appropriate limits relative to a defined premise. Additional details on the type and levels of IOW's are outlined in Section 4 and Section 6. For a specific example that closely follows the flow outlined in this section for one specific piece of equipment, see Appendix C. General guidance and considerations for identifying and setting appropriately conservative limits is outlined in Section 9. Note that this work process may be applied to a single equipment item, multiple equipment items in a group (corrosion circuit) or more generally to the overall process unit. A flow chart for the overall work process is shown below in Figure 5.1. September 23, 2011 Page 11 API RP 584 Integrity Operating Windows Figure 5.1 Suggested IOW Development Work Process. September 23, 2011 Page 12 API RP 584 Integrity Operating Windows 5.2. The first step in the process is to review the existing mechanical design conditions and prior operating conditions (normal, upset, start-up, shut-down, etc.). The identification of the likely or "active" damage mechanisms in Section 5.5 requires a fundamental understanding of the mechanical design,the process operating conditions (temperatures, pressures, service, inhibitors, etc.) and the materials of construction including the alloy and material grade, method of fabrication, prior thermal and mechanical treatments, etc. Consideration should be given to both the normal operation and any non-normal operation that could produce unanticipated damage mechanisms and/or accelerated damage rates. Other operating conditions such as startup, shutdown, catalyst regeneration, decoking, hydrogen stripping, etc. should also be considered. 5.3. The second step is to define any anticipated future unit/equipment operating conditions and establish a "premise" for establishing IOW limits. Any planned changes to the operation will need to be considered during the identification of the "potential" damage mechanisms that may be associated with those planned changes (i.e. higher sulfur in the feed stock to a refinery). 5.4. In the second part of this step, an operating premise needs to be developed that establishes the desired future run time for reliable operation and acceptable economic life of the asset. Generally the premise would be established on an acceptable damage rate or maximum amount of damage acceptable during the planned run time. In some cases, it may include setting limits on operating conditions that may introduce a new damage mechanism e.g. a limit may be placed on operating temperature in a Hydrotreater in order to avoid High Temperature Hydrogen Attack (HTHA). A key consideration for establishing a premise is the time frame for which it will apply. In some cases, the established time frame may be very short (for a specific operation to take advantage of an opportunity feed stock for example), but in general, the time frame for setting damage limits should be based on an acceptable life for the equipment and/or the time period until the next turnaround. A premise may be established on an individual equipment basis or on a unit specific basis. September 23, 2011 Page 13 API RP 584 Integrity Operating Windows 5.5. The next step is to identify all of the active and potential types of degradation mechanisms that could occur in each piece of process equipment. A determine should be made of the historical damage rate for the equipment and predicted future rate considering any planned changes in operation. Section 7 and Appendix A contain examples of degradation mechanisms and potential operating variables within process units that may need IOW's established. There are several other sources of industry data that specifically identify typical degradation mechanisms for various operating units. Specifically applicable to the refining and petrochemical industry is API RP 571 covering damage mechanisms and API RP 580 and RP 581 covering Risk Based Inspection. A list of common degradation mechanisms is also provided in API 579 / ASME FFS-1 Fitness-For-Service Annex G. Specific operating site programs that have been utilized to identify/establish equipment specific damage mechanisms and/or risk that should be considered during this process may include; Risk Based Inspection Studies; Corrosion Loop & Circuitization Programs or other Unit Corrosion Reviews; Equipment Criticality Assessments; PHA or HAZOP Studies. 5.6. After identifying all applicable degradation mechanisms, each process variable related to activation of, or progression of the equipment damage needs to be identified. In many cases, there will be multiple, sometimes co-dependant operating variables that are required to produce the damage e.g. temperature, reactive sulfur content and alloy are co-dependant variables that affect the high temperature sulfidation rate. There may also be multiple variables, product / reactants or other measurements that are indicators of the activity of a single specific damage mechanism e.g. desalter efficiency, pH, chloride content, iron content, conductivity, salt point, dew point and others are all indicators of corrosion potential in an crude unit atmospheric tower overhead system. The goal of the IOW program is not only to identify the key monitoring parameters but to also set limits around the most appropriate "controllable" parameters that can be adjusted by operations to achieve the desired level of equipment integrity and reliability. In general, the parameter that is most "controllable" and most effective at reducing the corrosion potential should be the primary variable for monitoring and applying limits. Other measurements or variables that are not primary indicators of damage may be considered as informational. 5.7. Once the primary controllable operating variables/parameters have been identified, the next step in the process is to establish upper and lower limits to avoid unacceptable damage mechanisms/rates. There are multiple aspects to consider when establishing each of the operating limits as follows; September 23, 2011 Page 14 API RP 584 Integrity Operating Windows 5.7.1. The limit needs to consider the accuracy and relevance of the measurement e.g. measurement location may not be ideal relative to the damage location, the degree of measurement accuracy may require a more conservative limit being set to provide adequate response time if the measurement is not entirely accurate. 5.7.2. The limit needs to consider the rate of further damage progression at the limit level selected i.e. how fast is the damage expected to progress and is there adequate time to adjust the operation to avoid failure or unacceptable damage to the equipment. 5.7.3. The limit needs to consider the level of risk for exceeding that limit. Setting a process limit will be related to the level of notification needed (alarm, alert, e-mail, or other notification) and related to the predetermined response actions when that limit is exceeded. 5.7.4. Consideration should be given to setting multiple limits in some cases to provide more time and less urgent responses to bring the operation back within normal operation before reaching a possible Critical IOW limit. Some process variables could have an IIL at one limit that would provide time to an SME to consider an appropriate response, a Standard IOW limit at a next level which may have a designated operator response, and ultimately a Critical IOW limit which would require an urgent operator response. 5.7.5. Limits are not only a target value for a single parameter. Many of the corrosion related damage mechanisms also have a significant time element that needs to be considered. For the simple case of high temperature sulfidation, where temperature, alloy type and amount of reactive sulfur present in the process stream drive the corrosion rate; if a limit were to be set on temperature alone an exceedance may occur without any measurable damage to the equipment if there was insufficient time for measurable damage to occur. 5.8. In order to determine the level of the IOW (Critical, Standard or Informational) a Risk Ranking process is useful. In some cases, the relative risk may be determined subjectively and in more complicated cases, the risk analysis may need to be more rigorous. Many operating companies have developed risk matrices and risk analysis procedures to provide guidance for consistent management decisions which may be used to determine the risk of exceeding the established IOW limit. An example risk matrix and analysis is provided in Section 6. Determining the IOW level and or risk for a given parameter is important to help distinguish which parameters and limits: will need alarms versus alerts, if predetermined actions must be taken to speed recovery times, help determine which parameters may fall under the OSHA Process Safety Information requirement, which exceedances may need formalized follow-up and investigation, and September 23, 2011 Page 15 API RP 584 Integrity Operating Windows which limits if changed or adjusted may need to be managed through a MOC process, etc. 5.9. Once the limits and relative risk ranking has been developed, the initially established limits should be compared to the original operating premise that was developed. The risk level for each parameter is often dependent (or co-dependant) on multiple factors and may need to be developed through an iterative process. In some cases, the existing sample points, instrument ranges, frequency of data acquisition, etc. may not be optimal in which case the assumed risk based on that measurement limit may be higher than is desirable. The intended business objectives for the run period also need to be considered, achieving product yields or production rates may require a compromise for some of the IOW limits, provided the risks associated with such compromises are acceptable to all stakeholders. In reality, this iterative process may be accomplished intuitively during the risk ranking process by continually testing a proposed limit level against the risk assumed at that level. 5.10. After establishing the limits and risk, the level of IOW (Critical, Standard or Informational) can be set. As noted in 5.8 (above), the selected level of IOW is used to distinguish which parameters and limits will need alarms, alerts or other type of notifications, as well as the required response actions and timing, per 5.11. The level is also linked to the need to determine the amount of documentation required, ownership of the IOW and necessary follow-up on exceedances that have been recorded. 5.11. The last box in the flow chart in figure 5.1 is to determine the appropriate actions that need to be taken and response timing for each IOW exceedance. As has been previously mentioned, Critical IOW exceedances will normally require a somewhat urgent specific response by the operator to avoid more rapid equipment degradation problems. That response should be spelled out and agreed to by the IOW team. Standard IOW exceedances will vary in their response actions and timing and will be less urgent than those associated with Critical IOW exceedances, but should also be spelled out and agreed to by the IOW team. Some of those actions will likely be for operators, but other response actions may be for designated SME's. Response actions and timing for IIL's will generally be mostly related to which SME should be notified in order to determine what response action is needed, if any, over the longer term. 6. IOW Risk Ranking 6.1. In this section, an example risk ranking process and risk matrix is provided to guide the user through a relative risk evaluation on the importance and priority of each parameter / limit combination under consideration. As noted in Section 5, IOW's may be risk ranked in order to help determine the appropriate priority of alarms, alerts and September 23, 2011 Page 16 API RP 584 Integrity Operating Windows notifications to operating personnel and SME's, as needed and/or specified by the IOW response action. This risk assessment will also help to determine what actions the operator needs to take and how fast the operator needs to act before the process gets too far out of control i.e. the higher the risk, the sooner the operator may need to respond and the more definitive the response may need to be. And the higher the risk the more levels of action might be designated for Standard IOW's in order to provide the greatest chance of regaining control before a Critical level of alarm is reached. See figure 3 showing an example where there might be more than one standard limit for tube-skin temperature IOW's before reaching a critical IOW limit. 6.2. The criticality or risk of the established limits for a given operating parameter is a function of the event probability and consequence (i.e. risk) when the limit is exceeded. In each case or scenario there will be a number of risk sub-factors that need to be considered when establishing the criticality/risk levels which will be related to the probability of the event and the potential consequence if the event occurs. An approach to establishing three levels of IOW's ("Critical", "Standard" and "Informational" limits) is outlined in order to separate IOW's for process parameters that may have shorter term process safety implications from those that have longer term process safety or reliability implications. After designating the highest risk IOW'S, i.e. Critical Limits, additional prioritization can be achieved through risk ranking of the "Standard" and even the "Informational" Limits in order to identify those limits that need quicker, more definitive action by the operator from those where there is more time to react to the information. 6.3. Tables 1 and 2 contain simplified examples of how a risk assessment matrix and process can be used to establish IOW's. Start by assuming a limit to a given parameter that may meet the premise established for the intended operating period. For that limit determine how likely and how quickly the component or equipment is to fail if that limit is exceeded. Also determine what the consequences are if failure does occur at the imposed limit level i.e. small leak, big leak, immediate emergency, safety issue and size, environmental issue and size, reliability issue and size, etc. The product of these two factors (probability of failure and consequence of failure) is the risk of failure. In table 2 (below) some suggested generic guidance, actions, involvement and responses to different levels of risk are shown. September 23, 2011 Page 17 API RP 584 Integrity Operating Windows Table 1 Generic Risk Matrix for Assessing IOW levels Table 2 Example Risk Chart for IOW Types / Actions / Guidance September 23, 2011 Page 18 API RP 584 Integrity Operating Windows 6.4. For a simple example of the use of this risk assessment approach, time is used in place of a probability of failure, where a probability of "5" = highly likely to fail within hours to days. For consequence of failure we will use a combination of safety and business interruption where the consequence of "D" = Significant exposure risk to personnel and potential loss of profit. This result would yield a "5D" category on the matrix in Table 1 with a corresponding "high" risk. Using Table 2, we determine that Critical Limits are required to be established with appropriate alarms where operators are required to take fairly urgent predetermined actions to return the process to normal operation. In addition, the appropriate SME's are notified for this parameter exceedance along with operations supervision. 6.5. A second example of the use of this risk assessment approach involves an unexpected process change that results in a likely to fail corrosion situation within a few months, if something is not corrected. So it's not immediately urgent, but clearly needs attention relatively soon. A probability of 4 is assigned. The consequence involves a big leak which would involve a possible environmental citation and business interruption, as well as undesirable media attention. A consequence of C is assigned, resulting in a 4C medium high risk on the matrix in table 1. Using table 2, Critical or Standard IOW's would be established and operators would have predetermined actions associated with the exceecance which would need to be implemented within the predetermined time and likely also a notification to corrosion specialist would be implemented to assess the situation and recommend further actions, if necessary. 7. Examples of IOW's 7.1. An example of an IOW set for high temperature hydrogen attack (HTHA) is shown in Figure 2, below. Note that mechanical design limits from the construction code for the vessel are outside the IOW limits for the process, which are typically set from some function of the appropriate Nelson curves in API RP 941. Note also that although the start-of-run conditions (SOR) are within the IOW, the end-of-run conditions may be outside the IOW depending upon hydrogen partial pressure and the duration of the EOR conditions. In this specific case, some owner-users may decide that a short term operation at EOR conditions above the Nelson curve is acceptable based on the amount of time it takes for incipient HTHA to occur i.e. no significant HTHA damage will occur. Other operators may decide that the IOW should never be exceeded even with EOR conditions. Such decisions can be made using appropriate risk analysis and the input of knowledgeable corrosion/materials SME's who are aware of the damage accumulation and incipient attack issues with HTHA. September 23, 2011 Page 19 API RP 584 Integrity Operating Windows Figure 2. Example of IOW limits for HTHA in a hydroprocess unit 7.2. Figure 3 is another example of how critical and standard IOW limits interact for controlling furnace tube temperatures. Several high temperature damage mechanisms are possible in furnace tubes. In general the main concern for furnace tubes is about the long term creep life and corrosion rates. However, at higher than design temperatures, failure can occur due to overpressure from the significant loss in material strength, i.e. short-term overheat and stress rupture. Figure 3 is an example of how various Alert and Alarm levels for potential Critical and Standard IOW's might be needed or considered for various tube temperature levels. September 23, 2011 Page 20 API RP 584 Integrity Operating Windows Potential Critical IOW Alarm Set Point Temperature Increasing > Long Term Creep Damage Short Term Creep Damage Design Metal Temperature Imminent Failure due to loss Concern and higher sulfidic Concern potentially high from API-530 of material strength corrosion rates sulfidic corrosion rates SME Track & Trend Potential Standard IOW Alert Set Point(s) Figure 3 Example of Critical and Standard IOW Limits for Furnace Tubes 7.3. Some examples of critical IOW limits would include: - Delayed Coker Heater Pass Flows Low flow can contribute to coking and overheating - Boiler Feed Water Level - Loss of boiler feed water level could quickly cause boiler tube rupture - Hydroprocess Reactor Temperature - Metal temperatures below the MAT could give rise to brittle fracture - Heater Tube Skin Temperature - Tube could rupture quickly if overheated, caused, for example, by a no flow or hot spot condition - Sulfuric Acid Strength in Alkylation - Too low acid strength could cause runaway reaction - System pressure on a major piece of pressure equipment - Over-pressure could result in major environmental and/or community impact 7.4. Some examples of standard IOW limits would include: - Hydrocracker Reactor effluent air cooler (REAC) NH4HS Concentration - Corrosion of the air cooler and downstream piping - Heater Tube Skin Temperature September 23, 2011 Page 21 API RP 584 Integrity Operating Windows - Metallurgical creep could lead to eventual tube failure - Crude Fractionator Dew Point Temperature - Sustained operation below dew point could cause damage to fractionator internals or potential loss of containment - pH of Crude Tower Overhead - Sustained operation below standard pH level could lead to corrosion of heat exchanger components, especially tubing and piping and potential loss of containment - Hydroprocess units - Water and/or chloride carry-over in hydrocarbon feed streams or hydrogen could cause accelerated corrosion from ammonium salts and hydrogen chloride solutions - Desalter Outlet Conditions - Sustained operation with salt content above standard level could lead to corrosion and potential loss of containment - Crude desalter temperature - Temperatures higher than 300 F will cause permanent damage to the Teflon bushings that insulate the electric grids Deterioration of these bushings will cause grid shorting and rendering the desalter non effective - Sulfuric Acid Alkylation DIB acid wash - Acid circulation rate – High flow will increase acid entrainment due to over mixing. Low rate will not allow for sufficient contact between acid and hydrocarbon Sulfuric Acid Alkylation – iron content in fresh purchased acid. Fresh acid will dissolve iron to achieve saturation point - Delayed Coker feed TAN content - High TAN can cause corrosion in the temperature range of 425 – 750 F - Delayed Coker feed sodium content - Sodium will cause rapid fouling of the heaters and can cause over heating of tubes - Solids Content - Coupled with a critical flow rate, can result in erosion/corrosion - FCCU Fractionator Bottoms system - Solids Content coupled with a critical flow rate, can result in rapid erosion/corrosion 7.5. Some examples of IOW Informational Limits (IIL's) include: - Ammonia content in a crude overhead system that could be assessed to determine if ammonium chloride fouling and corrosion may be occurring. - Calculated heat transfer coefficients and pressure drops for heat exchangers - Calculated dew points to avoid water drop out - Calculated salt deposition temperature to avoid precipitation of salts and fouling - Calculated wash water vaporization rates for wash water effectiveness - pH, chlorides, hardness, iron, cyanides in wash water to avoid corrosion September 23, 2011 Page 22 API RP 584 Integrity Operating Windows - Temperature differences between parallel banks or tubes from IR surveys for flow distribution in reactor effluent air cooler (REAC) systems that could lead to accelerated corrosion - Ammonia content in a crude overhead system that could be assessed to determine if ammonium chloride fouling and corrosion may be occurring - Carbonate content in the FCCU Gas Plant and Claus Quench Tower waters that would promote carbonate stress corrosion cracking. - Process though-puts that exceed design and may affect damage mechanisms - Turbidity of cooling tower water - increase can be an indication of increased risk of deposits and biological attack - Cyanide content in FCCU and DCU Gas Plant waters. The presence of cyanide will promote wet H2S cracking and promote general corrosion by destroying the protective iron sulfide layer - Iron concentration (ppm) in the steam condensate system. Iron will indicate accelerated corrosion due to low pH condensate. This could be an indication of upstream problems in either water treatment or neutralizing amine injection - Organic chlorides in purchased NHT feeds in a sampled tank that is not yet on line. Organic chlorides can lead to very high corrosion rates in the NHT and other hydroprocess units. - Temperature that has increased as a result of process creep. The temperature may have increased to a point that it now puts the equipment in the sulfidation range 7.6. More detailed, specific examples of IOW's for a few generic process units are included in Appendix A. A suggested tabular recording of IOW's is shown in Appendix B, including the IOW parameter, the related damage mechanisms, the required response, the timing of the response, related information and responsible party. An example IOW work process for a hypothetical exchanger is shown in Appendix C. 8. IOW Development 8.1. A site procedure should document the IOW work process. It should contain the following elements: implemented by a multidisciplinary team of SME's, roles, responsibilities, and qualifications for team members, required data and information to be reviewed and its accuracy, completeness of design and operating analysis, integration with existing PSM and operational programs, how the IOW's are to implemented in the field, how the IOW's will be documented, September 23, 2011 Page 23 API RP 584 Integrity Operating Windows handling of suggested monitoring instrumentation/controls and/or sampling points, how IOW exceedances will be communicated and to whom, and any required follow up or investigation of exceedances. 8.2. In order to develop the necessary information, identify potential degradation mechanisms and failure scenarios along with consideration for future operating conditions and business objectives, the combined efforts of a multi-disciplinary team of SME's is recommended. Typically this team would consist of: - Site corrosion engineer/specialist, - Unit process engineer/technologist, - Unit inspector, - Experienced unit operations representative(s), - Unit Maintenance / Reliability Engineer (as needed, ad hoc), - License Technology Specialists, as needed - Process Chemical Treatment Vendor (as needed, ad hoc), and a - Facilitator knowledgeable in the IOW work process. 8.3. The qualifications of the team and the quality of the development process and therefore the quality of the IOW's produced is dependent upon collaborative effort from the interaction of this group of knowledgeable, experienced SME's. 8.4. Considerable information is needed by the SME's on the IOW team in order to do a comprehensive job of constructing each unit specific set of IOW's. In order to facilitate the effectiveness and efficiency of the IOW work process, this information should be collected and brought to the IOW team meeting to the extent possible. This information typically includes: - Process and reactive chemistry knowledge, - Process flow diagrams to systematically review the process during IOW team meetings, - P&ID's that show sample points, IOW monitoring instruments, etc., - Piping isometric drawings that show all injection points, mix points, deadlegs and other piping hardware details that are included in the inspection program, - Existing operating windows that may already be in effect, - Identification of startup lines, temporary use lines and normally closed valves, - Operating and maintenance procedures, - Process chemical treatment programs - Feed sources, volumes, and compositions including intermediate products, - Knowledge of damage mechanisms, possible and probable that could occur in the process unit, - Historical operating, maintenance and inspection records for the process unit, September 23, 2011 Page 24 API RP 584 Integrity Operating Windows - Failure analysis and lessons learned reports for the operating unit and/or similar operating units - Equipment / process design data; laboratory data; operating data for the process unit (note the emphasis on data rather than "impressions" or SME judgment), - Start-up, shut-down and unusual operating conditions - MOC records for the operating unit, - Existing sample points and sample data - Existing process variable controls and measurement points e.g. PI's, TI's, analyzers, FC's, etc. - Metallurgical and corrosion information and data, (published and company private) related to the damage mechanisms anticipated for the process unit, - Materials of construction and materials engineering knowledge, including CMD's, - Operating knowledge, - Applicable industry and company recommended practices and standards, - Process and corrosion modeling tools, - Original unit feed composition. 8.5. Examples of unit specific process data that can be used during the IOW process include: - Crude units: Historical crude assays, average sulfur composition for the raw feed and primary cuts or product streams, total acid numbers, furnace monitoring data (IR and process temperatures), side-stream temperatures, overhead process parameters such as velocities, pH, choride contents, crude salt content, desalter efficiency and reliability, caustic injection rate (and strength) into desalted crude etc. - Hydroprocessing units: hydrogen, hydrogen sulfide and ammonia partial pressures, wash water volumes, injection points, and sources and quality of water, etc. - Amine systems: type of amine, loading, filtration, overhead bleed/purge rates, chloride content, HSAS content, % water in amine, steam temperature of amine reboilers, etc. - Catalytic Crackers: Polysulfide injection systems, slurry solid content, HCN and carbonate concentration in Gas Plant System, etc. - Claus Sulfur Units: Acid gas feed temperature, temperature of cold wall thermal reactor, temperature of final condenser outlet temperature, acid gas loading, sulfur levels. - Sour Water Strippers: Concentration of NH3 in Circulating Reflux - Merox Units: Sodium content of DSO, air controls - Selective Hydrogenation Unit: Di-Olefins content - Sulfuric Acid Alkylation: Spent acid strength to storage, acid strength, acid temperature, water content of acid, acid/hydrocarbon ratio in contactors, Contactor Isobutane/Olefin ration, Acid Precipitator Amps & Voltage, Acid Circulation rate to DIB Feed Acid Wash, DIB Acid wash mix valve pressure differential, Caustic strength of Alky DIB Caustic Wash. - Hydrofluoric Acid Alkylation: - water content in acid, isostripper and depropanizer temperatures, defluorinator breakthrough monitoring - Catalytic Reformer: Furnace temperatures, H2S content of reformer recycle gas, Water content of recycle gas, HCl content of hydrogen exiting the hydrogen HCl scrubbers. September 23, 2011 Page 25 API RP 584 Integrity Operating Windows - Delayed Coking Unit: Sodium in feed, TAN, Velocity in Coker Heaters, 9. General Considerations for Establishing IOW's and Their Limits 9.1. Historical integrity and reliability problems as well as changes that are anticipated in the process unit should be considered in the IOW development. 9.2. There may be upper and lower limits that need to be established and there may be one or more levels of those limits with different actions within different time frames required as each IOW level is exceeded. It will be up to the IOW team to determine whether each IOW needs to have both upper and lower limits, and if standard and/or critical limits need to be established for each IOW. Not all IOW's will have critical limits, and many may have only an upper or a lower limit. 9.3. Actual operation sometimes deviates from design for various reasons. Those differences can cause accelerated or unanticipated degradation with undesirable consequences. Those deviations must be considered. 9.4. There are numerous documented cases within the industry of accelerated corrosion and cracking under adverse conditions that range up to a few inches per year (see Table 3 for examples). The materials/corrosion specialist needs to be aware of this type of information to help the team decide what the appropriate operator response needs to be and how fast the actions need to be implemented. Table 3 Examples of Accelerated Corrosion Rates That Can Occur Under Some Circumstances Unit: Corrosion / Damage Documented Out-of- Time to Failure Mechanism Control Corrosion Rates Crude Unit: HCL / Amine Chloride >2,000 mpy Failed a new exchanger bundle in 18 days Corrosion in Ovhd & TPA Reformer: HCL / Ammonium >3,500 mpy New alloy finfan exchanger failure in 3 Chloride months, related to over injection of PERC and low operating temperatures Catacarb Unit: Wet CO2 >5,000 mpy Failure can occur in days to weeks on the piping at a dew point FCC Unit: Erosion of slurry system >1,000 mpy Multiple failures in slurry pumps and piping piping within 6 weeks after suspected cyclone failure Alkylation: H2SO4/ Acid Esters >15,000 mpy Failure occurred in 11 days on a new pipe reducing elbow where H2SO4 was diluted with H2O + CL HDS; HCL/Ammonium Chloride >300 mpy Failure occurred at a piping mix point combining H2+Cl and wet HDS H2 in approximately 2 years September 23, 2011 Page 26 API RP 584 Integrity Operating Windows 9.5. Numerous issues can cause deviations between actual and design operating conditions, including fouling of exchangers in series, operating with exchanger by-passes open, process conditions creeping upward without notice, lack of understanding of the nature and consequences of unanticipated degradation, misunderstanding between construction code design conditions and material of construction design limits for specific types of degradation, and not recognizing the impact of end-of-run (EOR) conditions versus normal or start-of-run (SOR) conditions. 9.6. For example, if there are banks of heat exchangers in series in high temperature, high pressure hydroprocess service, designers sometimes assume design operating conditions will prevail over the life of the plant. However, if the inlet exchanger in the series fouls and no longer cools the hydroprocess stream sufficiently, the next exchanger(s) in the series might see higher temperatures than it was designed for, in which case it might become susceptible to HTHA, sulfidation or low temperature damage mechanisms like ammonium chloride corrosion, for which the materials of construction in the downstream bank may not be designed to handle. Another situation occurs when process conditions begin to creep upward or downward over time; also known as "process creep". This might entail scenarios such as periodic, but small increases in temperature, small increases in hydrogen sulfide content, increases in unit throughput or increases in hydrogen partial pressure. Another example of process creep is the incremental in unit through-put over time that eventually exceeds design conditions and can result in accelerated erosion/corrosion. If those changes are not noticed, or not put through a management of change process, or if the proper IOW's were not in place, then unanticipated and therefore undetected materials degradation could occur. 9.7. If for some process reason, operators open a by-pass around an upstream exchanger causing hotter hydroprocess material to enter downstream equipment that was not designed for those hotter conditions, then again unanticipated and undetected materials degradation could occur, as for instance HTHA or sulfidation. 9.8. In some hydroprocess equipment, EOR conditions (e.g. temperature and hydrogen pp) are more severe than SOR or normal operating conditions. If actual EOR operating conditions were more severe and/or lasted much longer than original design or normal operating conditions, that could result in exceeding the HTHA resistance of the materials of construction. 9.9. The number of IOW's for each process unit will depend: number and extent of damage mechanisms anticipated and likely to be present, risks associated with the process fluids, complexity of the process unit September 23, 2011 Page 27 API RP 584 Integrity Operating Windows the extent of corrosion resistant materials of construction. 9.10. The numbers of IOW's for a typical process unit might range from 20 to 60 depending upon the above issues. These would be in addition to other operating windows that may affect process unit control and product quality, but have nothing to do with equipment integrity. Except for the least complex and least corrosive process units, if there are a relatively low number of IOWs identified for a particular process unit, some important process variables may not be captured in the IOW list. 9.11. The result of analyzing all this information and the team deliberations is typically a set of reasonable, practical IOW's that are not too conservative and not non-conservative, both extremes of which are not desirable and need to be avoided. Non conservative IOW's could lead to more degradation than desirable or anticipated and therefore higher risk; whereas IOW's that are too conservative could lead to a waste of valuable resources and lost opportunity. For example, establishing a furnace tube-skin temperature limit that is too high may not allow the operator enough time to adjust firing conditions before tube damage occurs; whereas, setting a tube-skin temperature too low may lead to limiting furnace operating conditions (and therefore LPO), where it is unnecessary to do so from at materials engineering standpoint. 9.12. Five to ten percent of the total IOW's may end up being designated by the team as "critical limits", where the operator will need to take immediate action to control the process or shut down, while most of the IOW's are designated as "standard limits", where the operator needs to take action within a specified timeframe to get the process back within the IOW limits in order to avoid escalation of the issue to a critical limit. 9.13. Exceedances of critical IOW limits may have more formal communications and more extensive reporting such as plant management. Responses to critical limit exceedances may require some formal investigation and reporting, and be treated similar to an incident investigation, whereas, standard limit and IIL exceedances may require reporting only to technical and inspection personnel for follow up and investigation. If systems are available, automated communication of IOW exceedances from on-line control and information systems directly to designated stakeholders can improve the effectiveness and efficiency of the IOW communication process. 10. Documenting, Implementing and Training on Established IOW's 10.1. Effective implementation of the IOW list is equally as important as establishing IOW's, so that effective actions within a specified timeframe are taken each time an exceedance occurs. A comprehensive list of IOWs should be readily available and communicated to affected personnel, which could typically include: September 23, 2011 Page 28 API RP 584 Integrity Operating Windows Operations personnel, Operations Supervision / Management Business / Oil Movements Inspection personnel Process engineers Reliability engineers Corrosion/materials specialists Safety / PSM / Environmental personnel 10.2. There can be several methods to document each set of IOW's. Two examples are shown below, one being more detailed (and thereby more useful from a broader perspective) and another being a simpler, more concise (but less useful from a broader perspective). 10.3. A More Concise Method: Simply compile a list of IOW's for each process unit including: The specific limits established, The recommended operator intervention/control steps, The timeliness of each intervention/control action, and Required IOW exceedance communications 10.4. A More Detailed Method: Include the IOW's as part of a comprehensive document on corrosion control in every process unit. These documents have been called Corrosion Control Documents (CCD's), Corrosion Control Manuals (CCM's), or Risk-Based Inspection (RBI) Data Files by some in the industry. These documents may include, but are not limited to: Description of the process unit and the normal process conditions, Shutdown, start up, and abnormal operating conditions that may affect corrosion and other degradation mechanisms, including the possibility of inadvertent contamination of process streams with unexpected but possibly predictable corrosive species, Process Flow Diagrams (PFD's) showing all construction materials, Corrosion Loop Diagrams (CLD's) which are areas of similar corrosion mechanisms, similar operating conditions, and similar materials of construction in each portion of the unit, Probable damage mechanisms in each corrosion circuit, where each damage mechanism is expected to occur, the relative susceptibility to the damage mechanisms, as well as likely damage rates expected to occur and under what circumstances, A history of corrosion problems that have been experienced in this process unit or similar units, Quantitative and predictive models for the degradation mechanisms, September 23, 2011 Page 29 API RP 584 Integrity Operating Windows Corrosion control procedures and practices such as those dealing with chemical injection, inhibitors, water washing, neutralizers etc., Recommended types of inspections focused on specific damage mechanisms, corrosion monitoring, process parameter monitoring process changes, construction materials, etc., Basis for each IOW, including any assumptions made, Risk analysis performed to prioritize the various IOW's and their associated monitoring methods, and of course The applicable IOW's that include the information in the simpler format above for recording IOW's. The more detailed documentation methods can become a resource for: The entire corrosion and degradation management strategy for the process unit, The implementation effort for all IOW's that will be input into the process monitoring and control system, Training and reference material for operators, engineers, inspectors and others that need to know the background for why each IOW was established, especially when considering possible changes, Risk-based inspection planning, Management of change decision-making that may affect equipment integrity, and Process hazards analysis (PHA) discussions. 10.5. Various combinations of the above two documentation methods can be developed depending upon the needs and desires of the owner user. 10.6. An important part of IOW implementation is training. Once IOW's are established, unit personnel need to become knowledgeable about all the unit-specific IOW's in their operating area, and especially knowledgeable in the reasoning behind them, so they can understand why it's so important to take the predetermined action within the specified timeframe. They also need to understand the undesirable consequences of failing to take action within the specified time frame. This operator training should include such things as: Why the IOW was established i.e. its purpose and intent, What damage mechanism is being prevented or controlled by the limits established, A clear understanding of the difference between informational, standard and critical limits, as well as the reason for the different response actions and timing, If there are multiple levels of the IOW's, i.e. upper and lower, as well as multiple levels of responses and response timeliness, then the reasons for each level of response needs to be fully understood, What can happen in the process unit, both short and long term, if the established responses are not implemented in a timely fashion when limits are exceeded, September 23, 2011 Page 30 API RP 584 Integrity Operating Windows The desired exceedance communications, by what mechanism and with whom to communicate, in the event that an IOW limit is exceeded. 10.7. Training should include describing the difference between Code design conditions (pressure and temperature) and materials selection design conditions. There sometimes is a misunderstanding regarding the differences between the design conditions stamped on the nameplate of the equipment and the actual process operating limits of the equipment based on degradation mechanisms. The mechanical design limits for pressure and temperature per ASME Code construction stamped on the vessel may be much higher than the operating limits established for materials of construction degradation resistance. This difference is one of the many reasons that IOW's are needed. 11. Monitoring and Measuring IOW Parameters 11.1. To monitor and measure IOW parameters, control systems and procedures are necessary to store the IOW's and notify the operator when an exceedance has occurred. That will likely involve additional monitoring and control instruments and/or sampling points for some IOW variables. If it's a monitoring instrument, then instrumented displays and some alarms will likely be needed. If it's a sample point, then procedures and practices will be needed to analyze a designated process stream and report it back to the operator within a predetermined amount of time so that the appropriate actions can be taken in the event of an IOW exceedance. Some systems generate trending data for IOW's and automatic electronic notifications to a predetermined list of stakeholders. 11.2. The overall response time of the system needs to be considered when setting alarm, and "notification" limits / levels. The response time needs to account not only for the limitations on the instrument / detector response but the overall design and limits of the communication system (getting the message to the intended audience). System response time is the length of time from when a limit has been violated until the mitigation procedure is activated. This time will be a function of system deployment, device response time, and activation strategy. System response time should be scaled relative to the risk level for critical and standard IOW's. The physical characteristics of the instrument and detection system also need to be considered. It is important to note that device response time may be significantly affected by ambient conditions. 11.3. In most cases, alarms will normally accompany all critical IOW's and some standard IOW's, depending upon necessary timing of IOW response. Process safety management may need to review the total number of alarms to avoid situations involving "alarm flood" in the event of an emergency. Notifications to specified September 23, 2011 Page 31 API RP 584 Integrity Operating Windows stakeholders/SME's should accompany critical and selected/specified standard and informational IOW's. 11.4. Sample points may be an interim process monitoring application where more data is needed to understand the process parameter and refine required frequency of measurement or sampling in order to justify the installation of future control or measurement instrumentation. 11.5. For some IIL's, several types of corrosion monitoring methods may be used, including: corrosion coupons, corrosion and hydrogen probes, and infrared thermography. 11.6. Appropriate monitoring equipment should be specified and installed at strategic locations to provide the information necessary to determine if an IOW exceedance may be occurring. 11.7. Typically an agreed upon list of IOW's will involve capital investment for monitoring and sampling systems and/or increased workload for laboratory analysis. This is because adequate monitoring and control systems may not be in place for each necessary IOW that has been established. Risk analysis and risk ranking is useful for prioritizing those investments and comparing them to all other capital and expense needs of the plant. 12. Updating IOW's 11.1 Periodic team meetings between Operations and SME's may be useful to monitor the status and update the IOW list. 11.2 The IOW list should be updated as needed to account for process and hardware changes (recent and planned), exceedance feedback, inspection results, new information about degradation mechanisms, or perhaps even a variable or degradation mechanism or additional IOWs that were identified after the original IOW list was established . 11.3 The MOC process should be applied whenever Critical or Standard IOW variables are being revised or updated, utilizing the same types of experienced SME's that were used to generate the original IOW list. A modified, streamlined MOC process specifically addressing IOW updates could be developed by owner-users. 13. Roles, Responsibilities and Accountabilities for IOW's 13.1. Numerous personnel at the plant site have roles and responsibilities for IOW creation, implementation, and maintenance including those in: Inspection Corrosion/materials September 23, 2011 Page 32 API RP 584 Integrity Operating Windows Operations Process engineering/technology Plant management Process Safety Management Laboratory Control systems Mechanical and/or reliability engineers 13.2. Inspection personnel have a role bringing data to the IOW team for creating and updating IOW's, as well as adjusting inspection activities as necessary when IOW exceedances are reported to them. 13.3. Corrosion/materials specialists have a role to identify damage mechanisms for the IOW team. A corrosion/materials specialist should also supply the CLD's/CMD's (where they are available), and estimated corrosion rates where measured rates for the current operating conditions are not available. They also have a role in understanding exceedances and advising inspection personnel on how inspection activities might need to be revised to account for the exceedance, if any, as well as advising process engineers on process issues that may need to be considered to avoid long term materials degradation issues. A corrosion/materials specialist will often have the role and responsibility of facilitating the IOW team, as well as documenting and distributing the results of the IOW work process. The corrosion/materials specialist may also have a role in providing operator training on IOW's. 13.4. Operations is responsible for providing information about current operating practices and providing operational data to the IOW team. They will also have information about the frequency of upset conditions. But their main role is in monitoring and responding to any IOW exceedances in the manner designated in the IOW control system and documentation. This would include obtaining water and process samples which have been identified as IOW monitoring points. Additionally operations have the responsibility to communicate any IOW exceedances in the designated manner to other designated stakeholders for their potential actions. 13.5. The unit process engineer has the role of bringing process design and engineering data to the IOW team. Often the unit process engineer is the designated "owner" of the IOW list and responsible to ensure that all IOW's are properly and continuously implemented in the manner designated in the IOW documentation. The owner of the IOW work process would also have the responsibility to ensure that exceedances were properly reported to others and a role in responding to exceedances and ensuring that responses to exceedances were handled and implemented in a timely manner. 13.6. Plant management has the role and accountability of ensuring that the IOW work process is adequately staffed with knowledgeable, experienced SME's, that the work process is carried September 23, 2011 Page 33 API RP 584 Integrity Operating Windows out in a timely manner, that all IOW's agreed upon are implemented in a timely manner, and that adequate resources for monitoring, sampling and control systems are designed, purchased, installed and implemented. Plant management would also have the responsibility to audit the IOW work process to ensure that it is operating in accordance with specification. Operations management would have the responsibility to ensure that all unit operators are adequately trained on IOW's and their required responses to exceedances. 13.7. PSM personnel have a role and the responsibility for ensuring that the IOW work process is adequate to meet the process safety information (PSI) aspect of local and federal regulations, as well as ensuring that the MOC process is properly utilized for making changes to the IOW list. 13.8. Laboratory personnel have a role in implementing, recording and reporting any required sample analyses used for IOW monitoring in a timely manner, per the IOW documentation. 13.9. Control systems personnel would have a role and the responsibility for designing, purchasing, installing and maintaining any control and monitoring systems for IOW's. 13.10. Mechanical and/or reliability engineers also have a role in identifying previous equipment failures and experiences. 13.11. The IOW team facilitator is often best accomplished by an experienced corrosion/materials or mechanical integrity specialist, either from the plant, a central office, or a third party. One of the facilitator's roles should be oriented toward eliciting information about what is actually happening in the field relative to what is in the documented records or what is "thought to be happening" by those who are not operators. The facilitator needs to have the skill for asking the right probing questions in order to fully understand issues that may impact the IOW work process. 14. Integrating IOW's with Other Related Work Processes 14.1. The IOW work process should be closely integrated with pressure equipment integrity (PEI) work processes (inspection, corrosion management and maintenance) at the plant site. As indicated in the introduction, the pressure equipment integrity work process can only be adequately accomplished when both work processes (PEI and IOW) are performing effectively with close interaction between the two work processes. 14.2. The IOW list and documentation should be a resource for PHA reviews and IOW team members should be ad hoc members of the process unit PHA review team. IOW exceedances especially critical IOW exceedances should be reviewed by the PHA team (or as pre-work by the IOW team) to determine if actions or limits may need to be revised. September 23, 2011 Page 34 API RP 584 Integrity Operating Windows 14.3. The IOW work process and documentation should also be a resource for the RBI work process, (and vice versa) especially since both require the same level of analysis of potential damage mechanisms. In fact, an IOW workshop and RBI workshop could be combined where there is complete overlap in resources and timing of the two programs. The analysis of IOW exceedances may affect the inspection plans generated by RBI, or any other modes of inspection planning, including time-based and condition-based inspection plans. The information assembled to produce the more detailed IOW documentation mentioned in 10.4 can become part of the front end data input to the RBI process, which would in turn produce a detailed risk-based inspection plan for each piece of fixed equipment including: inspection scope, methods, techniques, coverage, frequency, etc. API RP 580 and 581 are the two API Recommended Practices that address Risk-Based Inspection. API RP 580 is the generic boundary document detailing everything that needs to be included in an effective and complete RBI work process; while API RP 581 is a specific step-by-step work process for doing RBI which includes all the elements of API RP 580. 14.4. As indicated in section 1.3 and 11.3, the MOC work process must be closely integrated with the IOW work process for any changes, additions or deletions to be made to the IOW list. September 23, 2011 Page 35 API RP 584 Integrity Operating Windows Appendix A: Examples of Potential Process Parameter's for IOW's for Generic Process Units Example list of a few parameters for potential IOW's for a generic amine process unit Amine concentration Water content Rich amine acid gas loading Lean amine acid gas loading Regenerator steam to feed ratio Velocity in rich amine piping Reboiler steam temperature Lean Amine temperature from the bottom of the regenerator Heat Stable Salt (HSS) concentration Iron content in circulating amine Sour water velocity from regen O/H condenser to reflux drum Amount of reflux being purged (% vol) NH4HS and CN levels in the overhead Temperature of acid gas piping to SRU Total suspended solids Example list of a few parameters for potential IOW's for a generic crude distillation unit Crude furnace tube skin temperature limits Crude furnace outlet temperature, minimum pass flow and stack temperature TAN limits on crude feed and cuts Pressure drop across furnace coils Salt/chloride content in feed streams Inlet/outlet temperatures in feed preheat exchangers Sediment content of feed streams and desalted crude Water content of feed and various process steams Desalter wash water rate pH, O2 and NH3 contents of desalter water Desalter efficiency, operating temperature and outlet salt content Hydrolysable and organic chloride limits downstream of desalter Caustic injection rate in the desalted crude Various distillation column top temperatures Overhead wash water rate Filming and neutralizing amine injection rates pH in water boots Iron, sulfates, chlorides, ammonia, tramp amine and hardness in overhead water boots September 23, 2011 Page 36 API RP 584 Integrity Operating Windows Tramp amines in straight run naphtha and kerosene Oxygen ingress in vacuum systems Inlet/outlet temperatures for specific exchangers Example list of a few parameters for potential IOW's for a generic hydroprocess unit TAN, nitrogen, chlorides, fluorides, sulfur and water contents of feed streams Water content at outlet of coalescer HCL content of hydrogen makeup Chloride content of feed Inlet/outlet temperatures for specific exchangers Tube skin temperatures, stack temperature and minimum pass flow rates for hydroprocess heaters Hydrogen purity Reactor bed temperatures and pressure drops Wash water flow rates Cold separator sour water NH4HS and Chloride contents O2, iron, ammonia, chloride and calcium in injected wash water NH4HS content Hydrogen sulfide content in effluent, recycle gas and high pressure separator overheads Water carryover into fractionation and side strippers Fractionation overhead chemical injection rates and carrier flow rates Fractionation overhead sour water NH4HS and chloride contents Maximum temperature and pressures for start-up and cool down of reactors Example list of a few parameters for potential IOW's for a generic sulfuric acid alkylation process unit Water content of feeds and coalescer outlet Feed make up oxygenates, sulfur, and non-condensables Coalescer water boot pH and temperature Water in acid in reaction system and velocities in carbon steel piping Reactor temperature and contactor motor amps Settler operating pressure Effluent Exchanger outlet temperature Acid precipitator amps & voltage Acid loss and polymer production Fresh, circulating and spent acid strength Temperature and caustic strength in caustic wash system Temperature and velocity maximums for carbon steel piping in caustic wash system Acid and caustic carry over September 23, 2011 Page 37 API RP 584 Integrity Operating Windows Water boot pH Delta P in some exchangers (salt deposition) Example list of a few parameters for potential IOW's for a generic steam methane reformer unit Feed gas condensate pH H2S content of feed gas (if refinery gas is used) Hydrotreater & Desulfurizer – Temperatures and hydrogen partial pressures Heater furnace tube temperatures Heater steam to carbon ratio Temperature of syngas to low temperature shift reactor and PSA Chloride and ammonia (e.g. brass tubes present) content of process condensate Corrosion inhibitor limits in hot potassium carbonate solutions Example list of a few parameters for potential IOW's for a generic fluid cat cracker unit Catalyst hopper temperature Expansion joint maximum temperatures Fractionator bottoms slurry content, temperature and sulfur content Volumetric flow for cyclone underflows Delta P for slurry pump suction strainer Gas oil temperatures and sulfur maximums Fractionator overhead top temperature Fractionator wash water and polysulfide rates Fractionator overhead pH, ammonium bisulfide, sulfides, carbonates and chloride content Wash water rate for wet gas compressor interstage condenser Wet gas compressor interstage separator boot pH, sulfides, ammonium bisulfides, chlorides, and cyanides Example list of a few parameters for potential IOW's for a generic delayed coking process unit TAN, total sulfur and sodium of Coker feed Coker furnace tube-skin temperatures Pressure drop across furnace coils Rate of velocity steam Injection or process flow rate through radiant coils Rate of water injection in fractionator overhead, compressor interstage and compressor final stage September 23, 2011 Page 38 API RP 584 Integrity Operating Windows Ammonium polysulfide activity in injected water. Ammonia, iron, cyanide, carbonate, chloride, pH in water from fractionator overhead accumulator and compressor discharge receivers. Calculate ammonium bisulfide. Water fraction in stripper bottoms product and rate of water draw off of stripper water separator. Velocity in sour water piping. Maximum diffusible hydrogen in the compressor drums and absorber Water fraction in debutanizer overhead product and rate of water draw off in debutanizer overhead receiver September 23, 2011 Page 39 API RP 584 Integrity Operating Windows Appendix B: Sample Format for Recording IOWs Equipment Parameter to IOW type Comments/Reasons/Actions/Timing Party(s) Responsible and/or be monitored and limit for monitoring, process or controlled control and stream response actions (who does what) e.g. FCCU feed, e.g. e.g. Standard e.g. Explain why the parameter is being measured e.g. process engineer, fractionator OH, temperature, max and what can happen if it is exceeded. Explain operator, chemical slurry system, chlorides, how the operator needs to respond and how fast. treatment vendor, reactor, heat sulfides, water Standard min Explain how the parameter is to be measured and corrosion specialist, exchanger content, how frequently. Explain who is to be notified in etc. Critical max outlet, chemical cyanides, salts, the event of an exceedance. injection, etc. flow rates, etc. Critical min, etc. Informational Target range September 23, 2011 Page 40 API RP 584 Integrity Operating Windows Appendix C: Example of an IOW Development for a Heat Exchanger IOW's are typically developed on a unit basis or for an entire system, but in some cases are associated with a specific equipment item. The following example highlights how an IOW might be formulated for one exchanger. In this hypothetical example, a Crude Unit Fractionator Tower bottoms exchanger (X-1) is potentially under alloyed for future service (sulfidic corrosion concern). Based on the current feed slate to the unit, the actual measured corrosion rate is acceptable, but the refinery is planning to process additional higher sulfur crudes in the near future. This exercise will look at the data development and thought process involved to set appropriate IOW's for this hypothetical exchanger. Step 1 – Define the Operation This Crude Unit has been receiving a steady diet of blended crudes containing 0.37 % total sulfur with a TAN averaging 0.75. This X-1 exchanger is utilized in the Atmospheric Gas Oil (AGO) stream (although it can also be used in Atmospheric Tower Bottoms (ATB) service) and has an operating temperature at 650 degrees F with little to no temperature variation. There is a desire to increase the total sulfur in the AGO in the future from 0.37 up to 0.50 wt% and trial operating runs are currently planned. The next full outage that would provide an opportunity to inspect, repair or replace this exchanger is 5 years from the proposed change. Step 2 – Corrosion / Damage Mechanism Identification The X-1 exchanger was fabricated from carbon steel on the shell side (receives an AGO or ATB stream) and operates at 650 degrees F with an estimated 0.75 wt% sulfur (total). The primary damage mechanism of concern is sulfidation; naphthenic acid has not been a concern in this Unit. The estimated corrosion rate potential utilizing the Modified McConomy Industry curves is approximately 25 mpy (the current measured corrosion rate is only 10 mpy). Differences between the theoretical/potential rate and the measured/observed rate are likely due in part to the amount of reactive sulfur available in the specific Crude slate. The metallurgy for this exchanger is may be under-designed for the new application. Changes in the crude slate which will increase the amount of reactive sulfur may produce significant changes in the corrosion rate even with the same/similar total sulfur concentration in the tower bottoms stream. Step 3 – Determine the Parameters that will affect the Reliability of this Equipment (Long Term) Crude Slate / Blend Total Sulfur at AGO Cut Reactive Sulfur at AGO Cut Total Acid Number (TAN) at AGO Cut September 23, 2011 Page 41 API RP 584 Integrity Operating Windows Operating Temperature (and time if variable) at X-1 Shell Velocity of Process Fluid Step 4 – Define the Critical Operating Parameters (measurable & controllable) Sulfidic corrosion is a co-dependent process that is based on the amount of reactive sulfur present and the temperature for a given material of construction. Sulfidation rates may be accelerated by naphthenic acid and velocity of the process fluid both which act to remove the protective iron sulfide scale that develops as a process of sulfidic corrosion. In general the refinery does not measure or monitor reactive sulfur species but relies on total sulfur measurements. There is a moderate to high corrosion rate potential based on a theoretical analysis. The operating temperature and total sulfur content of the AGO stream are the primary operating parameters that will be targeted (controllable by the crude slate being run). Total Sulfur at AGO Cut (primary IOW) Total Acid Number (TAN) at AGO Cut Operating Temperature (and time if variable) at X-1 shell Step 5 – Safety Factor Basis (Considerations) Currently this exchanger has a calculated remaining life of 10 years based on the historical measured corrosion rate. Utilizing the estimated corrosion rate of 25 mpy the remaining life drops to 4 years. Since the primary crude slate will not change significantly, only small additions of higher sulfur crude will be added into the overall mix, the corrosion rate is not expected to vary significantly from the historical measured rate. Based on these factors, a 2X (or ½ life) safety factor was selected as the basis for limiting the sulfur and temperature of operation for the IOW. Step 6 – Set Limits on the Critical Reliability Operating Parameters Based on a desired operating period of 5 years (Turnaround interval) with a 2X safety factor, the remaining or usable corrosion allowance is 0.100". From a fixed operating temperature of 650 degrees F, the total sulfur amount in the AGO stream needs to be limited to 0.30 wt% in order to ensure reliable operation over the specified operating period. This limit then becomes an IOW for the X-1 exchanger. September 23, 2011 Page 42
views: | 385 |
posted: | 2/17/2012 |
language: | English |
pages: | 42 |


text:
I Want To...
Download Permits & Forms »
Find City Court Info »
Find Next Brush Pickup Date »
Report Traffic Issue »
Retrieve Impounded Vehicle »
Good Neighbor of the Year Award to be Announced Saturday »
Art in Public Places Works to be Installed »
East Knoxville Bicycle Route to Knoxville Zoo is Complete »
Take A Stand Against Bullying Event April 17 »
Cumberland Avenue Overhaul to Start This Summer »
Public Meeting on Mobile Food Vendor Pilot Program »
Tree Care Firm, City Protecting Ash Trees in Parks »
Civil Rights Act Anniversary »
Mayor Rogero Joins Community Leaders in Violence Prevention Efforts »
Market Square Project to Protect '6 Gorgeous Oak Trees' »
Cumberland Connections Blog »
Engineering Department Project Blog »
Like the City on Facebook® »
Follow the City on Twitter »
View Press Releases »
Click Here for Printer Friendly Version
City of Knoxville, Tennessee
Madeline Rogero, Mayor
Vote Now for Movies on the Town
August 18, 2008
- It's time for "Movies on the Town", a FREE outdoor movie series brought to you by the Knox County Public Library. Movies will be shown at the World's Fair Park on September 5, 12,19 and at Market Square for October 3, 10, and 17.
The fun starts at 7:30 p.m. with pre-show entertainment and the movies kick off at dusk. So get your blanket or lawn chairs in tip-top shape and prepare for a night in front of the silver screen!
Vote for the movies you want to see
Choose up to 6 of your favorites or write one in. Voting starts August 13 and runs through August 25 and the winners will be announced on August 28.
Vote now!
All movies will be PG 13 or less. You should check out reviews to make sure the movie is right for your family.
What's the schedule?
Pre-show entertainment starts Fridays at 7:30 p.m., and movies start around 8:30--as soon as it's dark enough!
World's Fair Park: Fridays, September 5, 12, and 19
Market Square: Fridays, October 3, 10 and 17
Where are the movies?
This year, they're in two different locations--the festival lawn at World's Fair Park and on Market Square. The movies in September will be at World's Fair Park, and those in October will be at Market Square.
Where do I park?
Free parking is available at the World's Fair Park parking lot, the Market Street Garage, the Locust Street Garage, the State Street Garage, and on the street.
View a downtown parking map here [PDF].
What's at World's Fair Park?
You'll be able to go for a splash in the giant fountains (bring a towel!) before the movie. You can grab food from downtown on your way, or check out the hot dog vendor, and enjoy a picnic on the biggest lawn in town--and there are even real bathrooms!
Can I bring my dog?
Dogs are invited to join us at the Park, as long as they bring their best doggie manners and stay on their leashes. Please be considerate of other movie goers. If your little furry friend is prone to woofing, howling, or other expressions of joy, we'd hate to see you end up in the dog house. Oh, and bring one of those fashionable little plastic bags--just in case.
Add to Favorites
Adobe PDF Reader
Email Page
Font Smaller
Font Normal
Font Larger
Get Directions
Make Home Page
Print Page
RSS/XML Feed
Search A to Z List
Site Map
Traduzca en Español
Translate to More Languages
Knoxville Weather Forecast, TN
Dial 3-1-1 For City Services
City Departments
Communications »
Community Development »
Community Relations »
Engineering »
Finance Dept. »
Fire Dept. »
Law Dept. »
Mayor's Office »
Parks & Recreation »
Plans Review/Inspections »
Police Dept. »
Policy & Redevelopment »
Public Service »
Special Events »
Sustainability »
List of All Depts. »
Phone List »
Copyright © 2013 City of Knoxville |
Read Our Privacy Policy
Email Webmaster
City County Building, 400 Main St, Knoxville, TN 37902 | Phone: Call 3-1-1

subset: commoncrawl


text:
Wiki Headlines 12th Mar: Page-bottom layout change on the way. Details here. Causes no change to editing/formatting of articles. This is just FYI.
YMMV main index Narrative
Find it here! Or here!Gundam Seed: Bloodlines is an Alternate Universe take on Gundam SEED in which Kira and Cagalli's places are reversed - Cagalli is a coordinator living on Heliopolis, while Kira is the prince of Orb. When ZAFT attacks Heliopolis, Cagalli is reluctantly forced into the role of the Strike Gundam's pilot.Early chapters pretty much follow SEED's plot, but the series begins to diverge as it goes on.
Gundam SEED: Bloodlines contains examples of the following tropes:


text:
The Richard Gray's Power Company (RGPC) PowerVault 11kW is designed for singe-home installations, but this beast can probably power up your whole neighborhood. The now-shipping system will fit right into the basement electronics and home automation equipment room or closet of your house, but it can actually reside more than half a mile away from the A/V gear, the company says.
You certainly will have zero worries about power protection in your home with the installation of the PowerVault 11kW, we know that. It works as a power conditioner, long-duration uninterruptable power supply and as a surge suppressor, and at an MSRP of $29,500, it handles those tasks like no other in the power management category.
The power output can be configured for 120V or 240V output, which works well in big home theaters with displays and amplification that need more juice than the usual 120V.
Power outages, surges and spikes won't mess with the PowerVault 11kW either, as it will continue to deliver clean and stable power for hours or days even when the utility provider cannot.
The RGPC product integrates with leading home control systems, and can even handle inrush demands of over 25kW to kickstart those hefty systems as well as high-performance A/V equipment and lighting control. The security afforded by PowerVault certainly befits its name.
Follow Electronic House on Facebook and Twitter.The 6-driver Paradigm soundbar includes Bluetooth with aptX streaming and several audio modes.
High-performance audio upgrades topped this homeowner's renovation and home automation to-do list.
Save money and make your home smarter? Here are the latest Z-Wave and Wi-Fi thermostats we're warming up to.