Roles: L4-Coordinator

This guide describes how bugs – when they are created in Azure DevOps (ADO) – also are classified to ensure that they are handled with regards to their severity and potential impact.

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).

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.

A bug is an unexpected problem in the software or hardware which can be reported for any issue in a product by e.g. product managers, product owners, test engineers, or customers (via L3 or L4 Support).

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.

The L4 coordinator is responsible for monitoring and prioritizing the support case backlog. Securing that the support cases are assigned to L4 engineers and are the single point of contact for escalations within its assigned product area.

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

This guide describes different types of software vulnerabilities and associated threats. It also describes various defense mechanisms that are typically needed to be prepared for software attacks.