This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
A reminder: Umler Redesign: Why are we doing this?
• Umler data can be hours behind reality, impacting velocity by impeding free-flow of traffic at interchange.
• Umler’s mission critical data can be incomplete, impairing railroads’ ability to:
− Comply with regulations and handling restrictions.
− Determine the best routing/proper train assignment.
− Optimize car utilization, pooling and reverse routing.
− Collect Car Hire
• Umler is out of step with industry’s car ownership model:– Umler was built for Class 1 users (most data from private owners).– Private car owners cannot interact easily with the system resulting in late
data and inaccurate data.
3
4
Legacy Umler Laptop Version
UMLER
250323775775
Data entry is made easier and data quality improves with dropdown lists, value descriptions, and error descriptions.
Navigation is made easier with dropdown menus, links to presentation groups, and color coded indicators for mandatory elements and those used in rating. Indicator shapes support those with disabilities.
Key Features of Umler/EMIS that will affect Car Accounting functions
• Enforced lineage• Introduction of equipment status• Duplicate EIN Handing• Conflict aging• ETC is generated, not input• Mechanical Designation is input, not generated• New and changed elements• Number of “critical” fields increased• “Error” data not allowed on file• “I don’t know” no longer permitted• Replacement of “Query87”
Enforced lineage means that the complete lifecycle of a unit is known
• Lineage continues to be tied to report of a “prior car ID” when registering, creating an EIN (Equipment Identification Number)
• Inputting of the “prior car ID” is edited– Prior car must be valid
– Prior car must be sequential
• System prompts user for correct car ID if
the wrong sequence is input
• Pre-registered cars are not considered in
sequence; lineage tied to Active cars only
7
• Enforced lineage• Introduction of equipment status• Duplicate EIN Handling• Conflict aging• ETC is generated, not input• Mechanical Designation is input,
not generated• New and changed elements• Number of “critical” fields
increased• “Error” data not allowed on file• “I don’t know” no longer permitted• Replacement of “Query87”
Equipment Status allows you to know the “real” size of the fleet
• Status is tied directly to Railinc’s event repository
• As new and restencilled (pre-registered) cars start moving, their status is recorded and updated
• Last movement date is known
• If “new” car is linked to an old car via prior ID and EIN
the prior unit goes “inactive”
• Inactive units remain on file until manually
removed
8
• Enforced lineage• Introduction of equipment status• Duplicate EIN Handling• Conflict aging• ETC is generated, not input• Mechanical Designation is input, not
generated• New and changed elements• Number of “critical” fields increased• “Error” data not allowed on file• “I don’t know” no longer permitted• Replacement of “Query87”
Duplicate EIN occurs when two or more units are active, pointing to the same EIN
• Situation occurs for several reasons– Wrong prior ID was input
– AEI tag errors
– Clerical error in reporting movement
• Illogical situation that must be corrected
9
• Enforced lineage• Introduction of equipment status• Duplicate EIN Handling• Conflict aging• ETC is generated, not input• Mechanical Designation is input,
not generated• New and changed elements• Number of “critical” fields
increased• “Error” data not allowed on file• “I don’t know” no longer permitted• Replacement of “Query87”
To keep the file clean, “conflicts” have consequences
• Conflicts occur when any illogical data exists on file– Duplicate EIN
– Pre-registered unit passes effective date
– Business rules change
• Conflict aging “consequences”– 30 days – Unit zero rated
– 90 days – Unit restricted in interchange
– 365 days – Unit subject to deletion from file
• Multiple email “ticklers” before each step
• Notification of conflicts on line
• Notification in electronic messages
10
• Enforced lineage• Introduction of equipment status• Duplicate EIN Handling• Conflict aging• ETC is generated, not input• Mechanical Designation is input,
not generated• New and changed elements• Number of “critical” fields
increased• “Error” data not allowed on file• “I don’t know” no longer permitted• Replacement of “Query87”
• Enforced lineage• Introduction of equipment status• Duplicate EIN Handling• Conflict aging• ETC is generated, not input• Mechanical Designation is input,
not generated• New and changed elements• Number of “critical” fields
increased• “Error” data not allowed on file• “I don’t know” no longer permitted• Replacement of “Query87”
• ETC was previously input, which generated Mechanical Designation
• Now, ETC is derived from data input, including the Mechanical Designation
Several changes are occurring to elements in Umler/EMIS
• Split of Umler fields
• Decode of Umler fields
• Scaling and standardization of Umler fields
• “Net New” elements
• Retired and deleted elements
• Multiple occurrences of elements now
managed (components)
12
Brake Shoe Type
• Enforced lineage• Introduction of equipment status• Duplicate EIN Handling• Conflict aging• ETC is generated, not input• Mechanical Designation is input,
not generated• New and changed elements• Number of “critical” fields
increased• “Error” data not allowed on file• “I don’t know” no longer permitted• Replacement of “Query87”
Several editing improvements are introduced that increase quality of data, but will also
enforces more rigor during input• Editing at element level for
– Format
– Scale and size
– Valid values
• If element is mandatory, fillers not allowed
• “Unknown”, “Zero” is not allowed
• Editing at relationship level more rigorous– Failure at a relationship level fails all related
element changes
• “Appearance” of more critical elements
14
• Enforced lineage• Introduction of equipment status• Duplicate EIN Handling• Conflict aging• ETC is generated, not input• Mechanical Designation is input,
not generated• New and Changed elements• Number of “critical” fields
increased• “Error” data not allowed on file• “I don’t know” no longer permitted• Replacement of “Query87”