Standards body
The standards world is a layered ecosystem. At the top, the international bodies — ISO and IEC dividing the technical world between them. Below, regional organisations: the European standardisation bodies producing EN standards, the CIS interstate council maintaining the shared GOST corpus. Then national bodies — one per country, holding the national catalogue and the seat in the international ones — and, orthogonal to geography, the industry societies whose names populate every specification: ASME, ASTM, API, NFPA, IEEE and their peers, writing the deep technical documents for their domains. Some bodies write standards; some, like the US national body, chiefly accredit the processes of others — a distinction that surprises people.
What the layers share is process: committees, balloting, consensus, publication, revision cycles. What they do not share is authority — a body's standards bind only through the adoption mechanisms this cluster keeps returning to, and overlapping scopes between bodies are common, with the same subject standardised differently in two catalogues.
For a project the ecosystem is background until it isn't: knowing which body's document governs, which adoption gives it force, and which body's revision cycle will move it mid-project is part of managing the normative base rather than being managed by it.
See this workflow in practice.
Book a demo to see how Armeta applies this concept across the drawings, standards, specifications, and project data that define the work.