©railinc 2008 all rights reserved 1 railinc corporation – 7001 weston parkway, suite 200, cary,...

©Railinc 2008 All Rights Reserved1Railinc Corporation – 7001 Weston Parkway, Suite 200, Cary, NC 27513 – 919.651.5000 -- www.railinc.com

Update on Umler/EMISfor

ACACSO

Orlando, November 13th, 2008

Alan McDonaldDirector, Asset Services

[email protected]

©Railinc 2008 All Rights Reserved


July 25, 2009UMLER becomes Umler/EMIS

• Umler/EMIS is coming – full speed ahead

• Many changes WILL affect you– Your systems that use UMLER WILL have

to change

– Your processes that use UMLER WILL have to change

– History will be severed

• You need to know what those changes are

• You need to know what to do to prepare yourself, your department and your company

2

New data structure and names

New web system

Error-free strategy

Access to reports and query

New Messaging

Web services opportunities

…in short, EVERYTHING


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”

6


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





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





Equipment Type Code (ETC) is generated, not input

11




• ETC was previously input, which generated Mechanical Designation

• Now, ETC is derived from data input, including the Mechanical Designation

• Rigor during current development to identify

differences and work with owners to

rectify

….more on data quality later


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




R1 R3

WheelComponent Loc = L3

2

AxleComponent Loc = 1

Base

AD C

TruckComponent Loc = B

43

2

Axle SpacingComponent Loc = 1

No Elements

1 per pivot point

Truck Componentsw/ Truck System

1 per truck

1 per spacing

Journal Size A147Wheel Diameter A294Stability Device Equipped B199Truck Axle Count B252Loco Truck Configurations B003Loco Truck Type A278

Axle Spacing Distance B020

Page 1

future

43

2

TruckSystem Loc = 1

4

AxleComponent Loc = 3

TRUCKSYS

TRUCK AXLESPACE

EMIS Component Diagrams - Version 8

WheelComponent Loc = L1


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


not generated• New and Changed elements• Number of “critical” fields


©Railinc 2008 All Rights Reserved15

Preparing for Umler/EMIS and its effects on your back-end systems and processes means that you need to

understand the changes

Railinc

Brake Shoe Type

DeletesInternal

Conversion Process

Equipment Owner

Old Umler Message

Umler Format

Umler/EMIS Data Format


All of these changed elements can be found on Railinc’s Umler/EMIS TAG

SharePoint Site

https://community.railinc.com/committee/uetag

(Sign-up required)

Documents located under

Project Support\Phase 3\Element Database and Conversion

16

Umler-Umler/EMIS Mapping

17

ETC Mapping

18


Railinc is planning a comprehensive suite of communications and training for

affected users• TRAIN II users

– Engaged and at-the table with the Umler/EMIS TAG

• Web users– Largest population; most are already engaged

– Web-based training, town hall and documentation late Spring 2009

• “Umler Query87” is being retired, replaced with Umler/EMIS query on line and via XML web services

***Only Types 19, 21 and 22 are being retired!******Balance of Query87 output is NOT being retired!***

• Reports and extracts will be sourced from Umler/EMIS– Some may have to change

19


Umler/EMIS Implementation – July 25, 2009

20

High Level Timeline2008 2009

Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

Electronic Message Testing

Data Conversion to New Format

Industry Communications

Training Program

Web Users Go Live

Rollout to Electronic Message Users - Class 1s, GE, Others


The promise of Umler/EMIS….

21

• Greatly enhanced ease of accessibility and use

• Broad communications support

• Accurate, real time data

• Status: knowing what records are “real” and which are Memorex

• Increased velocity and cycle time for your cars

• Full lifecycle integrity

• Reduction in operational problems because of data issues

• Access to a massive historical data store for analysis and trending

©Railinc 2008 All Rights Reserved22Railinc Corporation – 7001 Weston Parkway, Suite 200, Cary, NC 27513 – 919.651.5000 -- www.railinc.com

www.railinc.com

24 Hour Customer Service800-544-7245

[email protected]
