Categories: L4-and-Maintenance

The definition of done (DoD) for L4 bugs are the checks performed when an L4 bug is considered completed.

During L4 fault tracing it may be required to send a debug release outside of PCP. This has to be handled with care as it isn't a formally released software.

In emergency situations, software corrections may be required in a short time frame to solve a critical issue on the customer site. This type of emergency correction will be handled as a temporary correction (TC).

Some minor hardware changes to products can be implemented without setting up a project. This guide describes the steps involved and the checklists that shall be used.

This guide describes the process for handling software vulnerabilities in products within PCP R&D. It includes instructions on everything from recording a description of a reported issue to documenting and communicating its remediation.

This guide describes how to determine if a malware suspicion is correct or false and how to handle both scenarios. It also includes information about how malware is detected in ABB software.

The process is mainly divided into two parts: continuous maintenance of existing products during the product life cycle, and an eventdriven part handling both customer problems via Support Level 3 and manufacturing problems. The process covers both hardware and software.

This guide explains what a product issue number (PIN) is and how it is used within the PCP organization.

Hardware development has a lot of interactions with internal ABB functions and external suppliers, manufacturers, and customers. This page is intended to give an overview of how maintenance tasks come to the R&D Hardware teams.