This is an excerpt from PDP template (Project-specific document management procedure) For a complete overview of requirements for documents, please refer to the project's PDP.

The supplier is obliged to have a project archive for technical documentation for all official audits with an electronic signature. The supplier shall use a suitable electronic system that at least takes care of numbering, audit handling, status codes, deadlines, as well as traceability of files and shipments.

The archive must be available and in accordance with requirements for safety and durability with a minimum duration beyond the warranty period or in relation to a possible maintenance agreement.

The production format for all deliveries must be handed over to Bane NOR on request and is also mandatory for ‘as built’ publications (D revisions), or generally for final delivery of a delivery / partial delivery to Bane NOR.

In connection with small changes, alterations, rehabilitations and modifications, Bane NOR reserves the right to change models or drawings afterwards without prior approval from the supplier.

The production format for drawings / models the original format from the CAD program the files are produced in, incl. Xref / support files, e.g. AutoCAD (.dwg), Revit (.rvt), Tekla (.db1), Bentley (.dgn), Novapoint (.dwg). BIM / 3D models are delivered in .dwg format, alternatively IFC, LandXML or other format by appointment.

Bane NOR reserves the right to make revisions of the supplier's original archive..

Document plans are used for several purposes in the project. All participants in the project must plan their document production in accordance with current requirements, regulations and schedules. The document plan will also be used in connection with the import of metadata to Bane NOR's systems, so that manual registration is limited. Furthermore, the document plan must form the basis for status reporting from eSAM.

The supplier shall prepare a complete document plan for all technical documentation included in the delivery. The document plan must be prepared and handled as a separate technical document with a document number and technical front page. The plan must be sent officially to Bane NOR for comment and acceptance, both in PDF and XLSX format.

In connection with the construction plan and preparation of FDV and Manufacturing documentation for end customers, the document plan will also be used for import to the operating archives for reserving FDV no. (Operating number) from Bane NOR's operating organization.

FDV no. Is applied to the document plan by Bane NOR when the plan is of satisfactory quality and in good time before the FDV documentation is prepared. FDV no. and revision number must be applied in the title block / title field for all technical documents and drawings before the documentation is transferred to operation. It is the individual supplier's responsibility that this is done.

During the process, the project will be able to change the layout of the document plan's content and structure if necessary

All documentation must be readable, this means that original files must be converted directly from originals to pdf so that it is possible to use the table of contents to browse the documentation. Technical documents shall be prepared based on Bane NOR's template for technical documents (ref. Bane NOR's Technical Regulations), see project-specific templates Appendix 2 - template for document cover. For FDV documentation, the documents must contain bookmarks for easy navigation.

The documentation must be self-explanatory and have the necessary references / references to associated documents and drawings. All technical documentation must have a unique document number, revision code, FDV number and revision number in the title block / title field.

A4 format must be used for technical text documents, see appendix 1. A3 format can be used for tables / sketches, and the like that are included in technical text documents. All pages in technical documents must have a header with the document title, document number, date, revision number and page number (page x of y). All signature fields on the front page must be filled in with initials. 2D. Signed by the person who prepared the drawing / revision. 2E. Signed by the person who checked the drawing / revision. 2F. Signed by the person who has approved the drawing / revision. Field 2E (checked by) and field 2F (approved by) can not be signed by the same person.

AutoCAD files with x-ref files must be checked and packaged (zipped) before handing over to the FDV archive.

Completion of title fields for technical drawings shall be prepared based on Bane NOR's template, see Appendix 3 - Template Title block for Technical Drawing. Project members can order / download a standard plug-in template (PTG - Project Template Generator) to AutoCAD to complete the title field from this link: http://esam.bim2share.no/Pages/UserDocs

The title field should be legible and should always be placed in the bottom right corner. Unless otherwise specifically agreed, technical drawings shall not consist of several pages. All signature fields on the front page must be filled in with a user ID and the supplier must send a signature list to the contract area, which must be updated at all times. The person conferencing and approving the documentation must not be the same person. Deviations from the above design requirements are only permitted after approval by Bane NOR's project manager. The approval must be documented.

Administrative documents: <Project name> - “document type, name”

Example: ERTMS Experience section East Line - Organization map

Generic Documentation (GP / GA): Generic Product - “Product Type”, “Product Name” - “Document Type” Generic Application - “Product Type”, “Product Name” - “Document Type”

Example: Generic Product - EBITRACK2000, Shaft Counter System Installation Description Generic Application - CBSS_BV_L2 - ETCS Level 2 - System Description AIRTECH - TYPE XYZZA Cooling System - Maintenance Manual

Specific application (SA): Track Track, «subject» - «Product type», «Product name» - «document type»

Example: Østfold line east line, (Ski) - (Sarpsborg), ETCS / IL- LOP_01 Local Operator Space - Functional description

Site-specific documentation: Course Course section, “Location”, subject ”-“ document type ”

Example: Østfold line east line, (Ski) - (Sarpsborg), Plots Station, ETCS / IL - Plan and cable plan

The file name must be the same for all versions of the document during the project's lifetime (without the use of date, rev, or other terms)

All technical documents and drawings produced under the auspices of the project (suppliers, subcontractors or internally) shall bear a unique document number in accordance with this procedure. The document management manager or equivalent role administers and assigns serial number series to the project and its contracting parties.

The document number consists of: project code, parcel code (area division), subject code and a 5-digit serial number separated by a hyphen. In addition, all documentation must have an audit number to satisfy follow-up of the document's history. The revision number is not part of the document number.

All documents and drawings must have the following format in the code structure:

Table 1: Document numbering structure

Examples: URH-00-A-00001, see chapter 6.3.4-7 for an overview of which codes (project code, parcel code, document type and serial number) apply to this project.

This code consists of 3 letters that tell which project in Bane NOR the document belongs to. The code must be included as part of the numbering structure for technical documentation.

Table 2: Project code (The table will be expanded as needed) <Project code is defined by the document management manager in collaboration with the project manager>

This code consists of 2 characters (numeric). The code identifies the project's area division. If the document has no reference to parcel, 00 (zero, zero) must be used.

Table 3: Parcel (The table will be expanded as needed)

<parcel codes are defined by the document management manager in collaboration with the project manager>

Specification of subject codes in the project is governed by requirements in the Technical Regulations. Subject codes are used to distinguish between the documentation for the various subjects in the project. There is one professional code for engineering and another for documentation for administrative purposes. The subject code for engineering shall be used to group the technical documentation into topics and consist of one character. See the table below.

Subject codes are used to distinguish between the documentation of the various subjects involved in the project. There is one professional code for engineering and another for documentation for administrative purposes. Subject code engineering shall be used to group the technical documentation to which topic they deal, and consists of one character.

The following subject codes for engineering are used:

Table 4: Document type

The serial number consists of five digits. This number is the unique identifier that identifies the document within each project, parcel and document type. There can thus be several documents with the same serial number, as long as the combination of project, parcel and document type is different.

Table 5: Serial number (The table will be expanded as needed)

<Serial number series are defined by the document management manager or equivalent role in collaboration with the project manager>

Avtales med dokumentansvarlig

For større 3D-modeller skal det etableres et eget tekstdokument som revisjosstyres på vanlig måte. I dokumentet skal alle modellfiler listes. Den faktiske forsendelsen skal utheves/markeres slik at de blir enkle å identifisere.

Figur 3: Modellstruktur

Leveransehyppighet og detaljrikdom kan variere fra prosjekt til prosjekt.

Revisjonsnummeret for et dokument eller en tegning er et sekvensielt nummer som øker med 1 for hver gang en ny revisjon av dokumentet/tegningen blir utgitt offisielt. For offisielle utgivelser (revisjoner) vil revisjonskoden bestå også av en statuskode som forteller formålet med utgivelsen. Det benyttes to (2) sifre for å sikre en korrekt (alfanumerisk) sortering i lister og rapporter. Merk at revisjonsnummeret ikke er en del av dokumentnummeret. Det er et krav at telleren i revisjonsnummeret øker for hver utgivelse. Det betyr at det ikke skal forekomme flere varianter av samme nummer (00C, 00D, 00U etc.) av et dokument eller en tegning. Det skal ikke forekomme hull i revisjonsserien for et dokument eller en tegning. Alle offisielle utgivelser skal håndteres som revisjoner og omfattes dermed av reglene i denne prosedyren. Revisjonsnummeret skal alltid starte på 00 (første utgivelse), deretter skal telleren fortløpende øke for hver utgivelse. En offisiell revisjon skal alltid kombineres med utgivelsesstatus (se tabell nedenfor).

Tabell 6: Utgivelsesstatus

Figuren nedenfor viser hvordan bokstavene typisk benyttes i ulike prosjektfaser. Antallet revisjoner per fase kan variere.

Figur 4: Eks Revisjonskoding

Ved sluttføring av prosjektet dokumenteres og arkiveres alle som bygget-tegninger etter STY-605016, og prosjektets PSD. Dokumentasjonen får da påført et nytt dokumentasjonsnummer med fagkode for dokumentasjon og et nytt tegningsnummer i tittelfeltet.