Node Software Issue

Definition/Typical Issues

Was there a performance gap with the software? Did the software fail to perform as desired?

Examples of items coded under this node include:

  • Access™
  • Maximo®
  • Operations applications
  • Computerized maintenance management system
  • Learning management system
  • Distributed control system

Note 1: This node only addresses software. Computer hardware issues are categorized under the Process/Manufacturing Equipment Issue (#7) node.


Examples

Example 1

  • The software control system failed to properly control a machining operation. As a result, a number of parts were improperly machined. The software did not consider an unusual sequence of steps that occurred when machining some parts.

Example 2

  • The software system failed to alert the operator to elevated temperatures on a fired heater (i.e., a heater that uses a flammable gas as the heat source). As a result, the heater was damaged and had to be replaced.

Example 3

  • A defect in a spreadsheet program resulted in a calculation error when computing heating times for a product.

Example 4

  • Some procedure steps were not printed out because of a bug in a word processor program.

Typical Recommendations

  • Work with the eventual users of the system to develop a needs specification and a design specification prior to development of the software.
  • Perform tests of the software prior to implementation.
  • Review program-user comments prior to purchasing software in order to identify potential problems.
  • Review release notes and other documentation to identify potential implementation and compatibility problems prior to purchase.
  • Update commercial software on a routine basis.
Back to top