How to update AutoPIPE with a new piping code or a new Code Compliance Calculations?
Can I use a different edition of the same code and get the same results until the new Piping code has been added to AutoPIPE?
AutoPIPE does not support module updates. Another words, the piping codes available in each version of AutoPIPE are hard coded into the program and cannot be updated with copy/pasting a few files. A new version of AutoPIPE would need to be installed in order to see a different list of Piping codes / Code Compliance Calculations available in the program.
Note: See the following WIKI page here for a list of current AutoPIPE versions available for download. Check the release notes for all new enhancements including new piping codes that may have been added.
If you do not see a particular piping code needed for a project, log a service ticket requesting an enhancement.
Bentley TSG does not perform any kind of code evaluations between Piping Codes or different editions of the same Piping Code. Therefore we cannot comment on what code or edition should be used for your piping analysis. Ultimately it is the responsibility of the user to select a Piping Code and Edition to be used for a model's analysis.
Please keep in mind that CAE development team is constantly updating the program based on users requests and industries acceptance. It is a considerable undertaking in both time and financial investment for programming, producing all background calculation in Mathcad, & QA&R testing for each new piping code added to AutoPIPE. Therefore, it may be sometime after a code release before it will appear in the program as an option, but it all starts with logging service ticket for the enhancement
Question: When will an updated piping code appear in AutoPIPE?
Answer: The most important date is when was the code actually published, do not just consider the code edition year. In most codes (Example ASME B31.3 - 2018) there is a page near the front of the document with copyright information. This page may contain the actually publication date, example - image below from ASME B31.3 - 2018
At this point, an enhancement request must be submitted where the development team evaluates it based on importance, number of people requesting the code, development effort, and determines if it will be added to a version update project (ex. 12.1, 12.2, etc). Whenever the version update project is started, all the scheduled work will be completed and thoroughly tested before the predetermined scheduled release date. Whenever an item fails testing, it goes back to development for rework and then must be resubmitted to testing again. Sometimes this is an iterative process until it passes and can be released in a new version of the program. Otherwise, all scheduled work that does not pass testing by the predetermined scheduled release date, will be completed in the next project.
How long does this all take? it all depends on publish date, enhancement request submitting date, number of people requesting, development time, QA testing, schedule release update project cycle, etc... Best case scenario, 4-6 months after publication release date. However, if it failed testing and development is already in the middle of another project, it may take 6-9 months from date of publication before it appears in the program. Again it all depends on factors mentioned above.
As mentioned in ASME B31.3 2018, the code will NOT become effective until 6 months after the publication date. Meaning that ASME B31.3 - 2018 will not be in effect until April 2019, but this feature may be already in the program by that date. Furthermore, after being released, some codes are not immediately accepted by industry or governing bodies. It may take months or years before a code is accepted. By that time, another version may have been released.
In summary, just because a code is available does not mean it is immediately put into the program. However, it all starts with submitting an official request for an enhancement. The more people who ask for the same request and industry's acceptance will push development to get said feature into the program quicker.
Question: A particular piping code edition is not available, plant was build listing code of record = ASME B31.1 - 1971 (1973 update), options or justification for using another code without performing a code reconciliation?
The intent is not to change the Code of record with regards to the plant construction. However modifications performed to the plant 20+ years later usually can be completed if the specific project design code named was found to be more stringent / conservative than the original. Therefore suggest to analyze the project to a code edition currently available in AutoPIPE. Perform a manual evaluation of code calculations between the 2 code editions (i.e. code of record and selected code in the program). Validate any review with calculations being the same, more stringent / conservative or less conservative. Make changes to AutoPIPE's settings or allowable values as needed to meet the requirements of the project design.
Forum: when is code to be updated
Piping codes - AutoPIPE