Roles: Hardware-Engineer

This guide describes the recommended branching strategy to manage code repositories.

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.

This guide describes the procedure for monitoring, inspection and calibration of used test and measurement equipment. It is valid for the PAPCP REH instruments.

User documentation should provide the necessary information to help the customer ensure that the site is as secure as possible.

The Development Team process manages the planning, prioritization, and visualization of all activities related to the development of software and hardware components. There are multiple development teams in each development stream.

This guide defines requirements and methodologies for VHDL designs and test benches. It helps PA develop FPGAs using VHDL.

Hardware development involves the design and manufacture of electromechanical devices. It includes CAD models, prototypes, manufacturing documentation, and certifications.

The hardware engineer (electrical/mechanical/logical) develops hardware solutions by ​analyzing requirements, designing, implementing, integrating, and testing hardware for products or systems.​

A product issue is a uniquely identified problem impacting a product, requiring clear communication with various stakeholders. It must be documented with accurate information and version details and managed in parallel with bug management and product releases.

Mechanics includes all parts that are not electrical, such as housings, baseplates, and labels. All mechanics are created in a CAD tool.

The purpose of this guide is to provide handson support to the roles involved in setting up a test plan and test suites in Azure DevOps (ADO), demonstrating the product's test coverage.

This guide provides handson support for the roles involved in executing test cases and reviewing test results.

A work item of type "Bug" can be used to suggest an enhancement, something that is not a real defect, but an idea for improvement. This guide describes how to handle enhancements as bugs.

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.

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

Various certifications are applied for in the development of products. This guide covers the ten activities of the general certification flow, and includes specific information regarding marine certifications, certifications for hazardous areas, certification affecting manufacturers, and the order of certification applications.

For a new epic, feature, or user story, there may be a need to write new test cases or modify existing test cases. The purpose of this guide is to provide handson support to the roles involved in writing, updating, or reviewing test cases of a product.

This guide provides an overview of Kanban and its application to software development teams.

Hardware products are manufactured by Electronic Manufacturing Services (EMS). The EMS is responsible for assembling the product according to ABB design. This page describes key items in the New Product Introduction (NPI).

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

A Product lifecycle management (PLM) system enables collaboration between different functions by gathering all productrelevant data in one place. For hardware development, the choice is in Windchill. This page intends to be a goto page for how to find information regarding Windchill.

The product test verifies that the product to be released has acceptable quality. It applies to new products and maintenance/updates of existing products.

This page is intended to be a base for the creation of a new PCB layout. It is meant to be supported together with the PCB layout checklist, which is to be used in the development of the layout.

The engineering service request is the main template to be used during development. The purpose of this site is to reference the two different options when communicating with a Service Provider (for instance layout work, parts list, etc.).

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.

All relevant formulas which are necessary for highspeed design analysis are listed on this page.

This page is intended to give an overview of what kind of documentation is present for the Combitrol & Combimatic documentation.

A production package is created for every product and is the basis for a manufacturer. A production site is commonly called an electronic manufacturing service (EMS). This list is used by the EMS to create the product (box build).

The AML is the Approved manufacturer list. It is a list of electronic components, PCB, mechanical parts and labels, which are all approved by ABB PA PCP.

The developer/author scope definition quick checklist.

This guide describes how Scrum can be used by teams to manage their work. Scrum is a framework that implements the principles of Agile as a concrete set of artifacts, practices, and roles.

Introduction

This guideline describes the custom standard fields used in bug templates. For a more general picture of the standard work item template change process in Azure DevOps, see ADO standard work item template change management process.

This guideline describes the Document Update work item type and the custom standard fields used in its template. For a more general picture of the standard work item template change process in Azure DevOps, see ADO standard work item template change management process.

This guideline describes the custom standard fields used in the Epic template. For a more general picture of the standard work item template change process in Azure DevOps, see the ADO standard work item template change management process.

This guideline describes the custom standard fields used in the Feature template. For a more general picture of the standard work item template change process in Azure DevOps, see the ADO standard work item template change management process.

This guideline describes the fields used in the system epic template.

This guideline describes the custom standard fields used in the User Story template. For a more general picture of the standard work item template change process in Azure DevOps, see ADO standard work item template change management process.

This guide describes what system interfaces are, how they are documented, and how they are managed.

This guide gives an overall view of the test performed before a component, container, product, or system is released.

The test phase checklist is a general guide for users to gauge the quality of product build delivery before starting tests in system test (ST) or RAT. Further, tailoring can be done to align the checklist with any specific product.

This page is intended to be a base for the creation of new schematics or circuit diagrams. It is meant to be support together with a checklist (7PAA010429 CDSchematics Design Checklist) that is to be used in the development of schematics. The tool that is used for this is called Xpedition designer (Mentor graphis).

This tutorial gives an overview of how to work with Markdown. It describes how to change content on the "PCP R&D Processes" website, and can also be valuable for anyone using Markdown in Azure DevOps (ADO).