Measuring Units

§1A measurement is a number and a unit

“5” is not a length; “5 mm” is. The number counts and the unit carries the physics — drop the unit and the physics goes with it.

This is why unit errors are among the most expensive mistakes in engineering: a quantity handled without its unit can silently change meaning by a factor of a thousand or a million. The discipline of this page — track units through every calculation, and check they balance — is the cheapest error-detection available, and §6 turns it into a formal test.

Contents

§2The seven base units

Since 2019 all seven are fixed to constants of nature rather than physical artefacts — the units no longer depend on a lump of metal in a vault.

The base units and what now defines them
Quantity	Unit (symbol)	Fixed by
Length	metre (m)	the speed of light, c
Mass	kilogram (kg)	the Planck constant, h
Time	second (s)	the caesium hyperfine frequency
Electric current	ampere (A)	the elementary charge, e
Temperature	kelvin (K)	the Boltzmann constant, k
Amount of substance	mole (mol)	the Avogadro constant, N_A
Luminous intensity	candela (cd)	a fixed luminous efficacy
For mechanical engineering the working three are the metre, kilogram and second — length, mass and time — from which force, pressure, energy and power all follow. The kelvin shares its size with the degree Celsius, offset by the freezing point of water: K = °C + 273.15.

Contents

§3Derived units

Multiply and divide base units and you get every other unit. Many combinations earn a name — but each is only shorthand for a product of base units.

Named derived units, resolved to base units
Quantity	Unit	In base units
Frequency	hertz (Hz)	s⁻¹
Force	newton (N)	kg·m·s⁻²
Pressure, stress	pascal (Pa)	kg·m⁻¹·s⁻² (= N/m²)
Energy, work	joule (J)	kg·m²·s⁻² (= N·m)
Power	watt (W)	kg·m²·s⁻³ (= J/s)
Electric charge	coulomb (C)	A·s
Voltage	volt (V)	kg·m²·s⁻³·A⁻¹ (= W/A)
Resistance	ohm (Ω)	kg·m²·s⁻³·A⁻² (= V/A)
Read the chain on the hero drawing: mass × acceleration builds the newton; the newton over an area is the pascal; the newton through a distance is the joule; the joule per second is the watt. Four of the most-used units in this Library, all one family.

Contents

§4Coherence

The SI is a coherent system: its derived units are pure products of base units with no numerical factors. This is the property that makes consistent-unit equations need no conversion constants.

Example 1 — coherence in action

Put F = ma in base units: a mass of 12 kg accelerating at 3 m/s² gives 12 × 3 = 36 in units of kg·m·s⁻² — which is the newton, no factor required, so the force is 36 N directly. The same calculation in mixed units (pounds, feet, minutes) would need a conversion constant to come out right. Work in coherent SI and the arithmetic is the physics.

The single most useful habit that follows: reduce to base SI units (metres, kilograms, seconds, and the coherent derived units built from them) before computing, and the answer emerges in coherent units with nothing to reconcile. Every worked example across this Library is set up that way.

Contents

§5The prefix ladder

Prefixes rescale a unit by powers of ten; engineering keeps to the powers divisible by three so the digits stay legible.

SI prefixes across the engineering range (each a power of ten)
Prefix	Symbol	Factor	Prefix	Symbol	Factor
tera	T	10¹²	deci	d	10⁻¹
giga	G	10⁹	centi	c	10⁻²
mega	M	10⁶	milli	m	10⁻³
kilo	k	10³	micro	µ	10⁻⁶
hecto	h	10²	nano	n	10⁻⁹
deca	da	10¹	pico	p	10⁻¹²
Beyond this range sit peta/exa/zetta/yotta and the 2022 additions ronna and quetta upward, and femto/atto/zepto/yocto with ronto and quecto downward — completing 10³⁰ down to 10⁻³⁰.

Rules that keep prefixes honest: only one prefix on a unit (nm, never mµm); the prefix binds before any exponent, so 1 mm² = 10⁻⁶ m²; and mass prefixes ride on the gram, not the kilogram (mg, g, Mg). Prefer moving the prefix over writing strings of zeros — 21 µm and 13.8 MPa are legible where their expanded forms are not.

Contents

§6Dimensional analysis

Every physically valid equation is dimensionally homogeneous: both sides carry the same combination of mass, length and time. Checking that is a free, powerful sanity test.

Base dimensions mass [M] length [L] time [T] — force [M L T⁻²], energy [M L² T⁻²], power [M L² T⁻³]

Example 2 — two checks in the dimensions

Kinetic energy ½mv²: [M] × [L T⁻¹]² = [M L² T⁻²] — exactly the dimensions of energy (the joule). Homogeneous ✓.

Pendulum period T = 2π√(L/g): inside the root, [L] ÷ [L T⁻²] = [T²]; its square root is [T], a time — as a period must be. Homogeneous ✓ (and note the dimensionless 2π is invisible to the check, as constants always are).

The test cuts both ways: an equation that fails is certainly wrong, while one that passes is only possibly right — dimensional analysis catches structural errors, not a missing factor of two. It also builds units: force must be [M L T⁻²], so its unit must be kg·m·s⁻², which is why the newton is defined exactly so.

Contents

§7Accepted non-SI units

A handful of non-SI units are sanctioned for use alongside the SI because practice demands them — but they are not coherent, so they must be converted before they enter a calculation.

Non-SI units accepted for use with the SI
Unit	Quantity	In SI
minute, hour, day	time	60 s, 3600 s, 86 400 s
degree (°)	angle	π/180 rad
litre (L)	volume	10⁻³ m³
tonne (t)	mass	10³ kg
bar	pressure	10⁵ Pa
The radian and steradian are dimensionless SI units — an angle is a ratio of two lengths, so it carries no base dimension, which is why the 2π in the pendulum check was invisible to the dimensions.

Contents

§8Quick reference

The working core of the page on one card rack.

Base seven

m · kg · s · A · K · mol · cd

Mechanical family

N = kg·m/s² · Pa = N/m²

J = N·m · W = J/s

Coherence

base-unit inputs → base-unit answer

no conversion constants

Dimensions

both sides must match

fail ⇒ wrong; pass ⇒ maybe

Prefixes

steps of 10³ · one only

mass prefixes on the gram

Contents

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Measuring Units. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to carry the subject from function and assumptions through design evidence, verification and controlled release. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Apply Measuring Units by beginning with the duty, not the component or software command. Convert the key ideas—units, base, seven, derived, coherence—into measurable requirements and interfaces. Record operating and non-operating environments, duty cycle, expected life, loads, energy sources, human interaction and reasonably foreseeable abnormal conditions. When a value is not a project requirement or verified supplier datum, identify it as an assumption or illustrative value.

Create a calculation and evidence trail that another competent person can audit. Every input should carry a source, unit, revision and uncertainty or tolerance where relevant. Every model should state its boundary conditions and limitations. Keep nominal capacity separate from design capacity, and keep verification margin separate from an arbitrary safety factor. If a code or standard governs the work, confirm the applicable edition and contractual status rather than copying a number from a secondary summary.

Design for manufacture, assembly, inspection, operation and maintenance at the same time. A technically valid geometry can still fail because it cannot be fixtured, measured, cleaned, guarded, reached or replaced. Review process capability, datum or reference strategy, tolerance accumulation, access, error-proofing and changeover. Where people interact with plant, apply the hierarchy of controls and consult those who will operate, clean, maintain and recover the equipment.

Plan verification before release. Define the characteristic, method, equipment, sample or test condition, acceptance criterion, record and responsible person. Validation then asks a different question: whether the resulting system is effective and suitable in the intended use context. A passed drawing check or analysis does not by itself validate usability, maintainability or production performance.

Step-by-step operating method

Define the duty. Capture the required function, interfaces, operating environment, life, loads and unacceptable outcomes.
Establish the model. Identify governing principles, units, material or process data, assumptions and uncertainty.
Develop alternatives. Compare feasible concepts against performance, manufacturability, safety, maintainability and cost.
Verify the design. Use analysis, test, inspection or demonstration with acceptance criteria defined before execution.
Release and learn. Baseline the design, control changes, retain evidence and feed operating results into the next revision.

Illustrative design review record

Illustrative values only. Build a one-page record with the required function, input sources, assumptions, governing load or process condition, failure consequences, selected concept, verification method and acceptance criterion. Mark every numerical input as project requirement, verified supplier data, measured value, calculation output or assumption. Review the weakest evidence first. If an assumption can change safety, compliance, interchangeability or capacity, it must be resolved before release rather than buried in a calculation note.

Evidence class	Question	Release expectation
Requirement	What must the design do and under which conditions?	Approved and traceable
Input	Where did the load, property, tolerance or process limit come from?	Source, unit and revision recorded
Analysis	Which model and assumptions connect input to result?	Checkable calculation or simulation
Verification	How will conformity be demonstrated?	Method and acceptance criterion agreed
Validation	Will the solution work for intended users and conditions?	Representative use evidence

Common failure modes and recovery actions

1. Watch for

Starting detailed design before interfaces and operating limits are agreed.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Using catalogue or typical values as though they were certified project inputs.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Checking nominal performance while ignoring tolerances, degradation and foreseeable misuse.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Confusing verification of requirements with validation of user need.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Releasing drawings or procedures without configuration, inspection and change controls.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.