ISO 8000 FAQsEverything you need to know about ISO 8000 .....
Why exchange product data with your customers using international standards
Exchanging quality, characteristic, master data is covered by the international data standards ISO 22745 and ISO 8000, and an internationally recognised form of electronic data exchange. ISO 22745 was developed from the NATO standard for exchanging spare parts data in multiple languages, often in hostile environments. The essential premise of ISO 8000 is that master data should be machine readable, portable between systems, and exchangeable in multiple languages without loss of meaning.
What types of organisations are adopting ISO 8000?
The single biggest example of exchanging spare parts data to the ISO 22745 standard is NATO. NATO is an international alliance that consists of 28 member states, and is able to exchange spare parts data in the native language of all member states. On the international stage, the Kingdom of Saudi Arabia, a G20 country, is currently adopting ISO 8000 as the standard for their national industrial information centre. Adoption of this standard also covers the description of all industrial items that are to be imported into this country.
Other states are now looking to adopt the ISO 8000 standard for the description of goods for import and export, as items described using this standard can be automatically mapped to customs tariff codes to ensure that the correct level of duty is paid, and accurate trade statistics can be collated and analysed. There are current discussions, in both national and global oil and gas companies, to introduce this standard as part of engineering and procurement (EPC) contracts as part of the efforts in the oil and gas sector to reduce costs in the new world of the $50 barrel of oil.
Who is going to ask me to supply ISO 8000 standard technical specification?
If you export to the Kingdom of Saudi Arabia, this will become standard practice for your customs submission. A number of leading global companies are now adopting ISO 8000, and as manufacturers you will increasingly be asked by end-users to validate their data using the ISO exchange standards, or you will be asked as part of the purchase order to supply data to these standards.
There is also a pilot project about to start with a consortium of oil and gas super majors, where they are looking to use ISO 22745 and ISO 8000 to manage data throughout the asset lifecycle from design through to de-commissioning.
What contract wording will require us to produce specifications to ISO 8000?
Example clause to include quality data as part of the supply of an item, equipment, or service.
The contractor, sub-contractor or supplier shall, as and when requested to do so, supply technical data in electronic format on any of the items covered in this contract as follows:
- The data shall be encoded using concept identifiers from an ISO 22745 compliant open technical dictionary that supports free resolution to concept definitions.
- The data shall comply with the specified ISO 22745-30 compliant data requirements.
- The data shall be provided in ISO 22745-40 compliant Extensible Markup Language (XML)
- The data shall be ISO 8000-110 compliant
- All identifiers must be ISO 8000-115 compliant
Do we have to create a new set of data to produce ISO 8000 technical specifications?
No, the technical data you currently have that sits in your product information system, or you use to populate your website or is written in product PDF documentation can all be used as the source of your ISO 8000 compliant technical specification.
Does this mean competitor manufacturers must standardise terminology?
No, in this context, a standard technical specification means a technical specification to ISO 8000-110. The methodology employed is the foundation for how items can be described in multiple languages without loss of meaning. This also allows manufacturers to use terms that are familiar internally and to their existing clients, but also allows for the mapping of those terms to established definitions from the standards that the manufacturer produces their product to, such as ISO 5593 – Rolling Bearings – Vocabulary.
Who owns the data?
ISO 22745, and ISO 8000 assert that the owner of the data is the person who manufactured the product, not the re-seller of the product, nor the end-user of the product. That is why KOIOS Master Data is helping manufacturers to create the data that populates an open registry.
Where do the technical specifications we create go to?
When you have completed your technical specification using KOIOS, it is uploaded to a global registry managed by the electronic commerce code management association (ECCMA). It is free to upload your data to this registry.
Do we have to upload our data to this registry?
No, if you wish to manage your own data, you can use your own resolution server. The full domain name for this must be entered when you complete your QUIP registration through your KOIOS account.
How much does it cost us to upload to this registry?
There is no cost to upload a record to the registry, and there is no cost to download a record from the registry. However, to be able to upload a record to the registry, the part number, or identifier, must comply to ISO 8000-115. This requires the purchase of a domain prefix for $500. This prefix works in much the same way as your domain name, and ensures that you are identified as the legal owner of the record.
Do we have to create a new data file for each customer that uses or sells our product and wants the technical specification?
No, when you upload your record to the registry you are supplied with a reference from the registry that can be shared with all your clients, and with the customs authorities in the Kingdom of Saudi Arabia.
What is the charge for customers to download from this registry?
There are no charges for your clients to download your records from the registry.
What happens to the technical specifications on our own website that are currently in PDF or HTM?
You keep those as you normally do, the standard technical specification is a third way of sharing your data.
How will this change the current process of data exchange in the supply chain?
This process will make it easier to exchange data throughout the supply chain, and to maintain that data through the life-cycle of an asset that your item might be part of. In major capital projects, it will eliminate the need for vast libraries of PDF documents containing spare parts information and the associated issues with that.
Does this affect the products we purchase as manufacturers?
The same process applies to items you buy, either as part of your manufacturing process, or as part of your maintenance spend.
What is the benefit to the manufacturer, distributor and end user?
The new registry will make it easier for manufacturers to distribute the data to their clients, whether they are distributors or end-users. Importing an XML file of data created by the manufacturer means that the data has provenance, and saves on third-party data cleaning projects.