Difference between revisions of "Master Data"

Latest revision as of 22:53, 25 May 2021

Goal

Status

Definitions

Definitions locations codes:

1. ENEE and UIC-Codes is the same. There is currently no common database for such codes
2. ENEE / UIC-Codes consists always of 5 digits (numerical)
3. DIUM is a certain commercial grouping of UIC-/ENEE-Codes

Subsidiary location type code

1. 03 (Border Point): 4n fixed, currently with leading “0”

• Maintained by UIC
• UIC and OSJD is the allocation company code

1. 36 (Production Station):

• Is always a station where RU activities happens (e.g. shunting, train composition)
• Only mentioned in the consignment note as a handover or takeover point
• Coding ENEE-/UIC-Code:

       Option a (tbd):
       * Up to 2 time 5 digits (always numerical) fixed
       * First 5 digits: Cluster station code (e.g. 
       * Next 5 digits: Production station in the cluster
       Option b:
       * Only 5 digits numerical fixed, with leading “0” if needed
       * Allocated by UIC

1. 37 (Loading Points/Siding):

• First 5 digits = ENEE-/UIC-Code: 5 digits numerical fixed, with leading “0” if needed
• Last 5 digits: free format 5 digits alphanumeric indicating place within ENEE/UIC-code (optional, spaces or blanks if none)
• End-to-End is always 37: Origin and/or destination of the wagon run (train run is 36!)
• Mentioned in the consignment note
• There must be a corresponding station in the same PLC with STC 36 and STC 42

1. 42 (DIUM)

• 5 digits numeric fixed, with leading “0” if needed
• Commercial station used in consignment note (origin/destination tariff points)
• Maintained by UIC

1. 66 (Lookup ENEE <-> PLC)

• 5 digit numeric, fixed, with leading “0” if needed
• Only Latvia
• Translations:

        From WSM -> WSM: Use directly the SLC
        FROM TRI -> WSM: Use lookup 

1. 57 (Terminals)

• Could be PLC or SLC depending of geography – How do we know if a SLC is a physical location or an attribute?
• UIRR responsible for assigning SLC to PLC, currently 3 digits for SLC

How to allocate a SLC in the CRD:

1. RU is in control for proposing the assignment of a certain SLC to a PLC

• STC 36/37/66: Address the IM
• STC 42: Address UIC
• STC 03: Address UIC. UIC needs to align with the involved IM(s)

1. UIC or IM is checking for double entries within the PLC and either accepting or rejecting
2. Allocation company to be set either to RU code (42) or IM’s company code (36/37/66)

Detected Gaps

• PLC attributes not filled
• national dialects in PLC definition

PLC attributes not filled

In many data sets the PLC attributes are not filled. This inhibits the usage of a attribute type. E.g. Type of location (Passenger, Freight, Infrastructure) One measure could be to make the necessary attributes mandatory. Consequence: The user has to load too many locations and to search externally for criteria to filter.

national dialects in PLC definition

The modelling of the network differs between IMs. There exists local situations where several PLC locations are defined for one business location. The different PLCs points either

• to sections/parts of a larger stations or
• they are used to store missing attributes (LOC_CUSTOMER1, LOC_CUSTOMER2, ...)

SLC are used for two purposes

The SLC is used both

• for detailing out a PLC (precision)
• for attributing information to the PLC

This is treated per network differently. This inhibits the usage of the master data.

Amount of PLC

The amount of PLC is too high for a specific usage but not complete. The SLC are not managed on a European basis which inhibits the usage as master data.

SLC defined several times

Some SLC's are defined several times triggered by different companies. E.g. Terminals Then we see the situation that the SLC is modelled differently (as PLC, related to PLC_A, related to PLC_B, ...)

PLC defined several times

PLC are defined several times to store attributes with it.

technical but no business governance

RNE ensures the technical assistance. But their is no body to manage and steer the business aspects of the CRD master data.

small players not involved

The master data is maintained by the bigger companies (IM and RU). The smaller RU and IM are not involved. This leads to gaps which inhibits the migration to CRD.

decentral government for PLC

The PLC are maintained per IM. Their is no assurance of the common governance which leads to national dialects in treaties and definitions.