Nexus StandardsIndustry, Trade and Supply ChainsSectors and industries
Area · registry row planned

Transport, logistics and supply chains

The transport, logistics and supply chains section of the Industry, Trade and Supply Chains subsite covers corridors, ports, airports, rail, fleets and supply-chain intelligence: how disruption, asset and movement records are identified and verified, and how they crosswalk to IMO, ICAO and transit data instruments and to supply-chain security guidance. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.

Area recordIndustry, Trade and Supply Chains
  1. TierSectors and industries
  2. Registryregistry row · planned
  3. Nexus StandardsNS-0, NS-3, NS-9, NS-11
  4. Open standards4
  5. Feeds4 · 0 admitted
  6. Couplings4
  7. Last reviewed2026-10-17

Context entry PROPOSED for the Nexus Standards registry.

UNI
NXS-STD-DC-000003
Status
PROPOSEDregistry row · planned · scope NET
Last reviewed
area context bank
Cite this page

Nexus Standards (2026). Transport, logistics and supply chains: area brief, Industry, Trade and Supply Chains (PROPOSED). https://nexustandards.com/industry-trade/transport-and-logistics-sector-standards/ · UNI NXS-STD-DC-000003. Last reviewed 2026-10-17.

Download the profile

Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.

01Scope

Transport, logistics and supply chains: what the area covers, and what it leaves to others.

The sectors and industries section of Industry, Trade and Supply Chains. Scope as the area context entry states it (PROPOSED).

In scope 5

  • Corridor, port and chokepoint disruption records
  • Asset exposure and continuity records for ports, airports, rail and roads
  • Movement data profiles (GTFS, AIS) and their licences
  • Maritime and aviation safety and cyber obligations as clauses citing IMO and ICAO instruments
  • Supplier-network dependency records

Out of scope 3

  • Traffic management or routing of vessels and aircraft
  • Customs or border control decisions
  • Commercial freight rates

Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.

02Nexus Standards that apply

4 Nexus Standards for this area.

The Nexus Standards the area context entry lists; the registry row lists NS-0, NS-3, NS-9, NS-11. Every one is proposed or specified; none is adopted by an authority.

  1. 01

    NS-0 · Constitution and principles

    Status proposed · 12 rules stated. Read NS-0 · The rules for this area

  2. 02

    NS-3 · GRIx record UNIs (grammar, legacy crosswalk, allocation authority)

    Status proposed · 0 rules stated. Read NS-3 · The rules for this area

  3. 03

    NS-9 · Contextual UNIs (deployments, instances, programme instances)

    Status proposed · 5 rules stated. Read NS-9 · The rules for this area

  4. 04

    NS-11 · Verification and monitoring (evidence, attestations, zero-trust conformance observation)

    Status proposed · 6 rules stated. Read NS-11 · The rules for this area

03Open standards

4 open standards, each with its relation.

Relations are register entries (NS-14), never conformance or equivalence statements; hover or focus a relation for its meaning. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here.

04Restricted compatibility profiles

2 closed standards, named only.

Closed or paywalled standards appear by name and link only; any compatibility profile of one is built on simulated data and kept on protected pages until an institutional arrangement with the issuing body is recorded. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.

05Hazards and sectors

What acts on this area, and who carries it.

Hazards and threats 5

Chokepoint closuresStorms and floods at portsCyber attacks on logistics systemsPandemic disruptionConflict

Sectors 1

transport-logistics
06Systemic couplings

4 couplings to other areas and subsites.

Each coupling names the mechanism that links this area to another; select a card on the canvas to trace it. Mechanisms are stated in the context bank (PROPOSED).

Canvas · the area and its couplingsDesign, not a record
Transport, logistics and supply chains: systemic couplingsThe couplings the area context bank records for Transport, logistics and supply chains: 1 area in Industry, Trade and Supply Chains, 3 areas in other subsites and 3 subsites reached. Each coupling carries a mechanism stated in the context bank (PROPOSED); a reading aid, not a dependency proof.

Fig.RUNNING marks the area you are reading; DONE an area in the same subsite, QUEUED an area elsewhere and GATE a subsite reached. Tags give reading order only, never a status. Design, not a record.

  1. Energy utilities and gridsEnergy and Critical InfrastructureFuel supply and electrified rail and ports depend on the grid; energy disruption stops freight and passenger movement.
  2. Industry and manufacturingIndustry, Trade and Supply ChainsJust-in-time production propagates port and corridor disruptions through supplier networks.
  3. Agriculture and land useWater and Food SystemsFood exports and fertiliser imports depend on corridors and chokepoints; closures transmit into food prices.
  4. Digital, telecom and platformsDigital, Cyber and AINavigation, port community systems and fleet telematics depend on telecom and timing services.
07Data and feeds

4 sources, with provider, licence and delivery path.

Sources the area reads or proposes. Delivery follows GRIx first; a source is shown live only after an owner decision admits it for public pages.

Every feed · pending admission

No legal register row admits any of these sources for live display on public pages yet, so nothing is read from them here. A register row that exists records the source for the governed GRIx path; admission for public pages is a separate owner decision.

Admitted
0
none yet
Register row exists
3
recorded for the GRIx path
Proposed row
1
terms to be recorded
Delivery
3 GRIx · 0 plugin · 0 browser · 1 snapshot
GRIx first, then plugin, browser-direct, snapshot
  • Digitraffic marine AIS positionspending admission

    Fintraffic · real time

    CC BY 4.0

    GRIx governed readregister row exists

  • OpenStreetMappending admission

    OpenStreetMap Foundation and contributors · continuous

    ODbL 1.0

    GRIx governed readregister row exists

  • World Development Indicatorspending admission

    World Bank · annual with quarterly updates

    CC BY 4.0

    GRIx governed readregister row exists

  • PortWatch port and chokepoint activitypending admission

    International Monetary Fund with the University of Oxford · weekly

    IMF PortWatch terms (reuse with attribution; terms to be recorded)

    build-time snapshotproposed register row

09Readiness

What each pathway can read from this area.

GCRI Canada evidence pathway

GCRI Canada

Disruption and movement records with source releases and licences become readable as evidence for GCRI Canada supply-chain cascade research under its own rules.

Open the GCRI Canada evidence pathway

Recognition pathway

The Global Risks Forum (GRF)

A port or corridor authority that publishes continuity clauses and attestations gives GRF a record trail to consider; recognition is GRF's decision.

Open the Recognition pathway

Capital pathway

The Global Risks Alliance (GRA)

Corridor-resilience investments can present verified disruption baselines to GRA, which assesses capital readiness under its own rules.

Open the Capital pathway

Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.

11Audiences

Who works with this area: 4 audiences.

  1. Port, airport and corridor authorities
  2. Logistics operators
  3. Trade and transport ministries
  4. Supply-chain risk analysts
12Working group

The working-group charter, proposed.

Scope

Profile disruption, asset and movement records for transport and logistics and crosswalk them to IMO, ICAO and transit data instruments.

No working group is chartered yet; a community may charter this one under NS-13 through a docket.

Deliverables · 3
  1. Chokepoint and corridor disruption record profile
  2. Crosswalk from NS-10 clauses to IMO cyber guidelines and ICAO Annex 19 (by section and URL)
  3. Licence matrix for AIS, GTFS and port activity data
Liaison targets · 4
  • International Maritime Organization liaison sought
  • International Civil Aviation Organization liaison sought
  • UNCTAD liaison sought
  • MobilityData liaison sought
13Open problems

3 open problems an expert would start with.

  1. AIS and port activity data are fragmented and often licence-restricted, which limits open disruption monitoring.
  2. Firm-level supplier networks are confidential, so propagation models rely on sector input-output tables that hide concentration.
  3. ICAO and IMO instruments are not openly licensed, so clause crosswalks must cite by number without text.
14Registry depth

The registry row: scope NET, 2 crosswalk domains.

This area has a row in registry/subsites.yaml (status planned), so it carries five depth pages and the register crosswalk of its domains.

Crosswalk graph · transport, logistics and supply chainsFrom the registry
Transport, logistics and supply chains: the register crosswalk48 nodes on four orbits (Nexus Standards and consumers inside, then domains, external standards and issuing bodies) joined by 55 register links.
Nexus StandardsDomainsExternal standardsIssuing bodiesConsumers

4 Nexus Standards · 2 domains · 22 external standards · 19 issuing bodies · 1 consumers. Relations are register entries (adopt, profile, crosswalk, cite), never compliance claims; names belong to their stewards.

Crosswalk graph48 nodes and 55 links from registry/external-standards.yaml, registry/subsites.yaml and registry/consumers.yaml. Relations (adopt, profile, crosswalk, cite) are register entries, never compliance claims.

The registry holds no geography for the area itself: areas are not places. The one geography it implies is where the bodies that issue the area's external standards sit.

Standards globe · Transport, logistics and supply chains: issuing bodiesFrom the registry
Where the issuing bodies of the external standards register sitA plate carrée world map with Natural Earth coastlines, H3 resolution 2 hexagons at the public seats of 16 issuing bodies and one dot per seat. 22 register entries.
Issuing bodies' seats (16)H3 cells, resolution 2 (6); darker, more register entriesSubsites, consumers, standards: no geography in the registry
Issuing bodies and their seats (16)
BodySeatRegister entries
IEC TC 65Geneva, Switzerland2
ISO/TC 268Geneva, Switzerland2
ISO/TC 299Geneva, Switzerland2
European Parliament and CouncilBrussels, Belgium1
IEC TC 65 with ISA (ISA/IEC 62443)Geneva, Switzerland1
IEEEPiscataway, New Jersey, United States1
ISO/IEC JTC 1/SC 27Geneva, Switzerland1
ISO/TC 251Geneva, Switzerland1
ISO/TC 292Geneva, Switzerland1
ISO/TC 59/SC 13Geneva, Switzerland1
ITU-RGeneva, Switzerland1
ITU-T SG15Geneva, Switzerland1
NISTGaithersburg, Maryland, United States1
OASIS CSAF TCWoburn, Massachusetts, United States1
OpenSSF (Linux Foundation)San Francisco, California, United States1
OpenVEX community (OpenSSF project)San Francisco, California, United States1

1 subsites: no geography in the registry (areas, not places) · 2 consumers: repositories, no geography · 19 Nexus Standards: documents, no geography · 3 issuing bodies without a fixed public seat, listed not drawn: World Customs Organization; International Civil Aviation Organization; International Maritime Organization · Programme regions of the ecosystem coverage register: named, not drawn (no coordinates in the registry)

Standards globe16 issuing bodies with a public seat, 22 register entries, H3 cells at resolutions 1 to 4. Seats are city coordinates, not registry fields; subsites, consumers and standards have no geography, so none is drawn. Plate carrée still map; globe with script.

Area on the sitesArtifact kindsGoverning standardsPages
Trade, resources and supply chains (GCRI Canada field gateway; GRF and GRA counterparts)data, dataset, report, map, documentationNS-1, NS-3, NS-3b, NS-4, NS-5therisk.global/fields/trade/
Supply chain chokepoints, port disruptions, corridor risks, critical mineralsdata, dataset, model, map, reportNS-1, NS-3, NS-3b, NS-5therisk.global/challenges/

From the ecosystem coverage register: what the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) sites publish on this area, as claimed there and not evaluated here.

15References

4 sourced references.

Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them.

  1. peer-reviewedSupply chain disruptions: evidence from the Great East Japan EarthquakeThe Quarterly Journal of Economics · 2021
  2. peer-reviewedFirm-level propagation of disaster damages within supply chain networksNature Sustainability · 2019
  3. published statisticsGuidelines on maritime cyber risk management (MSC-FAL.1/Circ.3)International Maritime Organization · 2022
  4. published statisticsLifelines: The Resilient Infrastructure OpportunityWorld Bank · 2019
16Learning

Risk Academy faculties for this area.

Plain links to the faculty pages of Risk Academy; no course, credential, recognition or endorsement is implied.

17Key terms

Terms used on this page.

UNI
Unique Nexus Identifier: identifies and resolves an artifact and its record; it never certifies truth, readiness or approval.
PROPOSED
Drafted content that no authority has adopted. Every area entry here is a proposal to the Nexus Standards registry.
crosswalk
Relation: Nexus clauses are mapped to parts of the external standard by number, never by text.
cite
Relation: the external standard is cited by identifier and URL as a reference.
adopt
Relation: the external standard is used as published, values validated against it.
compatibility profile (restricted)
Relation to a closed or paywalled standard: named and linked only; any profile is simulated and kept on protected pages.
pending admission
No legal register row admits this source for display on public pages yet, so nothing is read from it.
GRIx
The governed data layer of Nexus Foundry: external data is read through it with its licence and source release.
docket
A public change record under NS-13, decided by editors with written reasons.
attestation
An evaluator's recorded result for one clause and one subject under NS-11; never a certification.
liaison sought
A liaison the working group would ask the body for; none is held unless the body confirms it in writing.
19Learn and apply

Where Transport, logistics and supply chains is taught, worked on and run.

Risk Academy disciplines that teach Transport, logistics and supply chains, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.

Risk Academy

Disciplines and courses

20Questions

Questions and answers.

Is the Transport, logistics and supply chains area adopted?
No. The area entry is PROPOSED content for the Nexus Standards registry beside its registry row. Adoption of any standard is a recorded authority decision and none is recorded today.
Are the feeds on this page live?
No. Every feed is pending admission: no legal register row admits it for public pages yet, so nothing is read from it here.
How do I change this brief?
Through a docket under NS-13: a pull request against the area context bank or the registry, decided by editors with written reasons.
Nexus Standards

Shape this brief: Transport, logistics and supply chains.

Propose a change, join the working group or name a source. Area entries are PROPOSED content for the Nexus Standards registry; a UNI identifies and never certifies, and nothing on this site is a certification, an approval or a readiness statement.

Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.

Skip to toolbar