Electronics Guide

Articles in This Category

Common Threads Across Regulated Sectors

The sectors differ in vocabulary, but the underlying compliance machinery is remarkably similar. Recognizing the shared pattern helps an engineer moving between industries orient quickly and helps a company reuse process assets rather than rebuild them for every market.

Risk Analysis Drives the Requirements

Regulated sectors do not apply uniform rigor to every function. They first classify hazards, then scale the engineering effort to the classification. Medical device developers perform risk management to ISO 14971. Automotive teams conduct a hazard analysis and risk assessment that assigns each function an Automotive Safety Integrity Level from ASIL A through ASIL D, or QM where no safety requirement applies. Civil aviation derives development assurance levels A through E from a functional hazard assessment, following the guidance in SAE ARP4761 and ARP4754A. Process industries assign Safety Integrity Levels 1 through 4 under IEC 61511, and machinery builders use performance levels a through e under ISO 13849-1 or SILs under IEC 62061.

Many of these frameworks share an ancestor. IEC 61508 is the generic functional safety standard from which ISO 26262 (automotive), IEC 61511 (process industry), IEC 62061 (machinery), and IEC 61513 (nuclear instrumentation and control) are derived. Civil aviation is the notable exception: DO-178C and DO-254 are objective-based documents that predate and stand apart from the IEC 61508 family, and they do not use SIL notation. Engineers who assume the schemes are interchangeable make costly mistakes, because an ASIL D claim is not a SIL 3 claim and neither is a design assurance level A claim.

Development Assurance and Traceability

Every regulated sector demands that requirements, design, implementation, and test evidence be traceable in both directions. The number of objectives to satisfy scales with the assigned criticality. Under DO-178C, software at design assurance level A must demonstrate modified condition/decision coverage of the source code, while level D software carries a far lighter burden and level E software, which cannot affect safety, carries almost none. IEC 62304 divides medical device software into safety classes A, B, and C, with the required documentation growing at each step. Automotive projects layer coding discipline on top, commonly through the MISRA C guidelines.

Development tools attract scrutiny of their own. If a compiler, code generator, or verification tool can introduce an error or mask one, the regulator wants evidence that the tool is trustworthy. DO-330 provides tool qualification guidance for airborne systems, and ISO 26262 assigns tool confidence levels through an analogous analysis. Configuration management, change control, and problem reporting are treated as safety activities rather than administrative overhead.

Qualifying Components for the Environment

General-purpose parts rarely survive regulated environments, and a commercial datasheet is rarely sufficient evidence. The Automotive Electronics Council publishes stress qualification specifications that have become de facto entry requirements for the automotive supply chain: AEC-Q100 for integrated circuits, AEC-Q101 for discrete semiconductors, AEC-Q102 for optoelectronics, and AEC-Q200 for passive components. AEC-Q100 sorts parts into temperature grades, from Grade 0 at −40 to +150 °C down through Grade 1 at −40 to +125 °C, Grade 2 at −40 to +105 °C, Grade 3 at −40 to +85 °C, and Grade 4 at 0 to +70 °C. Production parts then pass through the production part approval process required by IATF 16949.

Aviation applies a different but equally demanding regime. RTCA DO-160, currently at revision G with Change 1 issued in December 2014, defines more than twenty test sections covering temperature and altitude, temperature variation, humidity, vibration, operational shock and crash safety, power input quality, radio-frequency emission and susceptibility, lightning-induced transients, direct lightning effects, icing, and flammability. Defense and space programs add their own layers, including MIL-STD-883 test methods and MIL-PRF-38535 qualified manufacturers lists for microcircuits, and radiation characterization for total ionizing dose and single-event effects. Because these supply chains are long-lived and lucrative, counterfeit avoidance is itself standardized, notably through the SAE AS5553 and AS6081 documents.

Independent Assessment and the Route to Market

Sectors differ sharply in who decides that a product is compliant. Under the EU Medical Device Regulation, only the lowest-risk Class I devices may be self-declared, and even those draw a notified body into the assessment when they are supplied sterile, have a measuring function, or are reusable surgical instruments; every higher class requires notified body involvement. In the United States, most devices reach the market through a 510(k) submission demonstrating substantial equivalence, with De Novo classification and premarket approval covering novel and highest-risk devices.

Automotive illustrates the contrast plainly. Markets that follow the UNECE 1958 Agreement grant type approval before sale, evidenced by an E-mark, whereas the United States relies on manufacturer self-certification to the Federal Motor Vehicle Safety Standards, with enforcement arriving afterward through investigation and recall. Aviation approvals flow through technical standard order authorizations and type or supplemental type certificates, with much of the day-to-day findings work delegated to designated engineering representatives and organizations holding Organization Designation Authorization. Telecommunications adds a commercial layer: the NEBS criteria captured in Telcordia GR-63-CORE and GR-1089-CORE are not law, but network operators treat them as procurement gates, so failing them closes the market just as effectively.

Obligations That Outlive Shipment

In regulated sectors, approval is the beginning of the obligation rather than the end of it. Medical device manufacturers operate post-market surveillance systems, report adverse events, issue field safety corrective actions, and maintain unique device identification records. Automotive suppliers monitor field data through the operation and service phases addressed in ISO 26262, and vehicle manufacturers report defects and conduct recalls under national schemes. Aviation maintains continued airworthiness through service bulletins and airworthiness directives. Process plants prove that safety instrumented functions still work by testing them at the interval assumed in the original SIL verification; skipping the proof test silently invalidates the calculation that justified the design.

Cybersecurity Joins the Safety Case

The most significant recent shift across regulated industries is the treatment of security as a precondition for safety rather than a separate concern. Connected products cannot be shown to be safe if an attacker can change their behavior, so regulators have folded security engineering into approval itself.

In vehicles, UN Regulations No. 155 and No. 156 require a certified cybersecurity management system and a software update management system as conditions of type approval. In the European Union they applied to new vehicle types from July 2022 and to all new vehicles produced from July 2024. ISO/SAE 21434 is the engineering standard commonly used to generate the evidence those regulations demand.

In medical devices, Section 524B of the Federal Food, Drug, and Cosmetic Act, added by the Consolidated Appropriations Act, 2023, and effective March 29, 2023, requires sponsors of cyber devices to submit a plan for monitoring and addressing vulnerabilities, processes for providing updates and patches, and a software bill of materials covering commercial, open-source, and off-the-shelf components. The FDA may refuse to accept a submission that omits this material.

Industrial automation follows the IEC 62443 series, which defines security levels 1 through 4 and, unusually, divides obligations among asset owners, system integrators, and product suppliers rather than placing them all on the manufacturer. Aviation addresses the same problem through the airworthiness security process of DO-326A and ED-202A, with methods in DO-356A and ED-203A and continued airworthiness security in DO-355 and ED-204.

What Regulation Costs the Design

Sector requirements are not a wrapper applied to a finished product. They shape architecture, bill of materials, schedule, and budget from the first design review, and treating them as a late-stage formality is the most common and most expensive mistake in regulated development.

Architecture responds directly to the assurance target. A high-ASIL automotive function often justifies a dual-core lockstep microcontroller, error-correcting memory, and independent watchdog supervision. A high design assurance level avionics function requires structural coverage evidence that constrains coding style and demands that dead code be eliminated rather than explained. A safety instrumented function at a given SIL implies a specific architecture, diagnostic coverage, and proof-test interval, all of which must be documented before the plant is commissioned.

Component selection tightens as well. Qualified parts are more expensive, arrive with longer lead times, and come from a narrower supplier base, yet substituting an unqualified equivalent can invalidate the approval. Long product lifetimes make obsolescence a permanent program risk, since a part that goes end-of-life in an automotive or avionics platform may force requalification years after launch. Even a silicon errata sheet update can trigger impact analysis and regression testing.

Documentation is a deliverable in its own right. Design history files, safety cases, hazard analyses, traceability matrices, verification reports, and configuration records must be produced as the work happens, because reconstructing them afterward is both costly and, in an audit, unconvincing. Organizations that build compliance into their normal engineering process rather than bolting it on at the end consistently reach approval faster and with fewer findings.

About This Category

Industry-specific regulations address the specialized compliance requirements that govern electronic systems in regulated sectors. These regulations exist because the consequences of failure in certain applications extend far beyond typical product-liability concerns: a malfunctioning medical device can harm a patient, a failing automotive system can cause a collision, and compromised defense electronics can threaten national security. The articles in this category provide guidance on navigating the regulatory landscape of these critical industries, helping engineers and organizations develop compliant products that meet demanding standards of safety, reliability, and performance. Just as importantly, they explain the engineering reasoning behind the requirements, so that compliance becomes a means of building genuinely dependable systems rather than an exercise in paperwork. See also the companion category, Regional Regulatory Bodies and Compliance, which organizes requirements by geographic market, such as North America, the European Union, and Asia-Pacific, rather than by industry sector.

Several neighboring categories extend this material. Specialized Industry Standards covers sectors treated separately here, including nuclear, maritime, photovoltaic, and uncrewed aircraft applications, and Advanced Technology Compliance addresses newer regulated domains such as commercial space electronics and collaborative robotics. Risk Management examines the hazard analysis methods that underpin every sector framework, Software and Firmware Safety develops the software assurance practices summarized above, and Testing and Certification describes how the supporting evidence is generated and assessed.