.reqifzSample standard as ReqIF
A complete standard, broken down into individual, classified requirements.

VDE Nexus delivers standards content as SMART Standards: classified requirements in ReqIF format. You import them directly into your requirements tool and track changes requirement by requirement.
4 requirements importedDIN DKE SPEC 99200
IEC 60601-1:2020
Properties
Select a requirement to see its properties.
VDE Nexus AI
Connected via MCP
Focus: IEC 60601-1 · 9.2.2.4Answers from all standards
Illustrative example: standard texts are simplified, values and references are examples.
The basics
ReqIF is an open standard of the OMG and transfers text, structure, attributes and relations between tools.
For reading and reviewing
The complete text of the standard as a document.
For further processing
Every requirement as an object of its own, with ID, attributes and relations.
Provision types
Every statement carries attributes for its object type, its modality and its classification as normative or informative.
The modality follows the drafting rules of the ISO/IEC Directives, Part 2, and DIN 820-2: shall, should, may and can are marked consistently.
Because the modality is a separate attribute, you can filter your tool specifically for requirements, recommendations or permissions.
Standard number, title, date of publication and further metadata come from the official sources, not from manual entry.
Every statement keeps its position in the structure and receives a stable ID. When a new edition is published, you can see what is new, changed or removed.
.reqifzA complete standard, broken down into individual, classified requirements.
Project template with a ready-made import mapping for the data fields of SPEC 99200, including standardized attribute display. No manual configuration for each import.
Provided by DIN and DKE in the public GitHub repository for DIN DKE SPEC 99200.Open repository(opens in a new tab)
Advisor
Choose a question from the list or type a keyword. The advisor answers briefly and takes you to the right place on this page.
VDE Nexus Advisor
Answers reviewed by the VDE Nexus team
I don’t have an answer to that. I’m happy to pass your question on to a person.
Send question to salesHello! I answer your questions about ReqIF and about standards in ReqIF format from VDE Nexus: from the file format and the provision types of statements to the import into your system. Where shall we start?
An open, vendor-neutral standard of the Object Management Group (OMG) for exchanging requirements. The XML-based format transfers text, structure, attributes and relations, between tools and across company boundaries.
More on this: The basicsBesides a header with metadata, it consists of a few building blocks:
A .reqif file is a single XML file. A .reqifz file is a ZIP archive containing one or more ReqIF files together with embedded objects such as images.
PDF is well suited to reading and reviewing the complete text of a standard. ReqIF adds what further processing needs: every requirement enters your system as an object of its own, with ID, attributes and relations, without copy and paste and without media breaks.
It defines how standards are provided in ReqIF format: with metadata, the provision type of every statement and a consistent breakdown into requirements. DIN and DKE developed it together with the Initiative Digital Standards (IDiS); it was published in February 2025.
Every statement carries an attribute for its modality. It follows the drafting rules of the ISO/IEC Directives, Part 2, and DIN 820-2:
Into statements that can be understood on their own. A paragraph, a table or a list stays together if it forms a unit in terms of content. Every statement keeps its position in the structure and receives a stable ID.
The format does not change the status of a standard. Standards are technical rules whose application is generally voluntary. They become binding when laws, contracts or tenders refer to them. This answer does not constitute legal advice.
Into requirements management systems such as IBM DOORS, Siemens Polarion, PTC Codebeamer and Jama Connect, and into PLM systems such as Dassault Systèmes CATIA and Siemens Teamcenter. How completely attributes and formatting are adopted depends on the tool and its configuration.
More on this: Try itEvery requirement has a stable ID, so you can see which requirements are new, changed or removed. Many tools merge a new delivery with existing data, for example IBM DOORS or PTC Codebeamer from version 9.3.
More on this: Try itYes, that is exactly what the format is made for. You link requirements from standards to system or product requirements and to test cases. This creates end-to-end traceability for conformity evidence and audits.
Yes. Formatted text, lists and tables are transferred as XHTML, images as embedded objects. How well they are displayed in the target system depends on the tool.
Yes, with the sample standard: it comes from the public GitHub repository of DIN and DKE, and you can download it right here on this page. For anything else, write to our sales team: vertrieb@vde-sis.de.
More on this: Sample standardVia the VDE Nexus platform: in the publication list, the ‘Licensed’ and ‘Format’ columns show which standards you can use. You start the download in the publication details or retrieve the files via the API.
More on this: Try itWe agree the selection of standards, scope and delivery method with you individually. Our sales team will send you a quote: vertrieb@vde-sis.de.
The advisor replies with editorially reviewed texts. Your selection and input are neither stored nor transmitted.
Your question isn’t listed?
Then we will answer it for you personally.