This document discusses a project called Train Mint created by Fretless Idea for Rail Traction Company and Lokomotion. The project aimed to create an agile solution for managing interoperability and maintenance information across the companies. It improved maintenance forecasting for engines, allowed sharing of maintenance plans with partner rail companies, and streamlined information sharing about engine usage and train timing. The project was completed successfully in a short time frame using agile methodology. It provided benefits like improved forecast accuracy, time savings, and extra value from new metrics.
Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...
The Train Mint project: an Agile solution for interoperability management
1. Fretless Idea
Transfering information on Maintenance for interoperability
The Train Mint project
an Agile solution
for interoperability management
13th UIC eBusiness Conference - Paris, 23 October 2009
2. Fretless Idea
Project's domain
● Small Railway undertaking (33 engines)
● Solution will scale on RU growth
3. Fretless Idea
Content
● Who?
● When?
● Why?
● What?
● How?
● Doing the math
4. Fretless Idea
Who?
● Rail Traction Company
● Lokomotion
● Fretless Idea
5. Fretless Idea
Who: Rail Traction Company
● One of the major italian private rail freight operators
● 33 engines of which 19 interoperable
● Combined and traditional transport, traffic through the
Brenner pass
● Customer Project Manager Ing. Edoardo Marone
6. Fretless Idea
Who: Lokomotion
● Partner RTC
● Est. in 2001
● First private rail company to use
Brenner pass deregulation
7. Fretless Idea
Who: Fretless Idea
● IT systems design and implementation since 1999
● Skilled IT partner for Rail Operators since 2004
● + projects on other industries
9. Fretless Idea
Why?
● Detected lack of optimization on mileage
maintenance
● Rough forecast for interoperable engines
● No data on engine outside RTC shift but predictable.
● Mileage forecast quality not considered satisfactory
● 45' per day spent on calculations (25 engines total)
● Possibility of calculation mistakes (excel sheets)
● Double check
10. Fretless Idea
What?
1. Having maintenance forecast for engine groups
2. Having partner RU engine usage information
3. Having maintenance information shared with partner RU
11. Fretless Idea
What?
1. Extra requirements on-the-fly:
● Automating communication to partner RU which
engine have been set on which train (MIIRC ps)
● Automating communication to partner RU near real-
time timing information on the trains (MIIRC ps)
● Uptime/downtime calculation from the same data
(cheaper to do at this point)
12. Fretless Idea
How: initial situation
● Rail Traction Company
● GeCO system
●
maintenance forecast on weekly basis
● Lokomotion
● exposing service production from corporate
website
13. Fretless Idea
How: the analysis
● Assessment of
● Data availability
● Data quality analysis
● Integration
● Process definition
● Architecture choice
● Security assessment
14. Fretless Idea
How: the method
● Pull approach
● Build of resource + locations matching tables
● Missing mileage supply (existing GeCO fn)
●
New locations/distances insertion proposal (easing
administrators for systems synchronization)
15. Fretless Idea
How: agile
● Most suitable for critical time-to-production projects
● Value-oriented development → Better quality, better
productivity, cost reduction
● Managing priorities dynamically → New requirements
are welcome
● Narrowing development windows. Scrum → Daily
meetings with the team
● Continuous integration, continuous releases,
automatic build & deployment → customer satisfaction
16. Fretless Idea
How: the result
● Project success in short time
● Full customer satisfaction:
● Better maintenance forecast
● Maintenance plan shared with partner RU
● Streamline of information sharing (interop+timing)
● Extra value from uptime/downtime KPI
17. Fretless Idea
Doing the math
● +15% on forecast precision → >90%
● 28 man-days saved each year (on 25 engines)
● Payback <1 year (counting only time saved)
● 1 month for delivery using Agile methodology.
(Releases once a week)
18. Fretless Idea
Any questions?
?
Enough time for quick demo of maintenance module?
19. Fretless Idea
Thank you for your attention
Paolo Righetti
Chief Executive Fretless Idea
Tel. +39 346 78 78 170
E-mail: paolo.righetti@fretlessidea.com