725 abbreviations with 1,246 meanings, from the gate and discipline codes on the lifecycle charts to the standards, bodies and industry terms the Hub uses. Where the same letters mean different things, each meaning is listed with the lifecycles that use it. The list is built from the lifecycle and compliance data, so it stays current. For definitions of terms in general, see the glossary.
The North American automotive body that publishes APQP, PPAP, FMEA, MSA and SPC manuals.
Standards bodies and agencies
Used in: AIAG and VDA FMEA guide
Lead customers have qualified the part in their own products, by their own tests or a production part approval where their market asks for one, and approve it for their production, or have agreed when they will.
Gate codes
The die, package and stack pass their qualification to the published JEDEC methods and the target application, and the result is recorded.
Gate codes
In: Memory lifecycle
A cost or improvement change, such as a die shrink, a new material source or an assembly change, has been qualified and notified to customers, and is ready to implement.
Gate codes
At least one lead customer product built on the technology passes the customer's qualification and system evaluation, and the customer approves it for volume.
Gate codes
Owns the relationship with the customer's quality organisation: captures the voice of the customer and every customer specific requirement, prepares and submits the PPAP, handles customer portals, scorecards, complaints and change notifications.
Discipline codes
The three measures a chip design is usually judged and traded off on.
Design and verification
Sets performance and power targets from the architecture and tracks them through RTL, emulation and physical design to correlation on silicon.
Discipline codes
In: SoC lifecycle
The automotive process in which a supplier shows, with records, that its production process makes parts that meet requirements.
Quality and reliabilityStandards and regulations
Used in: PPAP guide, Traceability overlay, Automotive lifecycle: Automotive quality and PPAP, APQP lifecycle: PPAP Submission & Approval, APQP lifecycle: PPAP submitted gate, APQP lifecycle: PPAP approved gate
Timing, power and physical checks are clean on the final layout, and the layout matches the netlist.
Gate codes
Enough early money, from founders, angels, a grant or an accelerator programme, is committed to pay for the proof of concept, with what it must show agreed in advance.
Gate codes
The fab starts product wafers for customers, with its quality system certified, operations ready and customers qualifying their products.
Gate codes
A recurring review of complaints, vigilance reports, trends, vulnerability findings, field actions and changes confirms the benefit-risk balance still holds, updates the risk management file and decides any corrective action or design change.
Gate codes
The certification plans and the plans and standards under them are complete, consistent with each other, submitted to the certification authority or the integrator, and reviewed at the first stage of involvement.
Gate codes
The production part approval package is complete at the required submission level, every element has been checked against the customer specific requirements, the part submission warrant is signed and the package is submitted.
Gate codes
In: APQP lifecycle
Firmware and the main software run on emulation or FPGA prototypes of the hardware, the main use cases have been exercised, and the hardware and software issues found are tracked to closure.
Gate codes
In: System lifecycle
Owns the product's security: the security plan and secure development lifecycle, the review board, the release decision, residual risk acceptance and the security support plan until the end of support.
Discipline codes
Plans and runs post-market surveillance: complaint handling, trend analysis, vigilance reporting, field safety corrective actions, periodic reports, component obsolescence watch and the records archive at end of support.
Discipline codes
Protects the item in production: the cybersecurity control plan, secure provisioning of keys and certificates, end-of-line configuration and locking, protection of production tools and data, and the release for post-development.
Discipline codes
Leads disciplined problem solving for customer complaints, internal escapes and audit findings: containment, root cause by occurrence and escape, corrective and systemic preventive action, verification and closure, and the warranty and returns analysis that feeds it.
Discipline codes
In: QMS lifecycle
Owns the threat model, the security architecture, secure boot and update, security testing, the software bill of materials and the response to vulnerabilities until the end of support.
Discipline codes
In: System lifecycle
The customer has approved the part for production shipment, either fully or with an interim approval whose conditions and expiry are recorded and tracked.
Gate codes
In: APQP lifecycle
The checks and reviews that show a product or a kit meets its requirements before release.
Quality and reliabilityDiscipline codes
Runs advanced product quality planning under IATF 16949, the design and process FMEAs, the control plan and the production part approval submission, and keeps statistical process control running in production.
Discipline codes
Checks the kit as a whole: a library of QA test cases and QA designs run through every supported tool category, regression on every change, and the checks that the parts of the kit agree.
Discipline codes
In: PDK lifecycle
Assesses how much confidence the tool needs and how its errors would be detected, writes the human review policy, controls the flow documentation, runs incident and corrective action handling and change impact assessment, and records lessons learned.
Discipline codes
Defines the screening flow and lot acceptance tests, plans and runs qualification to the agreed framework, and reports lot acceptance for every flight lot.
Discipline codes
In: Space lifecycle
Gate and discipline codes are plain initials chosen for the Hub's charts, not any company's internal codes. Standard names belong to their publishers; the guides explain them in our own words. Missing an abbreviation? Suggest one.