Hardware
development
Hardware forms the foundation of every embedded system. From the initial idea to the finished circuit board, we develop custom electronics for control units, sensors, board computers, and edge systems – structured, traceable, and application-oriented.
Hardware Development with a Customer Focus
Professional Hardware Development for Embedded Systems
Leave nothing to chance and develop embedded hardware with structure and an overview.
Customer-centric PCB hardware design goes through 2 to 4 iteration cycles, depending on the specific requirements and complexity of the project.
From initial concept to pre-series production, we ensure every development meets our customers' requirements. We achieve this through structured requirements management.
Hardware Tech Stack
In hardware development, we rely on a tech stack as the technical foundation for our projects. It forms the basis for requirements regarding reliability, electromagnetic compatibility, and component availability.
At the heart of our work is Altium Designer for PCB development. Additionally, we use professional measurement and validation technology, including oscilloscopes, power supplies, spectrum analyzers, and logic analyzers from manufacturers such as Rigol and Digilent.
OUR ELECTRONICS DEVELOPMENT PROCESS
Standardized Processes in PCB Design
Hardware development must follow a clearly structured process that reduces error costs from the outset. The process must allow for iterations for systematic error elimination and require function-oriented testing so that solutions are robust.
Through targeted adjustments and optimizations in each project phase, we ensure that our products are technically mature and prepared for series production.
Definition of system structure and interfaces, selection of suitable controllers and peripherals. Creation of the Bill of Materials (BoM) based on function, price, and availability
Implementation of system architecture in circuit diagrams, ensuring component integration
PCB layout creation considering EMC and signal integrity guidelines
Internal and external review of the schematic and layouts, identification and correction of potential error sources.
Production of initial samples (prototypes), checking for function and quality
Setup of test scenarios for hardware commissioning, validation of basic hardware functionality
Our Quality Promise
PICKPLACE Hardware Development
Our hardware development is based on recognized industry-specific norms and standards. Depending on the industry and project requirements, we work with, among others:
EN 50155
IPC-2221
MIL-STD-461
IPC-A-610
EN 50129
DIN EN 61000
How we structurally implement customer ideas in electronics
Hardware Development Frequently Asked Questions (FAQ)
Hardware development is the development of the electronic assembly of a product. This includes component selection, circuit development, PCB layout, power supply, interfaces, protection circuits, sensors, actuators, commissioning, testing, and documentation. In contrast to pure software development, a physical product is created here. The developed electronics must be manufactured, assembled, measured, and tested under real conditions. Therefore, hardware development does not end with the schematic, but only when the assembly functions reliably, can be manufactured, and meets the requirements of the final product.
No. PCB development is an important part of hardware development, but not the whole thing.
Hardware development begins earlier: with requirements, system architecture, component selection, interface concept, power supply, protection concept, and technical constraints. Only after that are the schematic and printed circuit board created. The PCB is therefore the physical realization of the previously developed electronic architecture.
In short: PCB development is part of hardware development. Hardware development additionally includes concept, function, testing, EMC, manufacturability, lifespan, and technical assurance.
Hardware development includes, depending on the product, among other things Microcontroller, Microprocessors, memory, voltage regulators, sensors, actuators, communication interfaces, connectors, protection circuits, debug interfaces, clock sources, reset circuits, and power electronics.
Technical decisions are also part of this: What supply voltages are needed? What interfaces need to be exposed? What components are available long-term? What temperature ranges must be met? What standards, safety, or security requirements apply? How will the assembly be tested and manufactured later?
The circuit diagram describes the electrical function of an assembly. It shows which components are used and how they are electrically connected to each other.
A good schematic isn't just a collection of components. It depicts the technical structure of the system: power supply, microcontroller, memory, interfaces, sensors, protection circuits, debug ports, and test points. It also serves as the basis for review, layout, simulation, commissioning, and troubleshooting.
A hardware developer designs a product's electronic assembly. He determines which components to use, creates the schematic, oversees the PCB layout, and commissions the finished circuit board.
Typical tasks include component selection, circuit development, power supply design, interfaces, protection circuits, schematic reviews, layout coordination, measurements, troubleshooting, and testing.
He works closely with firmware development, mechanics, purchasing, manufacturing, and testing, because hardware doesn't happen in isolation.
Hardware developers ensure that technical requirements are translated into a functional, manufacturable, and testable electronic assembly.
No, at least not in the same sense as agile software development. Hardware development cannot be changed, tested, and rolled out in short sprints at will.
The reason is simple: hardware is physical. Between a change in the schematic and a tested prototype are fixed steps: component selection, schematic change, PCB layout, manufacturing data, PCB fabrication, assembly, commissioning, measurement, and failure analysis. Each iteration costs time, materials, and budget.
With software, an error can often be corrected with a commit, an update, or a rollback. With hardware, it’s different. If a component was selected incorrectly, a pinout doesn’t match, a trace is routed poorly, or the power supply is unstable, the assembly often has to be remanufactured or undergo extensive rework.
Agile methods can still be helpful. They support communication, prioritization, transparency, and risk management. However, the actual hardware development remains phase-based because physical prototypes must be built, measured, and evaluated.
In short: Agile elements, yes. Fully agile hardware development, no.
Reviews help identify errors before they become costly. An error in the schematic or layout is much easier to correct before manufacturing than after assembly.
Typical reviews check pin assignment, power supply concept, component dimensioning, interfaces, protection circuits, EMC measures, test points, manufacturability, standard requirements, and documentation.
Good reviews don't replace tests, but they reduce the risk of unnecessary hardware revisions.
Electronic components are not available indefinitely. Manufacturers discontinue components, change manufacturing processes, or stop delivering certain variants. This poses a significant risk for products with long lifespans.
Obsolescence Management This means identifying such risks early on and preparing alternatives. These include second sources, suitable component families, documented replacement options, modular architecture, and the ability to port hardware or firmware in a controlled manner.
Without obsolescence management, a single discontinued component can jeopardize an entire product.