Q&A - Software

The Contact Us function at the top of every page on the website is the preferred means for asking questions and receiving answers from the subject matter experts of the TIA QuEST Forum. Over the last few years many questions have been answered through this means. The number of each question is the ticket number in the Contact Us tracking system.

These questions apply to software products.

Question 10731 — If you have a hardware (“H”) registration do you also need to report software problems in your common measurements?

Answer — You are required to report all problem reports in the NPR submission INCLUDING software problem reports. These problem reports would also be reported in FRT and OFR.

SPR and SFQ are only reported when registrations include the “S” option for software. You would not be required to report SPR or SFQ since you only have a “H” registration.

Question 10511 — Clarification: For SFQ the counting rules that requires "Fixes addressing similar defects across multiple releases are counted separately.", does that mean if I have 1 software patch that covers 5 different releases, that counts as 5?

Answer — Yes

Question 13268 — I have questions regarding to the SFQ counting rule. 8.1.4 b) 8) states

A defective Fix meets one or more of the following criteria.
- Within the first 12 months of the fix release date:

      - cannot be installed
      - does not correct the intended problem
      - is withdrawn because of potential or actual problems

- Within the first 6 months of the fix release date, there is a critical or major problem that is a side effect found to be attributable to the fix.

Question 1: What does the 3rd bullet under the first clause mean? Does it strictly mean that the load containing this fix has to be removed from service? Or only the fix is identified as with problems, it does not care whether the load stays in service. In what situation is a fix withdrawn?

Answer — If a defective fix is made generally available whether it’s installed or not does not matter. If it’s withdrawn by the organization, it is still counted.

Question 2: Why is the second clause not already covered by the first clause?

Answer — The second clause represents cases where a fix is installed successfully, it does correct the intended problem, and does not have to be withdrawn - yet during the first 6 months after the fix release, a critical or major problem occurs. The problem may impact other functionality that the fix was not intended to impact. This is an example of a case where in the process of fixing one problem, another may be created. If a minor problem report is generated (as opposed to critical or major) during the six month, the second clause does not apply.