Hello. Sign In
Standards Store

Look Inside

UL 1998

3rd Edition, September 24, 2018

Complete Document

UL Standard for Safety Software in Programmable Components

Includes all amendments and changes through Revision Page(s) , September 24, 2018

View Abstract
Product Details
Document History

Detail Summary

Active, Most Current

Price (USD)
Single User
Call for Quote
In Stock
Add to Cart

People Also Bought These:

ISO 14229-1
ISO 20653

Product Details:

  • Revision: 3rd Edition, September 24, 2018
  • Published Date: September 24, 2018
  • Status: Active, Most Current
  • Document Language: English
  • Published By: UL (UL)
  • Page Count: 43
  • ANSI Approved: Yes
  • DoD Adopted: No

Description / Abstract:

These requirements apply to non-networked embedded software residing in programmable components performing safety-related functions whose failure is capable of resulting in a risk of fire, electric shock, or injury to persons. 

This is a reference standard in which the requirements are to be applied when specifically referenced by other standards or product safety requirements. 

These requirements address the risks unique to product hardware controlled by software in programmable components. 

These requirements are intended to supplement applicable product or component standards and requirements, and are not intended to serve as the sole basis for investigating the risk of fire, electric shock, or injury to persons. 

These requirements are intended to address risks that occur in the software or in the process used to develop and maintain the software, such as the following:

a) Requirements conversion faults that cause differences between the specification for the programmable component and the software design;

b) Design faults such as incorrect software algorithms or interfaces;

c) Coding faults, including syntax, incorrect signs, endless loops, and other coding faults;

d) Timing faults that cause program execution to occur prematurely or late;

e) Microelectronic memory faults, such as memory failure, not enough memory, or memory overlap;

f) Induced faults caused by microelectronic hardware failure;

g) Latent, user, input/output, range, and other faults that are only detectable when a given state occurs; and

h) Failure of the programmable component to perform any function at all. 1.6 Product standard requirements may amend or supersede the requirements in this standard, as appropriate. 

These requirements are not intended to address cybersecurity. Risks associated with unauthorized access or attack through a network shall be addressed in the product standard or other referenced standard such as the Standard for Software Cybersecurity for Network-Connectable Products, Part 1: General Requirements, UL 2900-1.