Created: | 16.03.2018 09:32:57 |
Modified: | 11.11.2022 09:43:50 |
![]() |
|
![]() |
Attribute | ||
Private string name |
||
![]()
|
Element | Source Role | Target Role |
DataContainer Class |
Name: hasExplanatoryNote |
Name: |
![]() Details how the data release was produced. This allows a user of a snapshot data set to assess the quality of the data. E.g. notes about conversion problems or gaps in the data.<br/>
|
||
DataPrepEntities Class |
Name: ownsAttachmentDocument |
Name: |
![]() |
||
ProjectStageGroupMetaData Class |
Name: hasRequirementSpecification |
Name: |
![]() Document describing the scheme requirements, operational objectives.<br/>e.g. "increase speed on Dresden - Leipzig to 200 kmh" <br/>This helps the supplier to design requirement validation tests.<br/>
|
||
ProjectStageMetaData Class |
Name: isBasedOnRegistryOfSpeeds |
Name: |
![]() The registry of design speeds used for the planning and signalling engineering. <br/>de-DE: VzG<br/>nl-NL: OS-blad, kan als string worden opgegeven. <br/>
|
||
StatusInformation Class |
Name: isDocumentedInAttachment |
Name: |
![]() The work executed to achieve the process step or the result of the work (e.g. note of approval in principle, quality approval note) is documented in an attachment.<br/>
|
||
ProjectStageMetaData Class |
Name: hasGeneralNote |
Name: |
![]() General notes about the planning step, e.g. scheme and project description "High-speed line Berlin to Madrid, construction of yard Kehl, the track had to be shortened lacking space, alternative solution was to insert an extra signal at position xy ....". The notes shouldn't be abused for storing information that redunds the data set.<br/>de-DE: Erläuterungsbericht<br/>
|
||
DiagnosticsOpcUaConfiguration Class |
Name: isGivenInXmlAttachment |
Name: |
![]() The OPC-UA information model is given as an XML attachment.<br/>
|
||
ProjectStageMetaData Class |
Name: hasDetailOnMaterial |
Name: |
![]() Details about materials relevant to the supplier such as desired reuse of materials, or availability of materials in storage.<br/>
|
Element | Source Role | Target Role |
TrainDescriberSystem Class |
Name: |
Name: includesOperatingRoomLayout |
![]() A schematic of the operating room layout showing the train describer system.<br/>de-DE: Verweis auf die ID des Raumplans Bedienraum, der als Anhang im Format PDF beigefügt wird.<br/>
|
||
Annotation Class |
Name: |
Name: refersToAttachment |
![]() Allows adding accompanying documents. This could for instance link to a exception procedure, french derogation.<br/>
|
||
AttachmentProperty Class |
Name: hasProperty |
Name: |
![]() |
||
LocalOperationDevice Class |
Name: |
Name: UiDesignAttachment |
![]() Reference to an attachment that describes the actual user interface of the local operation device in detail. Typically includes a drawing of the layout.<br/>
|
||
CommunicationRelation Class |
Name: |
Name: hasDescriptionForEndPointA |
![]() Description of the communication configuration at end point A.<br/>
|
||
CommunicationRelation Class |
Name: |
Name: hasDescriptionForEndPointB |
![]() Description of the communication configuration at end point B.<br/><br/>
|
||
MappingView Class |
Name: |
Name: refersToAttachedMap |
![]() Reference to an attached map that acts as a geographic underlay for the planning of the level crossing.<br/>
|
||
TrainDescriberSystem Class |
Name: |
Name: includesComputerRoomLayout |
![]() A schematic of the computer room layout showing the train describer system.<br/>de-DE: Verweis auf die ID des Raumplans Rechnerraum, der als Anhang im Format PDF beigefügt wird.<br/>
|
||
Configuration Class |
Name: |
Name: refersToBaselineDocument |
![]() In case the time stamp does not uniquely define the applied set of rules and regulations, an attachment/document describing the applicable implementation can be referred to.<br/>
|
Property | Value |
isFinalSpecialization: | 0 |