1. Request to clarify rationale, on API 2000 excessive thermal inbriething, got a "managerial" reply. It would probably have no response, if addressed to a local organization here. A more managerial answer ("look into the issue, solve it and inform me ") by a local small manager was once witnessed by me.
API could write the rationale of changes on every new edition, and this would be beneficial for them as well as their readers.Probably they write a brief history of changes implemented in the first page of some recommended practices? This has some resemblance to rationale, I remember ASME code has written so in the acceptance test procedure for boilers ( mentioning old PTC 4.1).
2. Cooperation of USA and Europe for practices seems to result in products probably more complete, but also more complicated. For example API RP 500, API RP 505, IP 15, concerning ATEX - Hazardous areas; or API 2000, ISO 28300, EN 14015 concerning tank breathing. Simplicity and clarity should not be disregarded in documents for engineering.
3. API issue recommends practices, needing engineering judgment to implement. The requirements for higher thermal inbreathing are undoubtedly applicable to new tanks. I suppose it depends on our judgment to apply them on existing tanks, or decide when. Probably a tank to the old API 2000 would face no problems during its life, but what about an accident due to breathing? Inspectors can support then that compliance to new API 2000 edition had been necessary. On the other hand such an accident seems remote, according to today's historical data.
4. Contrary to assumed situation as above for API, a practice established by law (e.g decree, directive) has to define whether the old one is still in force, as well as when the new practice is mandatory for existing equipment too. So situation is more clear (but API can supply more flexibility / freedom for the proper way).
5. API do not officially consider themselves accountable for omissions in previous editions. They could support that those editions complied with human knowledge and experience and acceptable safety level on the time of issue. After all "use your judgment". Even codes are developed and change in the course of time.
6. Nevertheless mentioned rationale seems to comply with the "free" spirit of API. May it be included in their future editions. This subject can be a chance to remind API organization of it. Hopefully I am not too optimistic.
Edited by kkala, 05 September 2011 - 12:00 AM.