computer hardware
Let an agent handle computer hardware by component, specification, compatibility, safety and end-of-life.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify
Researched by: Claude
Purpose and description
Let an agent handle computer hardware by component, specification, compatibility, safety and end-of-life.
The physical components of a computer system, such as processors, memory, storage, motherboards, power supplies, cooling fans, integrated circuits and complete single-board computers.
What it is for: Running software and processing, storing and communicating data.
It can be check specifications and compatibility; upgrade or repair components; handle hardware safely; recycle and wipe data.
Distinguishing features
Physical parts of computers
Specified by performance and interfaces
Compatibility matters
Contains hazardous and valuable materials
What it looks like
Circuit boards, chips, drives, cases, fans and cables.
How it is recognised
Component types and part numbers
Specifications such as clock speed or capacity
Historical systems such as VAX
Related models
is a kind of - category
runs - counterpart
is disposed of as - end of life
is identified by - identifier
In practice
Families and kinds
processors and integrated circuits
memory and storage
motherboards and buses
power and cooling
peripherals and single-board computers
Identifiers
manufacturer part number MPN components
Standards and regulation
EU RoHS Directive
WEEE Directive
Ecodesign rules for servers and computers
Failure modes and hazards
Electrostatic discharge damage
Overheating and fires in batteries
Data left on disposed drives
Also called
+737
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 4 bundles · 8 layers · 8 findings · 16 questions.
Component Which hardware.
Specification decides fit.
Type
CPU, memory, storage.
Type
Component type.
- Which component is it? definition
- What is its part number? provenance
Specifications
Performance.
Specifications
Specifications.
- What are its key specifications? measurement
- From the manufacturer datasheet? provenance
Compatibility Fit.
Parts must work together.
Interfaces
Sockets and buses.
Interfaces
Interfaces.
- Is it compatible with the system interfaces? boundary
- Is a firmware update needed? boundary
Power
Supply and cooling.
Power
Power and cooling.
- Is the power supply and cooling sufficient? boundary
- What is the power draw? measurement
Safety Handling.
Hardware can be damaged or dangerous.
ESD
Static.
ESD
Static protection.
- Are anti-static precautions taken? action
- Is the device unplugged? boundary
Batteries
Fire risk.
Batteries
Battery safety.
- Is a swollen or damaged battery present? boundary
- How should it be handled? action
End of life Disposal.
Disposal must be responsible.
Data
Wiping.
Data
Data wiping.
- Has storage been securely wiped or destroyed? boundary
- Which method? definition
Recycling
WEEE.
Recycling
Recycling.
- Where can the hardware be recycled or refurbished? action
- Is take-back available? action
What the second pass must settle
- Should component types be separate entries?
- How should part numbers be linked?
- How should historical systems be linked?