ISO/DIS 25500-1:2026(en)

ISO/TC 184/SC 5

Secretariat: ANSI

Date: 2025-11-14

Supply chain interoperability and integration – Part 1: Overview and principles of the industrial internet

© ISO 2026

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester.

ISO copyright office

CP 401 • Ch. de Blandonnet 8

CH-1214 Vernier, Geneva

Phone: +41 22 749 01 11

Email: copyright@iso.org

Website: www.iso.org

Published in Switzerland

Contents

Foreword v

Introduction vi

1 Scope 7

2 Normative references 7

3 Terms and definitions 7

3.1 authoritative legal entity identifier 8

3.2 authoritative identifier 8

3.3 authoritative source 8

3.4 callback security 8

3.5 characteristic data 8

3.6 concept encoding 8

3.7 data 8

3.8 dataset 8

3.9 date of origin 9

3.10 identifier 9

3.11 identifier issuer 9

3.12 industrial internet 9

3.13 information 9

3.14 international business identifier 9

3.15 international business registration number 10

3.16 jurisdiction 10

3.17 legal entity 10

3.18 legal name 10

3.19 onboarding 10

3.20 place of origin 10

3.21 prefix name server 11

3.22 proxy identifier 11

3.23 quality identifier 11

3.24 register 11

3.25 supply chain data formatting contract clause 11

3.26 trading entity 11

4 Principles of supply chain interoperability, integration and the industrial internet 12

4.1 General 12

4.2 Supply chain data formatting contract clause 12

4.3 Supply chain data verification 12

5 The series path to supply chain interoperability and integration 13

6 Structure of the supply chain interoperability and integration series 13

7 Relationship of the supply chain interoperability and integration series to other international standards 14

8 Conformance 15

Annex A (informative) Document identification 16

Annex B (informative) Supply chain data formatting contract clause - elaborated 17

A.1 Date 17

A.2 Trading entity identification 17

A.3 Location identification 17

A.4 Item identification 17

A.5 Item description 18

Bibliography 21

Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.

This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration, Subcommittee SC 5, Interoperability, integration, and architectures for enterprise systems and automation applications.

Any feedback or questions on this document should be directed to the user’s national standards body. A complete listing of these bodies can be found at www.iso.org/members.html.

Introduction

Supply chain data is the data that needs to be shared between potential or existing trading entities to support the acquisition, transfer, storage, maintenance and eventual disposal of goods or services.

Fundamental to this document is the understanding that data is the tangible form of information. For data to reliably transfer information between systems the data must be portable and unambiguous; this is the goal of ISO 8000, the international standard for data quality.

ISO 8000 achieves data portability and unambiguity through including provenance as well as concept encoding, a process where metadata and reference data are represented by a language independent concept identifier from a concept dictionary that contains the terminology (terms, definitions, symbols or images) used to provide the unambiguous meaning of the concept.

Also fundamental is the understanding that no two objects can occupy the same place at the same time and it follows that all objects can be uniquely identified and differentiated from all other objects by their time and place of origin. Finally, identifiers are a critical component of supply chain communication. An identifier is a string of characters created by an organization to reference a dataset, the characteristic data that describes the object identified.

Critical to supply chain interoperability and integration is trust. Trust requires the positive and verifiable identification of the trading entities and an understanding of their authority. Anonymity is not acceptable in supply chain data exchanges. In addition to the identification of the trading entities (who), the identification and description of the products and services subject to contract (what), as well as the locations (where) and the time (when) of associated events are necessary to create the industrial internet, a secure and efficient environment for the verification of supply chain data.

The industrial internet is above all else a trusted business-to-business (B2B) platform for commercial users. It is designed to allow interoperability of supply chain data and integration of supply chain systems between known and trusted parties as legal entities. To do this, the industrial internet needs to overcome both anonymity and impersonation. The industrial internet relies on verifiable legal identity to overcome anonymity and protection from impersonation through callback security.

The industrial internet uses a prefix name server (PNS), which is an ISO 8000-115 compliant register of prefixes with globally unique prefix records that contain the legal owner of any identifier with that prefix and contains an electronic address to resolve the identifier to the dataset it represents as well as any use restrictions. The PNS used in the industrial internet is.an enhanced version of the domain name server (DNS), that supports callback security, one of the earliest forms of secure communication and the backbone of two-factor authentication. For example, if you get a call telling you that your bank account or credit account has been compromised, and the caller asks you to verify your account information, the appropriate response is “thank you” followed by ending the call and promptly calling your financial service provider using a number you know to be correct (not one provided by the caller) – this is callback security. Callback security is simple, low cost and very effective.

This document describes the principles of supply chain interoperability and integration and introduces the fundamental the supply chain data formatting contract clause necessary for the creation and verification of quality portable data that underpins the industrial internet. This document includes an overview of the structure of the series of standards developed within ISO 25500; each standard part defines the data required to perform specific supply chain functions and how this data can be verified.

Supply chain interoperability and integration – 1: Overview and Principles of the Industrial Internet.

This document provides an overview of the standards developed in the ISO 25500 series for supply chain interoperability and integration.

The following are within the scope of this document:

— stating the scope of the ISO 25500 series as a whole;

— establishing the principles of supply chain interoperability and integration;

— describing the path to supply chain interoperability and integration;

— describing the structure of the supply chain interoperability and integration series;

— providing a summary of the content of each part in the supply chain interoperability and integration series;

— establishing the relationship of the supply chain interoperability and integration series to other international standards.

The following are outside the scope of this document:

— the interoperability and integration of the physical objects or services exchanged

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

ISO 8000‑114, Data quality — Part 114: Master data: Application of ISO/IEC 21778 and ISO 8000-115 to portable data

ISO 8000‑115, Data quality — Part 115: Master data: Exchange of quality identifiers: Syntactic, semantic and resolution requirements

ISO 8000‑116, Data quality — Part 116: Master data: Exchange of quality identifiers: Application of ISO 8000-115 to authoritative legal entity identifiers

ISO 8000‑118, Data quality — Part 118: Application of ISO 8000-115 to natural location identifiers

ISO 8601‑1, Date and time — Representations for information interchange — Part 1: Basic rules

ISO/DIS 25500‑2, Supply chain interoperability and integration — Part 2: Vocabulary

ISO/DIS 25500‑3, Supply chain interoperability and integration — Part 3: Verification of trading entity identity

ISO/DIS 25500‑100, Supply chain interoperability and integration — Part 100: Verification of supply chain data

For the purposes of this document, the terms and definitions given in ISO 25500-2 and the following apply.

ISO and IEC maintain terminology databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https://www.iso.org/obp

— IEC Electropedia: available at https://www.electropedia.org/

NOTE Prior to publication of this document as an International Standard, the following terms and definitions will be published in ISO 25500-2 and removed from this document.

3.1

authoritative legal entity identifier

ALEI

identifier assigned by the government agency that has granted and maintains an entity’s legal existence including its right to enter into legally binding contracts

EXAMPLE An identifier assigned by a government business register to reference a registered business.

Note 1 to entry: Government agencies are typically formed through legal actions such as proclamations, regulations, and acts and are not typically referred to by an identifier within those acts. Thus, a government agency’s legal name is its ALEI.

Note 2 to entry: ISO 8000-116 specifies how to represent the ALEI as an ISO 8000-115 compliant quality identifier making it an international business registration number (IBRN) while the ISO 25500-3 formatted international business identifier (IBID) includes the IBRN as part of a string that is used to definitively identify a legal entity

3.2

authoritative identifier

identifier issued by an entity that is the originator of the object identified or that is a legal authority

EXAMPLE The original part manufacturer issues the authoritative identifier for that part. Distributors can also assign identifiers, which are proxy identifiers (not authoritative identifiers).

Note 1 to entry: An authoritative legal entity identifier is an authoritative identifier issued by an organization that is a legal authority.

[SOURCE: ISO 8000-2]

3.3

authoritative source

originator of the object identified

3.4

callback security

system used for protecting a computer network, in which a user calls into a computer, which checks the person's username and password, ends the call, and then calls back the number or other form of address connected with that username and password

3.5

characteristic data

description of an entity by the class to which it belongs and a set of property values

[SOURCE: adapted from ISO 8000-2]

3.6

concept encoding

technique of replacing natural language terms in a message with quality identifiers that reference data dictionary entries

3.7

data

tangible, reinterpretable representation of information in a formalized manner suitable for communication, interpretation, or processing

[SOURCE: adapted ISO 8000-2]

3.8

dataset

characteristic data that describes the object or legal entity identified

3.9

date of origin

date of creation of a legal subject or object

3.10

identifier

string of characters created by an organization to reference a dataset

[SOURCE: ISO 8000-2]

3.11

identifier issuer

legal entity that issued the identifier referenced and so can resolve the identifier to the dataset it represents

Note 1 to entry: ISO 8000-115 specifies how a globally unique, registered prefix placed before an identifier indicates the identifier owner or issuer

Note 2 to entry: ISO 8000-116 specifies how to identify a legal entity through an international business registration number (IBRN) and ISO 25500-3 describes how to construct an international business identifier (IBID) to definitively identify a legal entity

3.12

industrial internet

efficient and trusted environment for sharing industrial data using callback security where the legal identity of the party requesting data verification and the legal identity of the party replying to the request are verified

Note 1 to entry: This is achieved by using registered ISO 8000-115 compliant prefixes where each prefix owner is identified with an ISO 25500-3 international business identifier, IBID. The IBID can be verified with the authoritative source as an active registration of a legal business. Routing the requests and the replies through an ISO 8000 prefix name server maintains the confidential electronic address information used for the exchange of verified data between known, verified legal entities.

Note 2 to entry: Adoption of the ISO 25500-1 supply chain data formatting contract clause supports the implementation of the industrial internet.

3.13

information

knowledge concerning objects and legal entities that within a certain context has a particular meaning

3.14

international business identifier

IBID

String of characters consisting of the three fields separated by the vertical line or pipe character (U+0007C) that uniquely identify a trading entity: the ISO 8000-116 formatted International Business Registration Number (IBRN), the legal name, and the date of origin as eight numeric characters (YYYYMMDD). This is presented as an ISO 8000-115 quality identifier that has ISO.IBID as the prefix, followed by a colon, followed by the string of characters.

Note 1 to entry: Some legal entities, such as government entities, gain and maintain their legal status through an act, proclamation, or regulation, and are not entered with an identifier at time of formation by the government authority that has originated them. For legal entities without a government issued identifier granted and entered into a register at time of formation, their legal name serves as their identifier. For these entities, the IBID consists of two fields separated by the vertical line or pipe character (U+0007C) that uniquely identify a trading entity: the ISO 8000-116 formatted International Business Registration Number (IBRN) and the date of origin as eight numeric characters (YYYYMMDD).

EXAMPLE 1 A corporation entered under the file number 3031657 and legal name Code Management Association into the business entity register of the United States’ state of Delaware on 1999-04-20 has an IBID of ISO.IBID:US-DE.BER:3031657|Code Management Association|19990420

EXAMPLE 2 An individual born 1922-01-17 and entered under the sequential number 54 and legal name Betty Marion White into the vital records register of the United States’ state of Illinois has an IBID of ISO.IBID:US-IL.VR:54|Betty Marion White|19220117

EXAMPLE 3 A government entity formed by the United States, through being signed into law on 1789-09-02, under the legal name of the Department of the Treasury has an IBID of ISO.IBID:US.GOV:Department of the Treasury|17890902

3.15

international business registration number

IBRN

ISO 8000-116 formatted identifier assigned to reference a legally authorised trading entity by a register maintained by the administrative agency for a governing body of the nation, state, or community with the authority to grant or terminate legal status to an entity including the entity’s legal right to enter legally binding contracts within a jurisdiction

Note 1 to entry: Businesses typically gain, preserve, and lose their legal status through entrance and maintenance in a government business register but not all entities receive legal status through inclusion in such a register database. For legal entities that are not added to a register database, one refers to the documents of formation that granted the entity its legal status such as proclamations, acts, or regulations for government entities. For such government entities, the legal entity may not be referred to by an identifier so its legal name also serves as its identifier with .GOV as the prefix subdomain element.

EXAMPLE 1 Code Management Association was formed in and is a registered corporation in the US state of Delaware (jurisdiction code: US-DE) where the Business Entity Register (register reference: BER) is maintained by the Division of Corporations. The business registration number for Code Management Association inside the Delaware Business Entity Register is 3031657. Code Management Association's IBRN is US-DE.BER:3031657.

EXAMPLE 2 The IBRN for the United States Department of the Treasury is “US.GOV:Department of the Treasury” as it is a government entity (.GOV) was formed when a congressional act was signed into law by President George Washington on 1789-09-02, in the legal jurisdiction is the United States (US) and its legal name is Department of the Treasury.

3.16

jurisdiction

territory within which a court of law exercises its authority

Note 1 to entry: ISO 8000-116 defines how a jurisdiction prefix is created using ISO 3166-1 and ISO 3166-2 (country and subdivision codes)

3.17

legal entity

physical or juridical person granted legal status by the governing body of a nation, state or community

[SOURCE: ISO 8000-2]

3.18

legal name

name of the organization as recorded in the authoritative legal entity registry where the organization was formed

3.19

onboarding

process of collecting and validating the data necessary to approve a new supplier, material, or service prior to the creation of a master data record

Note 1 to entry: Before a purchase order can be created a supplier master data record must exist.

Note 2 to entry: A purchase order will either reference an item (material or service) master data record or include descriptive text to identify and describe the item to be purchased.

3.20

place of origin

location where a subject or an object is created

3.21

prefix name server

PNS

ISO 8000-115 compliant register of prefixes with globally unique prefix records that contain the legal owner of any identifier with that prefix and provides an electronic address to resolve the identifier to the dataset it represents as well as any use restrictions.

3.22

proxy identifier

identifier issued by an organization that is not the originator of the object identified

[SOURCE: ISO 8000-2]

3.23

quality identifier

ISO 8000-115 compliant identifier where a registered and globally unique prefix is used to identify the legal owner of the identifier and provides an electronic address to resolve the identifier to the dataset it represents as well as any use restrictions.

3.24

register

business register

register maintained by the administrative agency for a governing body of the nation, state, or community with the authority to grant or terminate legal status to an entity including the entity’s legal right to enter legally binding contracts within a jurisdiction

EXAMPLE In the state of Delaware (in the United States), the Division of Corporations is the administrative agency that issues identifiers for juridical persons represented on documents of formation. This agency maintains the authoritative legal entity register for corporations in the state of Delaware.

Note 1 to entry: For legal entities that are not added to a register database, one refers to the documents of formation that granted the entity its legal status such as acts or regulations for government entities.

3.25

supply chain data formatting contract clause

requirement exchanged between trading entities to ensure the unambiguous identification and description of "who," "what," "where," and "when" to when sharing data between supply chain stakeholders

Note 1 to entry: ISO 25500-1 provides an example of a supply chain data formatting contract clause

3.26

trading entity

contracting entity

legal entity (such as an individual, business, government agency), involved in buying or selling in the supply chain, which has been granted legal existence and right to enter into a legally binding contract and be a party in court through its creation and maintenance of active legal status by a government agency

Note 1 to entry: ISO 8000-116 specifies how to identify a trading entity, or any legal entity, through an authoritative legal entity identifier, identifier issued by government authority originating it, formatted as an international business registration number (IBRN); ISO 25500-3 describes how to construct an international business identifier (IBID) to definitively identify a trading entity or any legal entity with ISO 8000-115 compliant prefix of ISO.NLI and the entity’s IBRN, legal name, and date of origin; and ISO 25500-3 describes how to verify trading entity data with the authoritative source through an automated process.

The industrial Internet, along with supply chain interoperability and integration, is represented by an intelligent service model which can be used to improve the quality of the data necessary for demand forecasting and logistics management across independent systems encompassing the orchestrate, plan, order, source, make, deliver, return and disposal functionality in a modern sustainable economic framework.

Data verification is achieved by implementing a standard process for requesting:

a) the verification of identifiers;

b) the characteristic data the identifier represents; or

c) using characteristic data to search for identifiers.

This data verification process is built on key data pieces which can be secured by trading partners by including a supply chain data formatting clause in their contracts.

Modern supply chains are data-intensive; they involve multiple stakeholders who need to ensure that the data they exchange is unambiguous and can be trusted.

A supply chain data formatting contract clause shall require standardization (including ISO 8000 and ISO 25500) designed to ensure the unambiguous identification and description of "who," "what," "where," and "when" to ensure clarity and consistency when sharing data between supply chain stakeholders. Table 1 provides an example of a supply chain data formatting contract clause.

Table 1 — Illustration of a supply chain data formatting contract clause

ISO 25500 presents the essential components of the industrial internet with the supply chain data formatting contract clause bringing in from trading partners key data and by providing a standard process for data verification to occur in a secure environment. This process uses registered ISO 8000-115 prefixes for both parties and callback security that routes the requests and the replies through a PNS. The PNS maintains in each prefix record the IBID to definitively identify the prefix owner while protecting privacy by keeping confidential the electronic address information used for the verified data exchange.

The ISO 25500 series provides standards in the field of supply chain interoperability and integration for industrial enterprises that leverages artificial intelligence (AI) as the new generation of information technology, flexible manufacturing technology, and structurally flexible supply chains.

The ISO 25500 series is intended to research, develop, and maintain international standards for an eco-system that promotes interoperable, integrated, and sustainable supply chains via an industrial internet.

To accomplish the goal, the ISO 25500 series pursues the following objectives: provide a foundation for effective, efficient, and safe supply chain interoperability and integration; maintain a central repository of terminologies used in the ISO 25500 series of standards; and define the formatting of requests for and responses to requests for verification of supply chain data on entities and items, operating procedure, and asset descriptions in a formalized manner suitable for automated processing.

The ISO 25500 series addresses three broad areas of standards’ development:

a) general aspects of supply chain interoperability and integration like the series overview and vocabulary;

b) verification of supply chain data through automated processing utilizing APIs; and

c) interoperability and integration in supply chain operating procedures such as procurement, warehousing, make, order processing, and logistics.

The general aspects of supply chain interoperability and integration area include foundation standards for the ISO 25500 series. ISO/DIS 25500-1 (this document) outlines and describes the series, principles of the industrial internet, and what we mean by supply chain interoperability and integration. This section also has a vocabulary part (ISO/DIS 25500-2) that serves as a repository for the terms and concepts used across the series for the sake of simplicity and consistency. Additionally, trading entity (like suppliers, buyers, manufacturers) identity verification through an automated process to verify legal party data with the authoritative source (ISO/DIS 25500-3) is taken as a first step before any other verification of data and so falls under the general aspects of supply chain interoperability integration.

The second area of the ISO 25500 series is the verification of supply chain data through automated processing using the industrial internet as described in this document. This section is on exchange of verified data between a requestor and respondent with verified legal identities routing the data through a PNS and specifies how to format the requests for and replies to requests for verification of supply chain data on entities and items. This begins (ISO/DIS 25500-100) with a generic structure of an application programming interface (API) to verify or request supply chain data. This structure uses ISO 8000 data quality principles and formatting and has three general data requests: 1) verify - where the request is sent to the identifier issuer with an identifier and response validates or rejects the identifier, 2) resolve - where the request is sent to the identifier issuer with an identifier and the reply is the complete dataset that the identifier issuer is willing to send, and 3) search - where the request is sent to the identifier issuer with the request that includes characteristic data and the reply is the possible matching identifier(s).

As some forms of data are increasingly requested in the supply chain and there is some confusion on what to request and to whom, there are also some standard parts to automate verification of specific supply chain data. For instance, certificates (ISO/DIS 25500-110) are essential to the functioning of the supply chain; there are certificates for potential trading entities (i.e., health or safety inspected, minority-owned business, no forced or child labor, fair trade, environmental responsibility, licenses), products (i.e., quality, safety, testing, content, function), services (i.e., completion of service), and people (i.e., trainings, licenses, education). Additionally, verifying item origin data (ISO/DIS 25500-120) to buy local or to avoid specific locales, as a means to support the local community, for political goals, and for supply chain resiliency (decreased transport related delays, expenses, environmental impact, and effect from tariffs) is often a supply chain priority for individuals, businesses, or governments.

The third area, operating procedures in supply chain interoperability and integration, focuses on the day-to-day processes of supply chain management such as procurement, warehousing, make, order processing, and logistics. For instance, a standard (ISO/DIS 25500-240) in this section covers fundamental concepts, principles, and vocabulary of the strategic sourcing process for effectively and efficiently onboarding products or services from new or existing suppliers. The standards in this section elaborate and organize steps to meet data sharing needs in each supply chain management task while referencing the supply chain interoperability and integration foundation elements and functionalities provided in the first two areas of the series to support their fulfilment.

All three sections draw on one another, for purpose and form, to constitute an in-depth understanding of and toolkit for the reader interested in supply chain interoperability and integration.

Table 2 — Overview Outline of the Structure of the Supply Chain Interoperability and Integration Series

Where relevant to its scope, the ISO 25500 series incorporates existing standards. The ISO 25500 series is focused on general aspects of supply chain interoperability and integration; the development of automated processing, particularly API, standards that facilitate supply chain interoperability and integration through interactive requests for data or the verification of data from an authoritative source through a secure callback communication channel while maintaining privacy with no access to the contact information of the requestor and sender and no personally identifying contact information collected or utilized; and operating procedures in supply chain interoperability and integration. This is different, for instance, from the standards developed under ISO/TC 154 on Electronic Data Interchange (EDI); the fundamental principle of EDI is the exchange of data based upon an already established trading partner agreement that identifies a specific implementation of an EDI standard where the optional segments, data elements or codes defined in the standard are agreed upon as mandatory. Where a user would implement TC 154 EDI standards to send transaction data to an established trading partner, a user would implement the ISO 25500 series protocols between verified legal entities to request specific supply chain data or the verification of specific supply chain data through a PNS.

The ISO 25500 series, as presented in this document, makes a unique contribution to supply chain interoperability and integration. The standards in the series benefit from existing standards, especially those within and across the suite of ISO/TC 184/SC 4 and ISO/TC 184/SC 5 standards. The ISO 8000 series for data quality, coming from ISO/TC 184/SC 4, brought key elements for formatting the data but was limited in requests and verification through automated processes. ISO 19450 Automation systems and integration — Object-Process Methodology, coming from ISO/TC 184/SC 5, is able to flesh out and clarify with models and their generated text the processes described in multiple parts of this series.

Supply chain contracts conform to this document when the requirements of 4.2 are included.

1. 
   (informative)
   
   Document identification

To provide for unambiguous identification of an information object in an open system, the following object identifier is assigned to this document. The meaning of this value is defined in ISO 10303-1.

{ iso standard 25500 part(1) version(1) }

1. 
   (informative)
   
   Supply chain data formatting contract clause - elaborated

Beyond a general inclusion of a supply chain data formatting contract clause, trading partners may wish to point to a more detailed explanation and example for each supply chain data element in the contract clause. Specifically, the key supply chain data formatting contract clause elements can be elaborated upon by drawing from the below:

• 1. Date

All dates and times shall be formatted in accordance with ISO 8601.

EXAMPLE The ISO 8601 format for 11^th day of October in the year 2025 is 2025-10-11.

• 1. Trading entity identification

All legal entities supplying goods or services under this contract shall be identified by their ISO 25500 International Business Identifier (IBID) or their legal name and International Business Registration Number (IBRN) formatted in compliance with ISO 8000-116.

NOTE 1 An IBID combines the ISO 8000-116 formatted IBRN, the legal name, and the date of origin all separated by a pipe symbol (Unicode character 007C) and is presented with the ISO 8000-115 prefix of ISO.IBID.

NOTE 2 An ISO 8000-116 formatted IBRN consists of a jurisdiction prefix composed of an ISO 3166-1 or ISO 3166-2 and authoritative legal entity register code separated by a period symbol (Unicode character 002E) followed by a colon character (Unicode character 003A) and the local authoritative legal entity identifier (ALEI) assigned by the authoritative legal entity register that granted and maintains legal existence for the legal entity.

EXAMPLE Code Management Association was formed on 1999-04-20 in the US state of Delaware, recorded under the file number 3031657 in the business entity register; its IBRN is US-DE.BER:3031647 and its IBID is ISO.IBID:US-DE.BER:3031647|Code Management Association|19990420

• 1. Location identification

All locations shall be identified using a Natural Location Identifier (NLI) formatted in compliance with ISO 8000-118.

NOTE An ISO 8000-118 formatted identifier for location has an ISO 8000-115 prefix of ISO.NLI followed by a colon character (Unicode character 003A) and a 14-digit string, generated through an algorithm described in ISO 8000-118, that combines latitude, longitude, and floor or elevation.

EXAMPLE The second floor of the Eiffel Tower is represented by ISO 8000-118 natural location identifier of ISO.NLI:9CQQBY9B96F1H2

• 1. Item identification

All items shall be identified using an international part number (IPN) formatted in compliance with ISO 8000-115.

NOTE 1 An identifier that fully conforms to ISO 8000-115 is an identifier where a registered and globally unique prefix is used to identify the legal owner of the identifier and provides an electronic address to resolve the identifier to the dataset it represents as well as any use restrictions.

EXAMPLE 3SCI is a prefix registered to 3-SCI LTD. under the IBID of ISO.IBID:GB-EAW.CR:08640185|3-SCI LTD|20130806 and includes an electronic address to resolve identifiers as well use restrictions. A part number WI-CORR WU101 issued by 3-SCI LTD. is formatted as 3SCI:WI-CORR WU101.

NOTE 2 3SCI:WI-CORR WU101 is formatted as an IPN in compliance with ISO 8000-115. A prefix registry record that holds simply the IBID is not a fully ISO 8000-115 compliant record as it does not contain an electronic address to resolve identifiers as well as use restrictions but is compliant with ISO 25500-1 A.4 for the purpose of identifying the legal owner of the identifier and so who would be able to resolve it to the dataset behind it and confirm any use restrictions.

• 1. Item description

The technical data that describes the physical, functional, and performance characteristics of an item, component, or process shall be provided in Interoperable Data Format (.idf) as described in ISO 8000-114. This format removes ambiguity through the use of concept encoding, a simple process where metadata and reference data are represented by ISO 8000-115 identifiers from an open technical dictionary. Values are also represented in the ISO 8000-115 format where appropriate (part numbers or asset numbers for example).

EXAMPLE Table B.1 — shows item characteristics as a set of attribute-value pairs but with no concept encoding and not in JSON; Table B.2 is the same data in ISO 8000-114 compliant format with concept encoding and in JSON syntax.

Table B.1 — Noncompliant representation of item characteristics with no concept encoding and not in JSON

Table B.2 — ISO 8000-114 compliant presentation of item characteristics with concept encoding and in JSON syntax.

Bibliography

[1] ISO 19450, Automation systems and integration — Object-Process Methodology

[2] ISO/DIS 25500‑110, Supply chain interoperability and integration — Part 110: Verification of certificates in the supply chain

[3] ISO/DIS 25500‑120, Supply chain interoperability and integration — Part 120: Verification of data in support of local purchasing

[4] ISO/DIS 25500‑240, Supply chain interoperability and integration — Part 240: Strategic sourcing concepts, principles, and data requirements