1 / 41

Umler Equipment Management Information System EMIS Project

kalona
Download Presentation

Umler Equipment Management Information System EMIS Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Umler Equipment Management Information System (EMIS) Project Project Update for ACASCO San Diego, CA November 16, 2007 Alan McDonald

    2. 2 Agenda Deliverable to-date Phase 3 Features Phase 3 Major Changes Getting Data In, accurately Status Management Conflict Management Getting Data out, efficiently Other features Timeline Action items Important take-aways

    3. 3

    4. 4 EMIS project driving principles Get the data that carriers need to operate their railways Make it real-time Make it simple for car owners to participate and use Make the system secure Increase data integrity and quality Make it flexible Make it last for the NEXT 40 years

    5. 5 What’s in Phase 1 Infrastructure Real time processing New Web site http://emis.railinc.com Customer registration Security grants and permissions Car Management functions Pools and pool assignments Car grades Transportation codes/ EMIS Equipment Management Codes EMIS TRAIN II Messaging Web services Phase 1 Audience: Class 1 Railway Car Management

    6. 6 What’s in Phase II? All Inspection reporting via EMIS ABT FRA Locomotive Inspections Door Lubrication Vehicular rack and flat certifications Retro-reflectorization reporting Future transactions Correction and nullification Advanced Query Data Refresh Company Specific Groups Implemented March 19, 2006 Audience: The entire Railway industry

    7. 7 What did this mean to you? ABT = Umler™/EMIS Web App SCABT is being retired EW ABT Alerts can only be closed via Umler® EMIS Legacy Umler Passkeys cannot be used for EMIS Legacy Umler coexists with Umler™/EMIS UMLER 03/04, UMLER 74/75 and UMLER 76/77 messages were retired

    8. 8 What’s next… Umler/EMIS Phase 3….. …the big deal

    9. 9 Umler/EMIS Phase 3 Features Equipment Characteristics Adds/deletes/modifications Restenciling Component management Status management Historical lineage On-line access to history Advanced query Scheduled query and reports

    10. 10 Phase 3 Major Changes Umler/EMIS “groups” replace UMLER formats Elements with multiple meanings are split Elements with coded values decoded Multiple occurrence “components” introduced ETC generated Dynamic data model Legacy Umler is retired

    11. 11 EMIS Equipment Groups Replacing Umler “Formats” with physical type Format “A” split into multiple groups Boxes Hoppers Gondolas Flat cars split Regular Intermodal Vehicular Special function to allow movement between equipment groups

    12. Umler to EMIS Conversion 54% of elements changing Splits, decodes, components, eliminations Mapping completed and distributed Spec Manual/Umler DB/EMIS map Conversion logic 95% completed Reverse conversion 40% done Internal System Modification well underway at Railinc. View towards back-end validation changes only No specific view towards data input changes for external systems Carriers have started to study

    13. 13 Components and Elements Hierarchy of groups, components and elements modeled in EMIS tables to create an easily extensible, high performance data model Child platforms (articulation) handled as components

    14. 14 ETC Generation Equipment Type Code (ETC) will be generated based on input Mechanical Designation M.D. is currently generated based on ETC Facility for ETC “check” provided Helper application to bridge paradigm shift Allow user to specify what ETC they are trying to get Show what fields are in error to provided ETC Notification when data updates will change ETC

    15. 15 Data Model Changes Transition from “spreadsheet” view of equipment data, with all attributes stored in a single row of a table to a normalized view with a number of interdependent tables

    16. 16 Equipment Add Blank screen based on equipment group All eligible elements shown Similar elements grouped and sorted Mandatory elements identified Default number of components shown Ability to add or remove Fill what is needed, ignore the rest

    17. 17 Equipment Multiple Adds From single entry, create multiple units Specify numbers, enter data once “Variable” data not duplicated forward Weights, for example New records entered in “Pre-registered” status

    18. 18 Equipment Clone Quick method of entry Use an existing record to create a new one Can use current or historical records “Unique” data not carried forward Ownership Prior equipment Weights Inspections Can clone to one or many new units Multiple must be in pre-registered status

    19. 19 Single Unit Editing Three columns – current value, blank field, errors All elements possible for unit shown, whether data exists or not Means to remove data from existing element Ability to add or remove occurrences of components Full unit edited prior to submit

    20. 20 Spreadsheet View Editing Like “select field” update Specify equipment population Pick-list of elements Identify like elements Build spreadsheet of equipment and elements Show current value and blank field to update “Copy down” functionality Full unit edited prior to submit

    21. 21

    22. 22 Handling Errors ERRORS NOT ALLOWED ON FILE All transactions are validated prior to submit Errors presented to user User may Cancel transaction Fix errors Suspend work Submit with errors On Submit, valid data posted Error data routed to “Notice Management”

    23. 23 Restencilling Linking current record to prior record “Simple” restencil Provide old/new equipment numbers, ownership Use “clone” function Allow editing during process Multiple restencil must be to pre-registered status Restencil “event” Similar to ABT Reports that restencil has occurred, updates status

    24. 24 Restencilling Restrictions Enforcing current/prior relationship Prior unit ID must exist in EIN History Matching Equipment “category” Built date Changing key data will sever relationship

    25. 25 Restencilling Permissions No specific authority necessary to use foreign prior unit Foreign company needs to know "BUILT DATE” to match EIN history to link Granting may be used, encouraged Disposition of old unit can be specified Owner of prior unit notified (tickler) when relationship established

    26. 26 EIN History Equipment history tracked through restencilling transactions via a unique equipment identification number (EIN)

    27. 27 Status Management Goal of one physical unit active at any time With restencil, enforces rule “new” unit is activated “prior” unit goes inactive Foreign owners notified of changes

    28. 28 Conflict Management Identifies illogical data based on external events Two equipment records pointing to one physical unit Units in active status with estimated data Flagged to owner Tickled to owner Statistical reports Zero-rate in 30 days Restrict in interchange in 90 days Delete in 365 days

    29. 29 Umler/EMIS Query Services Umler® online ?Umler/EMIS web Single Unit Equipment Query Define your output format and elements Save as template Web service (XML) query available to mimic web Advanced Query Access to historical data Historical lineage Transaction log history Trending

    30. 30 Messaging Changes Support legacy UMLER messaging as contingency Retire legacy UMLER messaging capabilities December 31, 2009 UMLER Master files and change tapes handled through Advanced Query Messaging must support components Identify location on vehicle Identify component

    31. 31 TRAIN II Input/Output EMISC00 Inbound EMISC00 TRAIN II message to remove equipment from a company specific equipment group: Message Header #ABCDbbbb0001EMISC000410311212RRDCbbbb/ Control Group Header*CH12345620041031121200USERIDbb Data Group Header *DH0001GER Detail Record +GRIDbABCDGROUPID1 0001 bABCD0000123456 Data Group Summary =DS0001SUM0001 Control Group Summary=CS1234560001 Trailer $0001EOM! Where ! = hex ‘9C’ EMISC60 Outbound EMISC60 TRAIN II message to remove equipment from a company specific equipment group: Message Header #RRDCbbbb0001EMISC600410311212ABCDbbbb/ Control Group Header*CH65432120041031121200USERIDbbABCD12345620041031121200 Data Group Header *DH0001GER Detail Record +GRIDbABCDGROUPID1 0001 bABCD0000123456 Data Group Summary =DS0001SUM0001 Control Group Summary=CS6543210001 Trailer $0001EOM! Where ! = hex ‘9C’

    32. 32 XML input/output <?xml version="1.0" encoding="UTF-8"?> <EquipmentChange xmlns:model="http://model.ws.railinc.com" xmlns:global="http://global.ws.railinc.com" xmlns:equipment="http://equipment.model.emis.services.ws.railinc.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../EquipmentChange.xsd"> <submitter> <model:company>ABCD</model:company> <model:userID>emisUSER</model:userID> <model:traceID>C123456</model:traceID> <model:userLocale>EN-US</model:userLocale> <model:environment>production</model:environment> <model:submitType>submit</model:submitType> </submitter> <equipmentUnit> <equipment:equipmentId> <equipment:equipmentIdValue>ABCD0000123456</equipment:equipmentIdValue> </equipment:equipmentId> <equipment:poolId> <equipment:poolIdValue>1230001</equipment:poolIdValue> </equipment:poolId> </equipmentUnit> </EquipmentChange>

    33. 33 CSV format (input/output) Report Air Brake Test Inspection “TRAN”,”ABT”,”0001”,”ABCD0000123456”,”REPT”,”EFGH”,”PERF”,”XYZ”, ”SPLC”,”411657”,”DTDN”,”20040214”

    34. 34 Advanced query output

    35. 35 Reports and Statistics Count of error and conflicts shown online Transactional errors are company specific and private Conflicts are public Monthly report of fleet size, status, conflicts Advanced query use for general query use Create custom reports Schedule

    36. 36 TRAIN II Query 87 19-22 Replacement Query 87 types 19-20 (Weights) eliminated Umler/EMIS Single Unit query Query 87 type 21 (Rates) remains as-is Query 87 types 22 replaced Umler/EMIS TRAIN II C60 XML Web Services Scheduled extracts Scheduled reports

    37. 37 Summary: Getting Data Out TRAIN II format over MQ (Frame Relay) EMIS C60/C61 TRAIN II format over FTP XML format via web services over TCP-IP Replaces Query87 XML format via FTP Query output from Advanced Query CSV (Spreadsheet) to FTP Email Replaces monthly files, change tapes Web output using CSV

    38. 38 Other Functions Historical Lineage Temporal Snapshot Drop Dead calculation Becomes public 2 years prior Equipment compare function Match pre-registered unit to active unit to update data

    39. 39 Timeline 2008 System Development Test Case Development Interim “plumbing” releases Comprehensive functional testing January 2009 Comprehensive data testing Parallel run July 2009 System Go Live Contingency December 2009 Legacy Umler Messaging shut-down

    40. 40 What do you need to do? Subscribe to EMIS Sharepoint https://sp.railinc.com/committee/uetag/default.aspx keep up on news Download elements list and conversion rules Stay tuned for formats and screen layouts If you subscribe to data from Railinc Establish/review internal use of data Map changing elements Strategize changes Decide on message protocols and formats TRAIN II Web Services FTP Establish connectivity with Railinc Review procedures for data entry and error handling

    41. 41 Important Take-Aways Umler/EMIS Phase 3 replaces UMLER mid 2009 Messaging Changes: Umler/EMIS TRAIN II, XML & CSV replace UMLER messaging Umler/EMIS website replaces TSUM (UMLER Online™) Web-service query replaces Query 87 UMLER data query Advanced query output replace reports, extracts and change tapes Data changes Data elements are being split and decoded Components are being introduced Equipment Type Code (ETC) generated, not input Mechanical Designation input, not generated Access Umler/EMIS security uses grants replace Passcode sharing Enhanced user-self-service for equipment maintenance, restencil and queries Advanced query access to historical data

    42. Questions and Answers Railinc 24 hour Customer Service 800-2447245 CSC@Railinc.com 42

More Related