Project_management::ProjectStageGroupMetaData

Project Stage Group Meta Data : Public Class

Created:	21.06.2021 10:29:55
Modified:	10.11.2021 10:20:01

Project:
Author:	Bob Janssen
Version:	1.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{12E01E32-0949-4856-878C-158D4F05EA0C}
Appears In:	Overview of the Project Management model, Project meta-data, Stages and stage groups

Meta-data informing a group of project stages. Stages are grouped to reflect common qualities such as: <ul>
<li>allocation to consulting engineering firm (e.g. stages x-y by ACME railway engineering GmbH).</li></ul>
<ul>
<li>area</li><li>discipline (aka subject matter), e.g. geo, interlocking, ETCS</li></ul>

Attributes
Associations To
Associations From
Advanced
Other Links

Attribute

Private string
dataCategory

Details:

Alias:	Data Category
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Marks the stage in the data-flow life cycle. E.g. <ul>
<li>first digitisation of as-is quality checked data (first assembly of digital inventory).</li><li>Insertion of topological nodes to divide-and-rule</li><li>Version bumping</li></ul>
Similar to planningType attribute in project stage meta data. SNCF: not stored in plans because done in the data factory. DB: Planung_G_Art_Besonders

Private string
discipline

Details:

Alias:	subject matter
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Discipline, subject matter, e.g. interlocking, geo-information, ETCS, etc. This supports the compartmentalising and sequencing signalling design, typically 1. GEO layout 2. IL engineering 3. signal positioning and sighting 4. ETCS engineering A responsible designer can sign for the compartment of the engineering work under his responsibility, Mr. S. Signaller signed off for his discipline, IL engineering, only.

Private string
modifiedSubSystem

Details:

Alias:	Modified Sub-System
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Designates the subsystem that is subject to planned changes, e.g. decentral interlocking.

Private string
modifiedSystem

Details:

Alias:	Modified System
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Designates the facility or system that is subject to planned changes, e.g. "signalling system" or "interlocking central unit".

Private string
projectSectionDescription

Details:

Alias:	Description of Project Section
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Description of the geographic zone under planning. Typically indicates that the present group of project stages applies to a section of a larger project E.g "section Dresden Hbf - Dresden Neustadt" (which is part of the larger project Dresden - Leipzig) DE: Bauabschnitt

Private string
referenceLineKilometre

Details:

Alias:	Reference chainage
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Reference chainage (aka kilometrage/mileage), where this group of project stages is centered, or e.g. the largest station in the planning area. E.g. km 125,35 +5,25 (m) en-UK: Engineer's line reference (ELR) de-DE: Strecke-KM auf fuehrender Strecke Note that the planning area location provides the precise machine-readable information.

Private string
referenceLineSection

Details:

Alias:	Reference to Line Section
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Informs the limits on the reference line of the planning area, e.g. "Km 12.7 to Km 13.5". Exact machine-readable information is found in the planning area.

Private string
requestedSchemaVersion

Details:

Alias:	Requested XSD version
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Version of the EULYNX DP schema (XSD version) that the data engineer was requested to use for the present data set. Note that a validation tool looks for xsi:schemaLocation in the header of the XML instance for the XSD to validate against. This XSD can differ from the present attribute because data engineers may need to apply a different version in the course of their work.

Private string
stageGroupDesignation

Details:

Alias:	Designation of the Stage Group
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

Designation of the group of planning stages, expressing the intent of the grouping, e.g. "stages resignalling design by ACME signalisation ferroviaire S.A."

Element	Source Role	Target Role
Organisation Class	Name:	Name: isCreatedByOrganisation
Details: The design organisation, engineering company, that created the plans for this group of plans.<br/>fr-FR: bureau d'études (champ obligatoire)<br/>de-DE: Ingenieurbüro<br/>
Line Class	Name:	Name: refersToProjectReferenceLine
Details: This group of project stages is centered on this line.<br/>de-DE: fuehrende Strecke<br/>en-UK: Engineer's Line Reference.<br/>Definition of the leading line supports orienting and plotting layout plans according to rules such as "the project plan shall be drawn such that the leading line plots with kilometrage counting up from left to right" or "London to the left", or "Paris à gauche, kilomètre 0".<br/>
Organisation Class	Name:	Name: isOwnedByOrganisation
Details: The sub-organisation of the IM or regional organisation of the IM that is responsible for, and owns the plans and data.<br/><br/>This allows addressing the correct organisation.<br/><br/>SNCF: signifie la région en <i>possession des plans </i>(champ obligatoire)<br/><br/>
ProjectMetaData Class	Name: splitsIntoGroupMetaData splits into group meta-data	Name:
Details: The project meta-data splits into one or more groups of meta-data. <br/>
OperationalLocality Class	Name:	Name: hasReferenceOperationalLocality
Details: Reference to the locality to which the meta-data apply. This links the project to company-wide planning and documentation. E.g. Projet Grand Paris<i>.</i><br/>

Element	Source Role	Target Role
AreaLocation Class	Name: coversPlanningArea	Name:
Details: Area where the actual engineering is carried out. Changes to objects are allowed and to be expected within this area.<br/>de-DE: Planungsbereich<br/>
AreaLocation Class	Name: coversObservationArea	Name:
Details: This group of planning stages covers the given observation area. The objects in this area cannot be changed.<br/>de-DE: Betrachtungsbereich<br/>
ProjectStageMetaData Class	Name: splitsIntoStageMetaData	Name:
Details: The property group splits into meta-data for this single stage.<br/>
DateTimeDescription Class	Name: hasDateOfCompletion	Name:
Details: The planned date of completion of this group of project stages.<br/>Supports project managers to forecast, timely ordering, and resource planning.<br/>
Attachment Class	Name: hasRequirementSpecification	Name:
Details: 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/>

Property	Value
isFinalSpecialization:	0

Object	Type	Connection	Direction	Notes
PM-0809 - Department responsible for inventory plans	Requirement	Realization	To
PM-0801 - Leading operational locality	Requirement	Realization	To
PM-0806 - XSD version	Requirement	Realization	To
PM-0814 - Planning group title block	Requirement	Realization	To
PM-0817 - Designation planning group	Requirement	Realization	To
PM-0807 - Planning group special type	Requirement	Realization	To
PM-0820 - Polygons observation area	Requirement	Realization	To
PM-0805 - Date of completion planning group	Requirement	Realization	To
PM-0803 - Planning group general attributes	Requirement	Realization	To
PM-0823 - Polygons planning area	Requirement	Realization	To
PM-0811 - Line section	Requirement	Realization	To
AreaLocation	Class	Strong	From	Area where the actual engineering is carried out. Changes to objects are allowed and to be expected within this area. de-DE: Planungsbereich
PM-0812 - Line kilometer	Requirement	Realization	To
ProjectMetaData	Class	Strong	To	The project meta-data splits into one or more groups of meta-data.
PM-0701 - Planning group meta data	Requirement	Realization	To
PM-0802 - Single planning step meta data	Requirement	Realization	To
PM-0804 - Attachment operational task	Requirement	Realization	To
PM-0818 - Designation sub-facility (controller)	Requirement	Realization	To
PM-0810 - Planning group leading line	Requirement	Realization	To
AreaLocation	Class	Strong	From	This group of planning stages covers the given observation area. The objects in this area cannot be changed. de-DE: Betrachtungsbereich
BaseObject	Class	Generalization	To
ProjectStageMetaData	Class	Strong	From	The property group splits into meta-data for this single stage.
PM-08 - Planning group meta data	Requirement	Realization	To
PM-0819 - Planning office	Requirement	Realization	To
DateTimeDescription	Class	Strong	From	The planned date of completion of this group of project stages. Supports project managers to forecast, timely ordering, and resource planning.
PM-0815 - Section of construction	Requirement	Realization	To
Attachment	Class	Strong	From	Document describing the scheme requirements, operational objectives. e.g. "increase speed on Dresden - Leipzig to 200 kmh" This helps the supplier to design requirement validation tests.
PM-0808 - Discipline	Requirement	Realization	To
PM-0816 - Designation facility (central unit)	Requirement	Realization	To
PM-0813 - Line number	Requirement	Realization	To