Engineering Question Bank
Direct, public-safe answers to technical questions that buyers, engineers, sourcing teams and reviewers may ask when evaluating semiconductor, defense-electronics and AI-infrastructure assurance.
How do I identify hidden semiconductor supply-chain dependencies?
Build a multi-tier dependency graph that links parts, suppliers, sub-suppliers, fabs, OSATs, materials, logistics nodes, geographies and qualification constraints. Then look for shared nodes and single points of failure that are not visible in a flat approved-vendor list.
How do I know whether supplier diversification is real?
Check whether supposedly independent suppliers converge on the same fab, packaging/test house, substrate, specialty material, firmware dependency, logistics route or qualified process. If they do, diversification may be only superficial.
What evidence belongs in a semiconductor provenance review?
Useful evidence includes manufacturer and distributor pedigree, chain of custody, certificates, trace records, lot/date-code consistency, packaging and marking observations, supplier history, storage/handling information, receiving inspection and relevant technical test results.
Can provenance analytics replace counterfeit testing?
No. Analytics can prioritize, triage and document source-confidence concerns. Qualified inspection or laboratory testing may still be required for a definitive technical determination.
What is a practical counterfeit-risk disposition workflow?
Use evidence to support actions such as accept, accept with conditions, inspect/test, quarantine, escalate or reject, while recording the evidence, uncertainty and approval authority behind the decision.
What engineering methods improve mission-critical electronics reliability?
Common methods include component derating, worst-case electrical and thermal stress analysis, margin review, layout/manufacturability checks, mission-profile analysis, failure-mechanism review and traceable corrective-action closure.
Why is derating important?
Derating creates margin below limiting component stresses and can reduce overstress exposure over mission life. It does not replace component quality, qualification or appropriate system design.
What should a power-electronics supplier capability assessment include?
Evaluate process control, component derating, thermal design discipline, traceability, change control, screening and qualification evidence, failure-analysis capability, corrective-action history and supply continuity.
What does L1-L3 AI-fabric validation cover?
L1 covers physical/optical/electrical health; L2 covers Ethernet link and switching behavior; L3 covers IP routing and path behavior. A complete workflow correlates those layers with congestion telemetry and workload symptoms.
Why can an AI fabric be link-up but still perform poorly?
A fabric can be administratively up while experiencing marginal optics, FEC pressure, lane errors, congestion, queue pressure, path imbalance, ECMP asymmetry, route churn or workload-specific incast.
What should an AI-fabric assurance report contain?
Topology, test conditions, acceptance criteria, per-layer evidence, telemetry anomalies, failure localization, reproducibility notes, remediation status and a traceable pass/fail rationale.
How should engineering risk scores be used?
A score should summarize evidence, not hide it. The decision record should preserve why the score exists, what evidence supports it, what uncertainty remains and what mitigation is recommended.
How do lifecycle and obsolescence affect defense electronics?
Long-lived systems can outlast commercial semiconductor availability. DMSMS, obsolete components, shrinking authorized channels and requalification constraints can become reliability and continuity risks.
What is evidence-to-decision engineering?
It is a structured method that connects technical observations, source records, calculations, assumptions and uncertainty to a documented risk decision, owner, mitigation and closure status.
How does SALAR differ from a parts broker or test laboratory?
SALAR's public role is engineering analysis and decision support across reliability, supply-chain dependencies, provenance, manufacturing stability and AI infrastructure assurance. It does not present itself as a parts broker or counterfeit-testing laboratory.
Go deeper: Technical Topic Hub · Glossary · Engineering Answers