Configuring Compliant Hardware Systems
Given a customer requirement, produce: (1) a component list, (2) a compatibility/best-practices check, (3) a documentation file structure.
Customer requirement: "Workstation for CAD design, budget $2500, needs to run 3 monitors"
1. Draft BOM (Bill of Materials): CPU, motherboard, RAM, GPU, storage, PSU, case, cooling
2. Compatibility check: socket match, RAM type/speed support, PSU wattage vs. TDP sum,
GPU output count vs. monitor requirement, physical clearance (GPU length, cooler height, case)
3. Compliance check: confirm REACH/RoHS declarations available for every component
4. File: /Customer_Name/Quote_v1/{BOM.xlsx, Compatibility_Notes.md, Compliance/}
Progress:
- [ ] Step 1: Capture and clarify customer requirements
- [ ] Step 2: Translate requirements into technical specs
- [ ] Step 3: Select candidate components
- [ ] Step 4: Run compatibility checks
- [ ] Step 5: Run best-practices checks
- [ ] Step 6: Verify compliance documentation availability
- [ ] Step 7: File documentation
- [ ] Step 8: Present configuration + sign-off
Step 1 — Capture requirements Extract: use case (CAD, gaming, server, office), budget, performance targets, peripherals/ports needed, physical constraints (space, noise, power availability), growth/upgrade expectations, deadline.
Step 2 — Translate to specs Map use case to minimum specs: CPU core count/clock, GPU VRAM/class, RAM capacity/speed, storage type (NVMe vs SATA) and capacity, required ports (Thunderbolt, DisplayPort count), form factor.
Step 3 — Select components Choose from approved/preferred vendor list first. Pull current manufacturer datasheets — never rely on memory or old specs, as SKUs and revisions change.
Step 4 — Compatibility checks
- CPU socket ↔ motherboard socket, chipset supports CPU generation
- RAM type (DDR4/DDR5), max supported speed, max capacity per motherboard
- PSU wattage ≥ sum of component TDPs + 20-30% headroom; connector types (EPS12V, PCIe 8-pin count)
- GPU length/height vs. case clearance; cooler height vs. case clearance
- Storage interface (NVMe slot count/generation, SATA port count)
- Peripheral/port count vs. customer's monitor/device count
Step 5 — Best practices
- Airflow: intake/exhaust fan balance, cable routing
- Redundancy where required (RAID, dual PSU) for business-critical use
- Firmware/BIOS version compatible with chosen CPU (check for required BIOS update on new CPU releases)
- Avoid single points of failure for mission-critical builds
- Leave one free expansion slot/bay for future upgrades when budget allows
Step 6 — Compliance verification For every component, confirm the manufacturer publishes current REACH SVHC and RoHS declarations. Flag and substitute any component lacking valid documentation.
Step 7 — Filing structure
/Customers/{CustomerName}/{Date}_{ProjectName}/
01_Requirements.md
02_BOM.xlsx
03_Compatibility_Check.md
04_Datasheets/
05_Compliance/
REACH/
RoHS/
06_Quote.pdf
07_Signoff.pdf
Name compliance files consistently: {Manufacturer}_{PartNumber}_REACH_{Date}.pdf
Step 8 — Present and sign off Summarize configuration, call out any compatibility risks or compromises made against the original requirement, get customer sign-off before ordering.
Example 1: Input: "Office PC, needs dual monitor support, quiet operation, $700 budget." Output:
- BOM: entry CPU with integrated graphics (2x DisplayPort/HDMI out), 16GB DDR4, 512GB NVMe SSD, compact case with low-RPM fans, 80+ Bronze PSU
- Compatibility: confirmed integrated GPU supports 2 simultaneous displays at target resolution; motherboard has 2 video outputs matching monitor cable types
- Best practice note: integrated graphics avoids added noise/cost of discrete GPU, satisfying "quiet" + budget constraint
- Compliance: RoHS/REACH declarations downloaded for CPU, motherboard, SSD, PSU, case; filed under customer folder
Example 2: Input: "Render farm node, needs max GPU compute, 24/7 operation." Output:
- BOM: workstation CPU, high-wattage redundant PSU, server-grade motherboard, ECC RAM, high-VRAM GPU(s)
- Compatibility flag: chosen GPU exceeds case clearance by 10mm — substitute shorter model or larger case
- Best practice: redundant PSU required for 24/7 uptime; added dust filters and higher static-pressure fans for continuous operation
- Compliance: verified GPU manufacturer's RoHS declaration is current revision (prior revision was outdated); re-downloaded
- Always pull specs from the current manufacturer datasheet/PDF, not memory — revisions change silently
- Build in power and thermal headroom (20-30%), not just bare minimum
- Document why a component was chosen when it deviates from cheapest/fastest option, for future reference and customer trust
- Keep one canonical compliance folder per customer order; never embed compliance docs only in email threads
- Re-verify compatibility when substituting any single component — a single swap can break multiple constraints (power, physical fit, port count)
- Don't assume RAM/CPU compatibility by generation name alone — check motherboard's QVL (Qualified Vendor List)
- Don't skip PSU headroom calculation — transient GPU spikes can exceed rated TDP
- Don't file compliance docs only when asked; collect them at selection time, since manufacturers may update or remove declarations later
- Don't reuse an old compatibility check for a "similar" build — small revisions (BIOS, PCB version) can invalidate prior compatibility
- Don't treat RoHS and REACH as interchangeable — they are separate regulations requiring separate declarations