AutoPIPE & STAAD.Pro Error Reports (Published Defect Report)Additional FAQ about access to the AutoPIPE & STAAD.Pro Error Reports.TR Number: noneProduct: AutoPIPEVersion: n/aArea: GeneralProblem ID#: 77491solution 500000092419
AutoPIPE and STAAD QA&R Error reports are available from the following resource:
As part of the sign up process to becoming a QA&R member, each company has appointed a single point of contact for all QA&R information, documentation, and shipping of new software. This single point of contact person is sent an QA&R Error Report email each month with an attached MS Excel file that contains detailed information about the current errors in the program. They also have exclusive access to viewing the same information online. Please contact this person for access to the QA&R information. They are in total control of dispersing the information among company employees. Remember that this is sensitive information and is prohibited to share with anyone outside of the a pointed company.
If you are a QA&R user, and do not know who your single point of contact person is, please send an email to the following people (see item #1 on WIKI here) asking for your company's single point of contact person(s) information.
If you are not a QA&R user, and are interested in becoming one, which includes many benefits besides viewing the QA&R error reports, please send an email to the following people (see item #1 on WIKI here) asking for details about the rewards of becoming an AutoPIPE QA&R user.
Again, only QA&R users have the added benefit of viewing the current QA&R Error reports. Otherwise, please see the following release notes installed with AutoPIPE:
Note: see following link here for opportunity to get a CofC (Certificate Of Compliance.
AutoPIPE V8i 09.06.01.xx and higher:
C:\Bentley\AutoPIPE V8i SELECTseries \ autopipe_readme.chm... after being opened see the "Error History" hyperlink under the "Local Information"
AutoPIPE V8i 09.06.00.xx and Lower:
C:\Bentley\AutoPIPE V8i SELECTseries\readme_autopipe.htm
After the file is open, see the "QA Reporting Notices" section for details. However, note that the www.Bentley.com web site mentioned in this document has been updated per the new QA&R process mentioned above.
From Nov 2014 to now, the AutoPIPE Product Manager, Luke Andrew, will issue an RSS news feed about Major and Critical issues that affect AutoPIPE's results. Check the news feed periodically for newly logged issues.
Detailed monthly error reports as well as open error summaries for respective software products will now be posted to a private QA&R Community under the Bentley Communities website. The older error reports page will cease to exist.
Note: Again, access is reserved only for those who are apart of the AutoPIPE or STAAD QA&R program.
If your company is apart of the QAR&R program, instead of having numerous people at the same company with access to this private community, a single point of contact (no more than 2 people) at each company will have already been identified and invited as a member with full access on this new QA&R Community. This is documented on the 6-1-2 form on file at both the individual company and Bentley Office. This form can only be updated by filing a new form to QA&R office. No changes to this form will occur based on verbal conversations over the phone. To find out who in your company has this access, please send an email to the "Software Quality Manager" or :"Contract or Sales" person asking for these details.
One of the many advantages about becoming a QA&R member is the ability to have 24 / 7 access to a detailed list of published errors and personal notifications sent by the QA&R manager when new Major / Critical issues occur.
QA&R users pay an extra fee each year for additional benefits (i.e. upgraded service in documentation, right to perform an on site audit, programming assurance, etc..). Most QA&R users are in the nuclear industry, and by Federal requirement must have full access to software's published errors. As mentioned above, the original AutoPIPE's and STAAD's Error reports web site has been updated to meet the new process of sending the Error Reports to each QA&R single point of contact person.
Please contact the following people (see item #1 on WIKI here) asking for details about the rewards of becoming an AutoPIPE and STAAD QA&R user.
Thank you for your understanding.
Yes and No,
For all users, to assist in the screening of the models created in previous program versions for any potential impact by a defect, the program shall automatically examine the model database after opening the model in a newer version and generate a report, listing all the potentially known issues that might impact this opened model
In addition, some of the known issues against a particular version of AutoPIPE can be viewed from the "autopipe_readme.chm" installed document, see "Option #2: Installed document" information above.
Only for users appart of the QA program have the added benefit of detailed documentation sent to the QA single point of contact mentioned above. The MS Excel file will report all open / closed issues for a particular version of the program.
Notice following columns in the MS Excel file sent:.
First Affected Version = The first AutoPIPE version that carried this error (subsequent versions were also carrying it until it got fixed)Corrected Version = The AutoPIPE version in which this error was fixed.
For an error to affect 18.104.22.168 both the following conditions should be true:
1. The corrected version is later than 9.2.3 i.e. 9.3.0, 9.3.1, 9.3.22. The 1st affected version is 9.2.3 or older i.e. 9.2.3, 9.2.1, 9.2.0, 8.9.0,…..
Note, the Excel columns can be sorted and filtered as needed.
Tested OK = Defect has been fixed and passed testing.Evaluated Fix, Scheduled = Fix is in progress
Each reported issue is give a 1 of 4 severity levels, see the following definitions:
Critical– an error is classified as “Critical” if either the following apply:A) Software operations and/or function are severely faulted that the software is “ unusable” orB) Analytically software module produces unconservative results which have been further evaluated in accordance with Quality Service Procedures as being reportable under 10CFR21.
High– a “Major” error is one which prevents the use of primary section(s) or feature(s) of the software and for which no feasible avoidance exists.
Intermediate–an “Intermediate” error is either
a) Any error which prevents the use of a primary function(s) and for which an avoidance exists, orb) Any error which prevents the completion of a secondary function and for which no avoidance exists.
Minor– all miscellaneous error of any type not included in the above categories