Project_management::ProjectStageMetaData

Project Stage Meta Data : Public Class

Created:	15.06.2021 14:17:01
Modified:	04.11.2021 10:57:30

Project:
Author:	Bob Janssen
Version:	1.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{D165B435-44EE-4cb0-9264-C37DC660B40A}
Appears In:	Overview of the Project Management model, Project stage meta-data, Stages and stage groups, Data release, Planning correction

Meta-data informing a single project stage. de-DE: Planung Einzel

Attributes
Associations To
Associations From
Advanced
Other Links

Attribute

Private string
basedOnPreviousStage

Details:

Alias:	Based on previous stage
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Reference to the previous planning stage, if available, on which the current data release is based. Textual reference such as "Planning stage 02.03, removal point W12". Can be used as alternative or complement to a UUID reference.

Private string
constructionPhase

Details:

Alias:	Name of the construction phase
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

The name of a phase within the (re-)signalling project that summarises the goal that the individual stages in this phase aim to achieve.

Private boolean
forInformation

Details:

Alias:	Only for information
Initial:
Stereotype:
Ordered:
Range:
Transient:	False
Derived:	False
IsID:	False

Notes:

True: this release is for information only, e.g. for the purpose of resource allocation before the stage starts. False: this release is part of the formal design process.

Private string
levelOfDetail

Details:

Alias:	Level of detail
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Indicates the level of detail of the project stage. Suggestions, should be tailored to national rules: <ul>
<li>feasibility (rarely in data)</li><li>pre-design</li><li>draft design - preferred variant</li><li>detailed design - for quotation/to be ordered, supplier neutral</li><li>detailed design - supplier specific</li></ul>
de-DE: Planungsphase

Private string
planningType

Details:

Alias:	Type of planning
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Indicates the use case for which the data were produced. This can distinguish stages that are internal to the data production process (corrections) from the release to external data consumers. Suggested planning types: <ul>
<li>first digitisation</li><li>revision due to data base correction</li><li>revision due to survey data</li><li>"project target type" would indicate that the release aims to reflect the goal of the project.</li></ul>
<ul>
<li>as-constructed (as-built)</li></ul>
de-DE: Planungsart (zB. Bauzustand)

Private string
registryOfSpeeds

Details:

Alias:	Registry of speeds
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Version and/or name of the registry of speeds that governed the engineering. Alternatively, this information can be provided in an attachment. nl-NL: naam en versie van OS-blad

Private string
releaseNumber

Details:

Alias:	Release number
Initial:
Stereotype:
Ordered:
Range:
Transient:	False
Derived:	False
IsID:	False

Notes:

Identifies a release, i.e. an incremental modification, for a planning stage. String format allows for the release number to have a leading zero digit.

Private string
sequenceIndex

Details:

Alias:	Index of the sequence
Initial:
Stereotype:
Ordered:
Range:
Transient:	False
Derived:	False
IsID:	False

Notes:

Number or letter for sequencing the stages. On schematic drawings, this version may inform status information, e.g. 2 for a development release, A for an approved version. SNCF: the sequence indicator can differ per discipline.

Private string
stageDesignationLong

Details:

Alias:	Full designation name of the stage
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

The designation of the planning stage. Typically describes the goal of this individual stage.

Private string
stageDesignationShort

Details:

Alias:	Short designation name of the stage
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

The designation of the planning stage, shortened to fit in a title block.

Element	Source Role	Target Role
BaseObject Class	Name:	Name: hasObjectsInPlanningArea
Details: The objects in the planning area that may be modified in the course of the project stage.<br/>
DataRelease Class	Name:	Name: refersToDataRelease
Details: Reference to an individual released engineering data set of the given discipline.<br/>de-DE: ID-Ausgabe-Fachdaten<br/><br/>
ProjectStageMetaData Class	Name:	Name: referenceToPreviousStep
Details: Reference to the previous planning step on which the current data release is based. The referenced project stage might not be part of the current file.<br/>Can be used as alternative or complement to a textual reference attribute.<br/><br/>
ProjectStageGroupMetaData Class	Name: splitsIntoStageMetaData	Name:
Details: The property group splits into meta-data for this single stage.<br/>

Element	Source Role	Target Role
PlanningCorrection Class	Name:	Name: hasCorrectedProjectStage
Details: Reference to the revised stage.<br/>
DateTimeDescription Class	Name: hasDateOfRuleSet	Name:
Details: The date stamp of the baseline of the rule set that governs the planning activities.<br/>
Attachment Class	Name: hasDetailOnMaterial	Name:
Details: Details about materials relevant to the supplier such as desired reuse of materials, or availability of materials in storage.<br/>
DateTimeDescription Class	Name: hasDateOfCompletion	Name:
Details: The planned date of completion for this planning phase. <br/>This date of final information is not to be confused with date of taking into service. The data are incorporated into the data management systems within a given delay <i>after</i> the taking into service.<br/>
ProjectStageMetaData Class	Name:	Name: referenceToPreviousStep
Details: Reference to the previous planning step on which the current data release is based. The referenced project stage might not be part of the current file.<br/>Can be used as alternative or complement to a textual reference attribute.<br/><br/>
Attachment Class	Name: hasGeneralNote	Name:
Details: 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/>
PlanningCorrection Class	Name:	Name: isBasedOnProjectStage
Details: Stores the GUID of the project stage instance that needs correction; the referenced project stage might not be included with the current EULYNX DP file.<br/>
StatusInformation Class	Name: hasStatusInformation	Name:
Details: Documents the status in the workflow.<br/>
Attachment Class	Name: isBasedOnRegistryOfSpeeds	Name:
Details: 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/>

Property	Value
isFinalSpecialization:	0

Object	Type	Connection	Direction	Notes
PM-0904 - ID Engineering data release	Requirement	Realization	To
PM-0910 - Construction step long designation	Requirement	Realization	To
PM-0907 - Single planning step general attributes	Requirement	Realization	To
BaseObject	Class	Generalization	To
PM-0912 - Baseline of ruleset	Requirement	Realization	To
PM-0905 - Signaling objects planning area	Requirement	Realization	To
PM-0802 - Single planning step meta data	Requirement	Realization	To
PM-0911 - Date of completion single planning	Requirement	Realization	To
PM-0903 - Attachment register of permitted speeds	Requirement	Realization	To
PM-0901 - Attachment explanatory report	Requirement	Realization	To
PM-0914 - Informative	Requirement	Realization	To
DateTimeDescription	Class	Strong	From	The date stamp of the baseline of the rule set that governs the planning activities.
Attachment	Class	Strong	From	Details about materials relevant to the supplier such as desired reuse of materials, or availability of materials in storage.
DateTimeDescription	Class	Strong	From	The planned date of completion for this planning phase. This date of final information is not to be confused with date of taking into service. The data are incorporated into the data management systems within a given delay after the taking into service.
PM-0917 - Planning phase	Requirement	Realization	To
PM-0913 - Index	Requirement	Realization	To
PM-0915 - Sequential number	Requirement	Realization	To
Attachment	Class	Strong	From	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. de-DE: Erläuterungsbericht
ProjectStageGroupMetaData	Class	Strong	To	The property group splits into meta-data for this single stage.
PM-0902 - Attachment special materialisation	Requirement	Realization	To
PM-0908 - Construction phase	Requirement	Realization	To
StatusInformation	Class	Strong	From	Documents the status in the workflow.
Attachment	Class	Strong	From	The registry of design speeds used for the planning and signalling engineering. de-DE: VzG nl-NL: OS-blad, kan als string worden opgegeven.
PM-0906 - ID Signaling object planning area	Requirement	Realization	To
PM-0919 - Reference special comparison	Requirement	Realization	To
PM-0932 - Reference planning basis	Requirement	Realization	To
PM-09 - Single planning step meta data	Requirement	Realization	To
PM-0916 - Single planning step type	Requirement	Realization	To
PM-0909 - Construction step short designation	Requirement	Realization	To