	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

Project Documentation Requirements
Auftraggeber / Endkunde / End Customer: Uniper Hydrogen GmbH Holzstrasse 6 40221 Düsseldorf, Deutschland
Auftragnehmer / Kontraktor / Contractor:
Ingenieurdienstleister / Engineering Subcontractor:
Projekt Nr. / Project No.:				KKS RDS-PP:	n/a
Endkunde / End customer Document ID: HITW-UNI-DM-ACC050-0001				Phase: Phase:			Concept
				DCC Bereich/Schlüssel:			ACC050
EPC-Kontraktor / EPC-contractor Document ID:				DCC Area/Key: Dok.-typ: Doc.-Type:			Terms of delivery
				Zweck: Purpose:			Issued for Tender
Ingenieurdienstleister / Eng. subcontractor Document ID:				Vertraulichkeit: Confidentiality:			Public
				Disziplin: Discipline:			Document Management
Weitere Hinweise und Bemerkungen / Further notes and remarks:							Überprüfungsstatus / Review status:
Rev.	Änderung / Beschreibung - Change / Description					Status / Status		Datum / Date
00	First issue					Released		17.06.2026
Erstellt von / Created by		Geprüft von / Reviewed by	Geprüft von / Reviewed by			Geprüft von / Reviewed by		Freigegeben von /
								Approved by
Name / Signatur: Name / Signature: Rejan Niemeyer		Name / Signatur: Name / Signature: Thorsten Gröning	Name / Signatur: Name / Signature: Lukas Kivilip			Name / Signatur: Name / Signature:		Name / Signatur:
								Name / Signature:
								Thorsten Gröning
Funktion / Abteilung: Function / Department:		Funktion / Abteilung: Function / Department:	Funktion / Abteilung: Function / Department:			Funktion / Abteilung: Function / Department:		Funktion / Abteilung:
								Function / Department:
DM		TPM	Project Engineer
								TPM

Project D ocumentation Requir ements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	1/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

2 Revisionsprotokoll / Revision record

Rev. No. Grund der Revision / Reason for Revision Datum / Date

00 Frist Issue 17.06.2026

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	2/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

5 Table of Content

6 1 Purpose .................................................................................................................... 4 7 2 Scope ........................................................................................................................ 4 8 3 Terms and Abbreviations ........................................................................................ 4

9 3.1 Abbreviations ............................................................................................................. 4 10 3.2 Definitions .................................................................................................................. 5

11 4 Applicable Standards .............................................................................................. 6 12 5 Document Management Between Uniper and Contractor ..................................... 6

13 5.1 Delivery of Documentation ......................................................................................... 6 14 5.1.1 Use of Uniper DMS .................................................................................................... 6 15 5.1.2 Contractor Document List (CDL) ................................................................................ 6 16 5.1.3 Exchange and Review of Documents ......................................................................... 6 17 5.2 Minimum Requirements for Documents ..................................................................... 8 18 5.2.1 Document Templates ................................................................................................. 8 19 5.2.2 Document Format ...................................................................................................... 9 20 5.2.3 Document Metadata in Uniper DMS ........................................................................... 9 21 5.2.4 Document Numbering .............................................................................................. 10 22 5.2.5 Identification of Confidentiality .................................................................................. 11 23 5.2.6 Document Revision Protocol .................................................................................... 11 24 5.3 Engineering Drawings (2D – 3D) .............................................................................. 11 25 5.4 Project Language ..................................................................................................... 12 26 5.5 Scanning of Documents ........................................................................................... 12

27 6 Final Documentation .............................................................................................. 12 28 7 Project Coversheet ................................................................................................ 13 29 8 Drawings Header/Block title .................................................................................. 14 30 9 Further Guidelines and Procedural Instructions ................................................. 14 31 10 Annex ...................................................................................................................... 14 32

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	3/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

34 1 Purpose

35 This document defines Uniper’s documentation requirements for the FEED phase of the HITW 36 project and regulates the handling of documents and information within the project HITW. It also 37 outlines the procedures for managing documents and information flow, ensuring that all project 38 participants receive and have access to the necessary information for their specific roles during 39 the design, construction, first commercial start up, commissioning, and operation phases. In 40 addition, this document defines formal rules on how documentation and information should be 41 produced and distributed.

42 2 Scope

43 This document applies to the Project and is binding for the entire project team (FEED 44 Contractors/3rd Parties/Uniper). It covers all the project activities in the project FEED phase as 45 required and as defined in the Scope of Work. These formal requirements apply to all project 46 participants.

47 3 Terms and Abbreviations

48 3.1 Abbreviations

49 CDL Contractor Document List 50 CE Conformité Européenne/Declaration of Conformity 51 DCC Document Kind Classification Code 52 DIMP Document Information Management Plan 53 DMS Uniper Standard Document Management System 54 LoD ist of Deliverables as per Contract 55 MDR Master Document Register 56 HITW Hydrogen Import Terminal Wilhelmshaven 57 PDF Portable Document Format 58 QA/QC Quality Assurance/Quality Control 59 UNI Any/all Uniper legal entities with involvement in the project

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	4/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

61 3.2 Definitions

Document/ In the DIN EN 82045-1 standard, the term "document" is Documented described as follows: "A document is a fixed and structured set of Information information that can be exchanged as a unit between users and systems and must always be reproducible from the content to a revision status."

In the current version of ISO 9001, ISO 14001, ISO 45001, the term "documents" is no longer used, and the more all- encompassing term "documented information" is used instead. Electronically documented information can consist of multiple files, even from different applications. A documented information can represent any information without restriction of type or form. In this document, the term "documents/files" is used for better readability. If "documents/files" or "data" are mentioned individually, it is to be assumed that both terms may be used.

Document Document management system refers to the database-supported Management System administration of electronic documents. This also includes the (DMS) management of digitized, originally paper-based documents.

Uniper standard DMS is the leading DMS in the project. All project-relevant documents are stored in the Uniper DMS.

Metadata Metadata is information about data. It is data that describes the document and facilitates archiving and retrieval. In a paper archive, metadata are indexes, detail lists, registers, author's name or other search aids. Metadata is used wherever large amounts of data need to be clearly summarized so that they can be quickly recorded.

“Agreement”, or Refers to the agreement to be signed between Uniper and the “Contract” Contractor with all annexes and documents incorporated therein.

Uniper Refers to all Uniper legal entities

Contractor Refers to successful Bidder selected and employed by Uniper for the FEED Contract, which shall provide the services as defined in the Scope of Work.

Scope of Work Services to be provided by the FEED Contractor as defined in the document HITW-UNI-GE-ACC070-0002-FEED Scope of Work.

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	5/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

64 4 Applicable Standards

65 The following standards are to be considered in any case beyond the definitions in this document. 66 This document further supplements or specifies the requirements.

67 • IEC 61355-1 “Classification and designation of documents for plants, systems and 68 equipment“

69 5 Document Management Between Uniper and Contractor

70 5.1 Delivery of Documentation

71 5.1.1 Use of Uniper DMS

72 All documents which are contractually agreed and/or required for the execution of the project 73 phase(s) or the subsequent operation of the plant shall be managed within Uniper’s project 74 document management system (Uniper DMS).

75 All digital documents related to the Contractor’s scope shall be uploaded by the Contractor to 76 the Uniper DMS. Uniper will provide the necessary access rights and training for this purpose.

77 5.1.2 Contractor Document List (CDL)

78 Contractor shall develop a CDL according to the FEED Scope of Work (therein called Master 79 Document Register – MDR). For this, the attached CDL template shall be used by the 80 Contractor.

81 5.1.3 Exchange and Review of Documents

82 Document exchange takes place exclusively in the Uniper DMS. The Contractor is responsible 83 for uploading his documents in the Uniper DMS, according to the requirements outlined in this 84 document.

85 5.1.3.1 Submission Process for Contractor Documents

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	6/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

87 1. The Contractor uploads the documents to the Uniper DMS for review and initiates the 88 submission by selecting "Submit for review" and completing all required steps. 89 2. The submitted documents are routed through the DMS to the Uniper Document Controller 90 for a formal check of the submitted document. The document is either accepted for content 91 review or formally rejected for resubmission. 92 3. The Contractor receives a notification via email (digital transmittal) through the Uniper 93 DMS with the review results.

94 5.1.3.2 Issue Purpose to Uniper

95 The Contractor shall record the defined issue purpose for each submitted document in the CDL, 96 designated field on the document at submission, and include it in the corresponding metadata 97 when uploading to the Uniper DMS.


				noitacifitnedI	tpecnoC	DEEF	liateD	noitcurtsnoC	gninoissimmoC	revodnaH
Issue purpose abbreviation		Purpose
	Issue
	purpose
	abbreviation		Purpose
	IFR		Issued for Review	x	x	x	x	x	x
	IFRx		Issued for extended review		x	x	x	x	x
	IFI		Issued for Information	x	x	x	x	x	x
	IFT		Issued for Tender			x	x	x	x
	IFF		Issued for FEED	x	x	x
	IFA		Issued for Approval	x	x	x	x	x	x
	IFP		Issued for Permit		x	x	x	x
	IFH		Issued for Hazop			x
	IFC		Issued for Construction				x	x	x
	IFM		Issued for Commissioning				x	x	x
	ASB		As Built							x
	WTH		Withdrawn	x	x	x	x	x	x	x

WTH Withdrawn

98 5.1.3.3 Release of the Reviewed documents

99 All documents that have been reviewed by Uniper are given a status at the end to indicate the 100 outcome of the review. The review result is indicated as follows:

Review status (Processing)
Issue purpose code	Review status	Description	Action
All	Under review	This status indicates that the formal check of all submitted documents has been completed by the Document Controller	Document to be forwarded internally to the technical team for their review
All	Formally rejected	Formal check completed with comments; to be resubmitted for review	Document does not meet the project documentation requirements. Resubmission required
IFI, ASB, WTH	Acknowledged	Documents submitted for information purposes	Document is to be distributed internally with the relevant team

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	7/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

Documents submitted for information IFI, ASB, Acknowledged Feedback on the submitted document purposes that contain incomplete or WTH with comments requires discussion and resolution incorrect information

IFR, IFRx, IFP, IFT, IFF, IFH, IFC, IFM	Accepted	This status is used for documents submitted for review, permit and/or construction	Document is accepted and can be transferred in further work status, if required
IFR, IFRx, IFP, IFT, IFF, IFH, IFC, IFM	Accepted with comments	This status is used for documents submitted for review, permit and/or construction that contain parts or information that have been commented upon	Document is conditionally accepted with comments. Document can be transferred in further work status if required. However, comments must be taken into account, and the document should be resubmitted, if necessary
IFR, IFRx, IFI, IFT, IFF, IFA, IFP, IFH, IFC, IFM, ASB	Rejected	Review completed with comments; to be resubmitted for review	Document has significant deficiencies and/or is incomplete. Resubmission required
IFA	Approved	This status is used for documents submitted for approval	Document is approved
IFA	Approved with comments	This status indicates that the document submitted for approval contains parts or information that have been commented upon	The document is approved. However, comments must be addressed, and the document should be resubmitted in compliance with the contract and/or the agreed-upon scope

101

102 5.2 Minimum Requirements for Documents

103 5.2.1 Document Templates

104 All official project documents submitted to Uniper must use Uniper’s defined templates, including 105 cover sheets for text documents and lists, as well as the standard Uniper title block for drawings 106 (in drawings or documents with format >DIN A4).

107 Uniper shall provide the Contractor with a native file format of the project cover sheet and drawing 108 title block after the contract is signed. (project cover sheet & drawing header)

109 All cover sheet fields including header and footer, and the drawing title block must be filled in. The 110 structure of the three-page cover sheet for text documents is as follows:

111 • Page 1: General information such as document number (Uniper & Contractor), revision 112 number, description, status 113 • Page 2: Revision protocol, on-hold points, list of annexes, other applicable documents

114 The following information must be listed on the drawing title block used by the Contractor:

115 • Project title 116 • Plant section (Part of the plant shown in the drawing in plain text) 117 • Document title (Plain text description of the drawing, in the project-specific language) 118 • DCC (Document Classification Code) 119 • Uniper document number & revision number (Uniper document number and associated 120 revision, separate from each other)

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	8/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

121 • Contractor document number & revision number (Document number and associated 122 revision of the issuing company, separately from each other) 123 • Sheet No. (Page number (# of #)

124 The following information is included in every document

Designation Indication Designation Indication

Project name Project name Document title Each document shall be given a unique and (defined by (subject, topic) meaningful title Uniper) Project identifier Project code Contractor Name / company name of the Contractor (defined by Uniper) Project no. Unique project Engineering Sub-contractors, manufacturers and number (defined service suppliers are to be considered as by Uniper) provider engineering service providers Customer End customer

125 5.2.2 Document Format

126 All documents shall be submitted digitally as searchable (OCR – Optical Character 127 Recognition) PDFs (Portable Document Format) for review. The final documentation shall be 128 submitted as PDF and native file. In case of special application software and related special file 129 types, the format(s) shall be aligned with Uniper.

	Item		Software / Format
Text, databases, spreadsheets	Text, databases, spreadsheets	MS Office latest version	MS Office latest version
P&IDs		See (Engineering Data 2D-3D) for further information
	Drawings	See (Engineering Data 2D-3D) for further information
Scanned documents		Acrobat.pdf format to be viewed with Adobe Acrobat
Schedules		Primavera P6
3D Models		See (Engineering Data 2D-3D)

130

131 The necessity of handing over native files of documents submitted by the Contractor during 132 project processing before handing over the final documentation shall be agreed between the 133 Contractor and Uniper.

134 5.2.3 Document Metadata in Uniper DMS

135 When uploading/transmitting documents to the Uniper DMS, the Contractor must complete all 136 metadata fields as comprehensively as possible. At a minimum, the following must be provided:

137 • Uniper document number (document ID) 138 • Contractor Document ID (optional) 139 • Document title

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	9/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

140 • Revision 141 • Issue purpose

142 The file name consists only of the document number. Additional information about the document, 143 as described above, shall be provided in the designated metadata field(s).

144 5.2.4 Document Numbering

145 The Contractor shall use Uniper’s document numbering system for all delivered documents, using 146 the CDL to generate all the numbering.

147 The compiled document number must be clearly shown on each document. A Contractor’s 148 internal document ID may also be included in the Uniper DMS and on the document in the 149 respective field provided.

150 Document Numbering Structure:

AAAA-	AAA-	AA-		AAANNN-		NNNN	-ANN
HITW	UNI	PM		ABB010		0001	S01
Project identifier/Code

Creating company (to be aligned with Uniper)

Creating discipline

Document type (DCC area + DCC key) Sequence number (consecutively according to the assigned codes starting from (0001) for each combination of company, discipline, and DCC) Extended document identification (if required): Sheet number (for technical drawings) / explicitly assigned to a main document. 151

Project identifier	→ The project code
Creating company	→ E.g.: 3-digit code (three-letter abbreviation) → The UNI code is used for Uniper, irrespective of the various legal entities → The codes for external companies is to be agreed in the project between Uniper and the Contractor
Creating discipline	→ 2-digit code (two-letter abbreviation). To be chosen based on the content of the document
Document Type	→ 1-digit DCC Area Code + 5-digit DCC Key
Sequence number	→ 4-digit (0001-9999) consecutively according to the codes assigned
Sheet number	→ 3-digit (Letter “S”+ two digit consecutive number starting from 01 (e.g. S01) which is hyphenated at the end of the document ID → An optional suffix for family parts or parts on multi-sheet drawings in technical documentation. It also applies to multi-part documents that depend on a main document and must always be considered part of it → Consult the Uniper Document controller for applicable cases

Consult the Uniper Document controller for applicable cases 152 The detailed structure and codes for document numbering are mentioned in the CDL template.

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	10/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

153 5.2.5 Identification of Confidentiality

154 Documents that are intended exclusively for authorised persons must be marked in accordance 155 with the agreements with Uniper (e.g. Internally confidential - Uniper and partners, Strictly 156 confidential - Uniper and partners). These documents must be stored in such a way that only 157 authorised persons have access to them.

158 5.2.6 Document Revision Protocol

159 The revision number, reasons for the revision, and issue/release date, and the names and 160 signature of the authorized persons responsible for creation, review and approval must be 161 specified in the designated field for each document submitted by the Contractor to Uniper. 162 Document revisions are labelled with two-digit numbers, e.g. "00", "01", etc. The first creation of 163 a document is marked with attribute "00" in the "Revision" field. After each release or significant 164 change, this is increased by 1 and is consecutive.

165 The revision number should be entered in the Uniper DMS metadata field „Revision“.

166 5.3 Engineering Drawings (2D – 3D)

167 All 2D and 3D drawings must be submitted in digital form, in their native format as well as pdf.

168 Following Software tools are preferred:

169 • Revit, Inventor, AutoCAD, Plant 3D, NavisWorks, Recap, Civil 3D, ArcGIS, Faro Scene, 170 Faro As Built, E-Plan 171 • Other used products have to be aligned in the project to build the best solution for 172 interoperability between the Contractor’s system and the systems used by Uniper.

173 At a minimum, the following metadata have to be extractable from the engineering models or 174 drawings:

175 - Tag number 176 - Installation location 177 - Function 178 - Description short (short text) 179 - Description long (long text) 180 - Comment field 181 - Component (including all technical relevant information) 182 - Consumer (including all technical relevant information)

183 These properties have to be aligned with the responsible Uniper discipline leads and may have 184 to be extended.

185 For process design, Contractor shall propose type and version of software, with alternatives. 186 These shall be subject to review and agreement by Uniper.

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	11/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

187 5.4 Project Language

188 The project language is English. Project documentation shall be submitted in the project 189 language. In accordance with Uniper’s requirements, any document relevant to authorities (e.g. 190 permitting, firefighting, NoBo) and operations (e.g. operating instructions/manuals) might have to 191 be submitted in German language. This will be specified in the FEED Scope of Work.

192 Some information/documents provided by Uniper as basis for the FEED (e.g., documentation 193 from previous project phases) will be provided in German.

194 Translation of documents must be performed by a certified translation office if the original 195 document is not prepared in the final language. The Contractor is responsible for the translation 196 of these documents and its context.

197 5.5 Scanning of Documents

198 Scanned documents are always stored in PDF format (structured with content directory, at least 199 300dpi and machine-readable). Scanned documents must be aligned with the defined project 200 document numbering and to be uploaded in the Uniper DMS.

201 6 Final Documentation

202 The Contractor makes the final documentation available to Uniper in pdf and native format in 203 accordance with the structure within the Uniper DMS and according to the FEED contract.

204 The final documentation will be subject to formal, technical and structural checks by Uniper after 205 receipt. Resubmission can be required if deficiencies are identified.

206 The final documentation will only be accepted by Uniper once the documentation is free from 207 obvious errors. To prove the completeness of the final documentation and for fast and reliable 208 comparison with the list of required documents, a documentation overview, i.e. the final CDL, 209 must be enclosed.

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	12/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

210 7 Project Coversheet

211

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	13/14

	H2 Import Teminal Wilhelmshaven HITW
Uniper		Uniper

212 8 Drawings Header/Block title

213 9 Further Guidelines and Procedural Instructions

214 • VA-PM-UNI-006.03 "Document control in projects" 215 • VA-PM-UNI-006.02 "General documentation process for projects"

216 10 Annex

217 • Contractor Document List template (CDL)

218

Project Documentation Requirements
Uniper Dok.-ID / Doc.-ID:	Rev.:	Datum / Date:	Status:	Vertraulichkeit / Confidentiality:	Seite / Page:
HITW-UNI-DM-ACC050-0001	00	17.06.2026	Released	Public	14/14

HITW-UNI-DM-ACC050-0001.pdf