RAIL-SYS Core Model Document

Section 1 - General
Reference: SE-TL-GDL-003
Version: 5
Application date: 02/02/2013

Purpose
This purpose of the RAIL-SYS Core Model document is to provide a description of the system solution
predominantly for service businesses and QSRW activities within Rolling Stock, and how their
requirements are satisfied by RAIL-SYS functionality.
The document is used during the requirements capture phase of the implementation when an impact
analysis is performed. The impact analysis compares the standard functionality with the needs of the
contract under consideration and the business processes already in place.
The document provides a summary of the RAIL-SYS solution. RAIL-SYS is part of the Alstom TWIST
systems architecture, which is shown below.

TWIST Architecture
TWIST: Together for a Worldwide Information System for Transport
Common ERP deployment

AMON
AMON RS Industrial
integrators sites
SAP R/3

Components RS
@PIS CHAS
Finance CHAS Traction
Core Model TIS sites

RAIL-SYS
RAIL-SYS TLS sites

RAIL-SYS Light
RAIL-SYS
RAIL-SYSLight
Light Small sites

The document describes the system solution and provides a reference to other supporting
documents.
RAIL-SYS is a modular system and the Core Model Document is structured to reflect this. The main
areas are Materials Management, Maintenance Management, Sales, Production and Finance. The
described functionality is unlikely to apply in its entirety to any one contract or business.

TRANSPORT
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Scope of application
The scope of the document covers the use of RAIL-SYS for TLS and TGS businesses and for QSRW
activities within Rolling Stock.

 Realisation Processes

 Support Processes
This document supports the process of analytical impact analysis and continuous improvement of the
Services system, Parts and Renovation business solution

Responsibilities for the execution of this instruction

The BIS Team is accountable for the maintenance and update of this document. The Business
Process Owners are accountable for evolution of the core model and the BIS Team is responsible for
delivering system evolutions. Local businesses execute the activities described in the document.

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 2/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Control Sheet

Issue Date Content of Modification Author(s)

1 Feb 2013 Creation as Section 1 of 8 new sections describing Jacqueline Lund
the RAIL-SYS Core Model Solution Dave Willetts
Caroline Fenton

Name Position Date Signature

Electronic
Written BIS <Updated
Dave Willetts signature
by: Project Manager automatically>
Prisma

ERP Alignment and Electronic

Verified <Updated
Jacqueline Lund Improvement signature
by: automatically>
Manager Prisma

Electronic
Approved <Updated
Annie Saillard SVP TLS signature
by: automatically>
Prisma

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

3/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Contents

1.0 Introduction ..................................................................................................... 6

1.1 Core Model document structure................................................................................. 6
1.2 Process Flow Charts .................................................................................................. 7
1.3 References................................................................................................................. 8
1.4 Cross References ....................................................................................................... 8
2.0 Data Warehouse Reporting ............................................................................... 9
2.1 Introduction............................................................................................................... 9
2.2 Business Intelligence tools ....................................................................................... 10
2.3 List of Data sets:...................................................................................................... 12
2.4 Master Data not from RAIL-SYS .............................................................................. 16
2.5 User Access and Security ......................................................................................... 16
3.0 Security ......................................................................................................... 18
3.1 Connection to RAIL-SYS Server ............................................................................... 18
3.3 Business Roles and RAIL-SYS Authorisations and Profiles........................................ 18
4.0 Time and Activity recording ............................................................................. 20
4.1 Labour bookings ...................................................................................................... 20
4.2 Depot Productive Time and Activity Recording ......................................................... 21
5.0 Transport applications – interfaces to RAIL-SYS ............................................... 22
5.1 Current Interfaces.................................................................................................... 22

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

4/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Table of Appendices

Appendix Section A Definitions and References ........................................................................ 23

A–1 Definitions ............................................................................................................... 23

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

5/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

1.0 Introduction

1.1 Core Model document structure

The total RAIL-SYS Core Model definition is split into the following eight independent sections for
maintainability. Each of these documents is version controlled, and stored on Prisma.

1. General section
2. Materials Management
3. Maintenance Management and Warranty
4. RAIL-SYS „Light‟
5. Production & Modernisation & Repairs
6. Quality Management
7. Sales
8. Finance

This document represents the General Section 1

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

6/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

1.2 Process Flow Charts

Process charts explain step by step how RAIL-SYS supports the business processes. These charts are held
at two levels:
a) End to End
Provide a high level overview of the functionality. Used for common processes, mainly Logistics and
Production (see illustration below).

b) Detailed Process
Detailed to SAP transactional level. One or more per process.

The process charts are held on MEGA: http://iww.transportmega.ch.power.alstom.com/railsys/en/

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

7/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

1.3 References
References are made through this document to the detailed User Instruction Documents (UIDs) which are
currently stored in the UK Prisma database under Alstom Transport UK section (Information Systems) and
also to On Demand lessons available via the intranet url
http://10.128.30.142/ondemand/content/OD_English

1.4 Cross References

Where reference is made within this section 3 to any of the other 7 Sections which make up the Core
Model Document, they are shown thus:
See Section 8, Finance, Labour Allocations.

Where reference is made to another section within this document, it is shown thus:
See section Error! Reference source not found. TMM Yard Management & Commercial Service

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

8/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

2.0 Data Warehouse Reporting

2.1 Introduction
Requirements
Many businesses using RAIL-SYS want to produce periodic as well as day-to-day operational reports, and
also to do data analysis. There are a number of reasons why it is not ideal to run use SAP directly for these:
Large amounts of data may be required which could cause a performance problem
Often graphical outputs are required
Standard facilities in SAP do not always make it easy to report against typical business scenarios
To overcome these issues, a RAIL-SYS Data Warehouse has been created which contains data extracted
from SAP and presented specifically for reporting on business scenarios. It also provides comparable
facilities to those contained in the FRACAS Data Warehouse, which were needed when warranty
implementation projects changed to using RAIL-SYS and RSL.
Solution
The Data Warehouse works by extracting data from RAIL-SYS tables, processing it according to appropriate
logic and then presenting it to the user as a dimensional model. To date the areas covered by Data
Warehouse are:
„Service Management‟ (most data sets are refreshed 5 times per week – 4 incremental + one full)
o Work done (service orders)
o Reliability (Service notifications plus linked order data – covers level 1 events and level 2
interventions)
o Service incidents (subset of events, only some contracts)
o Usage (distance run, powered hours etc)
o Labour hours (time confirmations against service orders, production orders, internal orders
and work packages, contains details of related service orders but not production orders)
o LCC (Life Cycle Cost) – comparison of actual and planned data for material and labour stars
“Material Management” (refreshed weekly)
o All material movements including receipts, transfers, issues plus expected receipts based on
open purchase order lines. Links to service management data for issues to service orders
(eg can show train part was issued to)
„Sourcing‟ (refreshed weekly every Friday evening European time plus additional end of month runs).
NB Only covers UK and Ireland
o Purchase orders
o Good receipts
o Stock information
o The general architecture of the solution is shown below:

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

9/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

The solution includes the following:

Extraction, Transformation and Load layer (ETL) - extracts data from RAIL-SYS via Datastage,
processes it via SQL and then loads it into special databases created for reporting (Data stars)
Presentation of the data via „Universes‟ and OLAP (On Line Analytical Processing) „Cubes‟
Reporting tools - layer of user access to the information

2.2 Business Intelligence tools

We currently use two Business Objects XI (BOXI) business intelligence tools – Web Intelligence and
Voyager OLAP reporting. Both of these are web based tools and do not require any client software; however,
users must be given specific access rights to create or modify reports.

Web Intelligence (WebI)

Good for regular reports with moderate formatting requirements
Based on data „universes‟
Can be scheduled to run automatically and send output to e-mail
Can include graphs and charts

Voyager
Business Objects OLAP tool for data mining
Good for ad hoc querying and exploring data trends
UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

10/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Can replace the need to export data to excel to analyse it

Based on data „cubes‟

In addition Crystal reports can be used to connect directly to the SQL databases. This requires client
software to be installed on the PC and is limited to a few key users and BIS/ITC only. Reports created can
then be deployed on the BOXI portal and run from there by any user with appropriate access rights. It is a
more advanced tool than the web based options but can deliver reports with more complex data and
formatting. It can also use data that is outside the data stars if a connection is available.

SAP Live Office is also available. This provides a way to use reports generated via Webi or Crystal within
office documents. The data can be automatically refreshed. This is a useful tool for creating monthly
contractual reports where a commentary is needed to go alongside tables and graphs of figures and some
content does not come from DWH.

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013

11/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

2.3 List of Data sets:

‘Service Management’ data stars

Data Set name Grain and main data Summary New deployments’ data Example Reporting
sources included?
Event T1 and I1 notifications Contains event records with reliability Yes if service management is Reliability and defect analysis by train,
Assessment Linked to technical and other codes, details of technical implemented using T1 or I1 symptom, root cause (Alstom LBS,
(EA) objects, catalogue objects (with product family and project) notifications and data is set up project specific, customer code)
(reliability) codes, and long texts. Includes labour hours in standard way Aims to replicate some FRACAS
service orders (aggregate figure only) from linked reporting
Also data from selected service order. Includes cumulative Labour hours analysis by defect coding
old data model figures for usage (e.g. km) at time of
implementations eg event.
UKML, Bucharest (not Shows Alstom „common capture grid‟
all data exists for these) values as well as project specific codes

Intervention T2 and I2 notifications Contains intervention records with a link Yes if service management is Analysis of interventions/component
Repair (IR) Linked back to some to the technical object details (product implemented using T2 or I2 repairs by LBS, material number, serial
data from originating T1 family and project) of the original event. notifications and data is set up number
(event) notification and Shows details about repairs (external in standard way Aims to replicate some FRACAS
service order and internal) including repair time reporting

EAIR Snowflake One record per T2 Selected data from the EA and IR stars As for EA and IR Analysis of interventions/ component
notification joined together via service order. repairs by original event data e.g.
Only contains interventions (T2 and I2 symptom codes
notifications) linked to an event (T1 or
I1record)
Work Done Service orders of all Contains details of all orders created Yes if service management is Analysis of work done by fleet, vehicle.
types, open or closed and work performed including planned implemented. Depending on Analysis of resources consumed
but excluding rejected and actual hours, costs (by category), exact data set up some fields (labour and material) against plan (for
orders materials planned and used. Also has may not be populated standard jobs) by fleet, vehicle.
task list. Analysis of maintenance costs by fleet,
UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or reproduce this document or any part thereof without prior written
authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 12/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Data Set name Grain and main data Summary New deployments’ data Example Reporting
sources included?
vehicle.

Reliability Service Notifications of Contains notification details for No, data from franchise model Analysis of fleet, train set or vehicle
certain types only, corrective work and defects, including projects is added to EA and IR corrective maintenance history.
currently covers: codes and short and long texts. Also stars. Analysis of particular types of defects
corrective work on the shows Alstom „common capture grid‟ Specific work may be done to (trend analysis, root cause analysis).
following contracts: values as well as project specific codes bring other pre franchise
West Coast (Class 390 model projects into the star.
and other fleets) The following are scheduled
Merval in Chile Some fields are only populated for for late 2008:
Dublin Citadis trams certain projects. Bucharest Metro
Chester Coradia Other Chile projects
Barcelona trams (by import)
Usage Measurement All counter based measurement Yes, if counter based Fleet, Train Set usage (kilometres,
documents documents (e.g. kilometres run, KWH, measurement documents mileage) reporting.
Linked to technical powered hours) created. For full data, Links to reliability information to
object data „standard‟ range of produce MKPF data.
characteristics should be used
Service Incident Y1 Service Notifications Contains contract specific information No, specific to WCML Class Service incident reporting for Class
of certain types only. for WCML service incident records 390 fleet 390 fleet
Only applies to WCML
Labour bookings Time confirmations All labour hours booked to service Yes
orders, production orders, internal
orders and cost centres/work packages,
whether made via CATS or simple
confirmations
May have multiple records for a single
order operation
Labour Time confirmations Hours against operations as recorded in Yes Can be used for planned vs actual
operations aggregated to order either CATS or AFRU hours comparison
operation level
UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or reproduce this document or any part thereof without prior written
authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 13/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Data Set name Grain and main data Summary New deployments’ data Example Reporting
sources included?
LCC data Imported from Comparison of actual and planned data Comparison of actual cost against LCC
spreadsheet for material and labour stars prediction

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or reproduce this document or any part thereof without prior written
authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 14/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

‘Material Management’ data sets

Data Set Grain and main data Summary New deployments’ data Example Reporting
name sources included?
Materials Goods movements line Goods movement details including Yes ?
Management items (MSEG table), plus related service order data (train number,
for expected deliveries type of work etc.), purchase order data
against POs, schedule (vendor, type of PO?). Does not show
line items special stock indicator. Also links to
stock levels snapshot.

‘Sourcing’ data sets

Data Set Grain and main data Summary New deployments’ data Example Reporting
name sources included?
Purchase Purchase order line items All purchase order details. No Analysis of Supplier Spend
Orders Covers UK and Ireland only Analysis of Supplier portfolio (active
suppliers) for a particular part.
Analysis of Commodity spends.
Analysis of Supplier delivery
performance (OTIF).
Goods receipts Goods movements of All goods receipts and returns. No Stores workload analysis.
specific types Covers UK and Ireland only Analysis of Supplier Quality
Performance (% returned parts by
reason codes).
Stock Stock data at plant and All stock information by storage No Current Stock value reporting.
storage location level locations Covers UK and Ireland only

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or reproduce this document or any part thereof without prior written
authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 15/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

2.4 Master Data not from RAIL-SYS

Some master data is taken from outside the system and loaded at appropriate frequencies into the
database.

Master data Data Set Function Central (TLS)

/ Local
Ownership
Euro Rates Purchase Orders Used to convert all the purchase order Central
values into Euros using the current
reporting month‟s Euro exchange rate.
Low Cost Purchase Orders Used to flag the countries, which are to be Central
Countries identified as „low labour cost‟ countries in
supplier reporting.
Contractual Reliability, Work This allows maintenance contracts to define Local
Reporting Period Done, Usage, EA their own reporting periods (maybe to align
with customer requirements) and supply
dates as a spreadsheet. Must be separately
developed for each contract
In addition there are some „hard coded‟ relationships within the processing such as the grouping of
the UK company codes into „business‟ descriptions (e.g. Metro, Parts, Mainline etc)

2.5 User Access and Security

User logons
All users have their own Business Objects logon, which will determine:
Which actions they can take (e.g. create new reports/edit existing reports or view only)
Which report folders they can access
Which Universes and OLAP cubes of data they can access (e.g. Reliability records, Work
Done/Service Orders, Purchase Orders)

Folder security
This is used to restrict which existing reports users can run or view
Users cannot edit reports in public folders – they must take a copy to their own personal folder, work
on it there and then request it to be deployed in the public folders
Note – Folder security overlaps with Data security
If a user has access to a folder they can view any existing „instance‟ of a report irrespective of
any data permissions in force
A user can only refresh or run a report in a folder if they also have the necessary permissions
on the data
Currently folders are organised broadly along business lines (e.g. folders for TLS USA, TLS Romania,
UK Mainline) plus generic folders such as REX reports. This will be developed to meet emerging
needs. We will establish folder „owners‟ who will be responsible for ensuring that only appropriate
data is published in their folder and can control the deployment of new reports.

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 16/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Record security
At present there is no row level security within any Data Warehouse objects – this means that for
example if a user can work with data from the Work Done star then they can see data in that star for
all projects and contracts within RAIL-SYS. This is different from the user accounts on RAIL-SYS itself
where generally a user can only update and view data from their own company.
However the „Labour Bookings‟ and „Labour Operations‟ data stars incorporate row level security.
This is controlled via an SQL account that works in the background to restrict a user‟s access by plant
or company code. Please note that authorisation must be obtained from the site financial controller to
access the individual company data.

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 17/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

3.0 Security

3.1 Connection to RAIL-SYS Server

RAIL-SYS can be accessed via the Alstom WAN Backbone.

3.2 User Access Rights Management

User access rights are managed for all TWIST systems in line with Alstom Transport requirements.
SoD (Segregation of Duties) compliance is measured with SAP GRC-RAR.

3.23.3 Business Roles and RAIL-SYS Authorisations and Profiles

Access to different parts of the system is controlled by the application of Composite and Single Roles
to a users profile according to their job role within the business.
Single Roles contain one or more transactions. Composite Roles are built up from one or more
Single Roles. Multiple Composite Roles can be added to a users profile.
Generally only Composite Roles are added to user profiles, the only exception to this is Segregation
of Duties (SoD) „Risky‟ Single Roles. All finance roles have been built to be compliant with SoD rules
defined by Internal Control. All other transactions, which have been identified as SoD „Risky‟, have
been contained within a number of Single Roles. To provide better control these Single Roles are
never added to Composite Roles and are applied directly to user profiles only on the receipt of
suitable authorisation.
An example of business roles and the associated Composite and Single Roles are shown below:

In addition to the business oriented Composite and Single Roles all users will have the following
generic Composite Role s assigned to their user profiles,: ZZZ_R6_GE_BC_END_USERS-CCCC.

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 18/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Reference Document(s):
S/00/IS/PRO/006/F003 RAIL-SYS User Account Request Form

S/00/IS/PRO/006/F004 Support User Account Request Form

S/00/IS/PRO/009 Procedure for User Access Rights Review

The following documents can be found on the RAIL-SYS MEGA web pages:

http://iww.transportmega.ch.power.alstom.com/RAILSYS/en/:

S/00/IS/PRO/011 Procedure for User Account Request

GIS_WMS_001_V1.1_Provision_SAP_UAR_20120412 User Access Rights in

SAP Instruction

User request form IS&T V0.1.xls SAP User Request Form IS&T

User request form EN V1.3.xls SAP User Request Form

RAILSYS data catalog 20120926.xls RAIL-SYS Data Catalogue

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 19/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

4.0 Time and Activity recording

4.1 Labour bookings

Requirements
There are several reasons why time booking to jobs is required:

To enable comparisons of planned and actual time

To record who/which team actually worked on a job
To record where the work was done
To add the correct labour costs to a job
To associate those costs with the correct cost centre via the work centre
To enable billing of chargeable work on a cost plus basis
To indicate progress through a longer job such as an overhaul
For productive activities not otherwise covered by a specific service order, it is possible to generate
„blanket‟ orders for an activity for a period of time (for example an order for shunting trains for a
month).
There may also be an overall requirement to account for direct staff time. As well as time spent on
jobs, this may avoidable non-productive time such as waiting for a train to work on and unavoidable
non-productive time such as undergoing training, sickness or leave. Time booking for non-productive
time is covered in Section 8 Finance, Labour Allocations.
Some of the above could apply to contract staff as well as employees.
Solution
Time spent on service orders can be captured using either CATS (Cross Application Timesheets) or
simple Confirmations.
Compared to CATS, simple confirmations offer the following advantages:
Less master data set up
More suited to booking labour on a job by job basis
No validation of total time for a day – so one employee number can be used for a group of
contractors
Either single or multiple entry screens can be used (transactions IW41 and IW44)
However a major disadvantage is that there are no checks against availability of the employee and no
facility to associate an employee with their cost centre or default activity type.
Using either method, an operation can be „finally confirmed‟ to indicate that it is complete. This allows
the tracking of long jobs such as train overhaul. It is unlikely that this would be used for short duration
service orders.
Activity Types are used in labour bookings. These combined with the cost centre determine the hourly
rate to be applied to calculate the labour costs. It is possible to set the hourly rate to effectively zero
so that no costs are in fact processed. This option can be chosen where it is necessary to record a
quantity of hours worked but it is not appropriate to have an associated cost (e.g. CW projects,
contractor time). More details on this are in Section 8, Finance, Labour Allocations.
It is also possible to create labour booking records in SAP using an interface e.g. ALISTA, TAMS.
This area will be developed in future and more detail will be available in a future version of this
document.

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 20/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

4.2 Depot Productive Time and Activity Recording

Requirements
In many maintenance contracts Alstom is responsible for certain types of general depot activities that
do not require an ERP system record related to a specific train/tram/loco/vehicle/asset. Typical
examples are shunting, train preparation and minor servicing activities such as filling sand boxes.
Even if the work is performed on an individual train basis, because of the frequency (daily) and
volume of work, a paper certificate may be considered an adequate and appropriate record.
For this type of work it is however important to record the labour hours expended, and possibly further
details such as personnel number. The costs associated with this labour need to be assigned to the
correct work package/WBS.
Solution
Service orders can be raised for this type of work, against a generic technical object for the fleet or
contract. Labour hours can then be booked against the orders in the usual way and the orders can be
assigned to the correct WBS using a combination of order type, maintenance activity type and task list
(see Section 8, Finance, Project Accounting).
As the orders do not relate to any specific object, they can remain open as long as required – a day,
week, month, and year – and decided by the local business. If the orders are going to have a fairly
short validity then it is recommended to set up a maintenance plan to generate the orders
automatically (see Section 3 Maintenance Management and Warranty, Maintenance Scheduling).
Note that generally this solution is only used for productive depot activities. For other work see
Section 8 Finance, Labour Allocations.

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 21/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

5.0 Transport applications – interfaces to RAIL-SYS

5.1 Current Interfaces

System Description Local vs Type Tech. On Sender Frequency

Core Side
Interface
ADEL TLS File of people transfer to RAILSYS core Flat File FTP Daily
AEINET Internal invoices interfaced to Apis local Flat File Manual On Demand
activities
ALISTA Time and Attendance core BAPI RFC On Demand
AMTRAK AMTRAK catalog , GDI, GDR, Inventory interface local Flat File FTP Every 15 mn

AMTRAK MSR MSR interface (Material Service Request) local BAPI RFC On Demand
AMTRAK WMS AMTRAK input warranty claim interface local Flat File FTP Daily
APIS DIP Digital Invoice Processing core BAPI RFC On Demand
Capacity Planning Finite Scheduling for WCTC (UK) local
CLAMP Materials definition core Batch Input File On Demand
DESKOM SNCF Invoice Dematerialization local Flat File FTP Hourly
DESKOM Invoice Verification local Flat File FTP Hourly
Digital Pen & Paper Corrective Maintenance local BAPI RFC On Demand
DMAGS to RAIL-SYS Engineering parts and BOMs definition, local Flat File FTP On Demand
developed and piloted at Ridderkerk
E-Pass Overhead Purchasing (replaces Marrakech) core Web Service IDoc Hourly
FRACAS Failure mode and effects analysis core
GEDI PO and invoices with external systems via GEDI core Flat File FTP
mainframe
GENIUS Train running and configuration. Defect status local Flat File FTP Every 10 mn
from RAIL-SYS to Virgin systems
Interflex Time & Activity recording. Interface developed for local
Salzgitter R6, CHAS and AMON
IVU RAIL Sweden contract - FTP transfer local Web Service SOAP On Demand
JDE Hornell Procurement & Logistic EDI local Flat File FTP On Demand
KOMPIS Sweden contract. 2 flows local Web Service SOAP On Demand
Marrakech Overhead Purchasing (UK&I). Superceded by E- local ALE
Pass
MAXIMO IBM Maintenance System used in Sweden local Web Service SOAP On Demand
Natixis Recovery rates of currency interface core Flat File FTP Monthly / Daily
NTV Notifications and train mileage, used in Italy local Web Service SOAP On Demand
OPTIMUS Inventory forecasting for USA local Flat File FTP Daily
Parts Folio Manage Service Operations core
Planisware Fleet Planning, service order and measurement local Flat File FTP Daily / OnDemand
docs
QM DWH Quality Management Notifications to DWH (TBD) core

RAILSYS DWH Contract, Engineering and Products LCC analysis core

RAILSYS Lignt Maintenance and Logistics flows core BAPI RFC On Demand
Sourcing DWH UK Sourcing Data Warehouse core Flat File FTP
SQCD Supplier QCD data local Flat File
Teranga Consolidated Finance reporting core
THETYS Apis Treasury Management core File SFTP On Demand
TRAIN TRACER Asset Management - Train core BAPI RFC On Demand
Event/Status/Position
ULYSSE Input of professional expenses from ULYSSE core Flat File FTP Every 15 mn
WAS Sourcing & Procurement core BAPI RFC On Demand
ZAP Transport Payroll Payroll core Flat File FTP Daily
UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 22/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

Appendix Section A Definitions and References

A–1 Definitions
For the purpose of this, and the seven other sections of the Core Model document, the following
definitions shall apply:
 AP Accounts payable (SAP module)
 APIS or @PIS Alstom Transports‟ core model for Finance (SAP solution)
 AR Accounts receivable (SAP module)
 BOM Bill Of Materials
 BIS Business Information Systems function
 CLAMP Common Language And Management of Parts
 CPA Contract price adjustment
 CS Customer Service (SAP module)
 GAAP General Accepted Accounting Practice
 GL General Ledger (SAP module)
 GRIR Goods receipt / invoice receipt
 IFRS International Financial reporting Standard
 IM Inventory Management (SAP module)
 ITSSC Information Technology Shared Service Centre
 LBS Logical Breakdown Structure
 MAP Moving average price
 MRP Material Requirements Planning
 MM Materials Management (SAP Module)
 P&L Profit & Loss
 PIR Purchase Information Record
 PO Purchase Order
 Product Hierarchy Field set in material master, which determines whether the part is
technically repairable, economically repairable or consumable.
 PS Project Systems (SAP module)
 Purchasing Group Code denoting the buyer responsible
 SAP 3rd party software ERP package
 RAIL-SYS SAP solution for Alstom Transport TLS
 ROQ Repair On Quote
 SD Sales & Distribution (SAP module)
 Service Exchange Process where a float of repairable parts are held so that a part can be issued at a
fixed /average repair cost, in exchange for a broken part
 SM Service Management (SAP module), Customer Service in SAP version 4.7.

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 23/24
 RAIL-SYS Core Model Document
Ref: SE-TL-GDL-003 Version: 5 Date: Feb 2013

 TGS Transport Global Solutions

 TLS Train Life Services (business within Alstom Transport)
 TOV Total order value
 WBS Work Breakdown Structure
 WM Warehouse Management (SAP module)

UNCONTROLLED WHEN PRINTED – Not to be used before verification of applicable version number
This document is the property of Alstom Transport and the recipient hereof is not authorised to divulge, distribute or
reproduce this document or any part thereof without prior written authorisation from Alstom Transport
Filename: SE-TL-GDL-003 Feb 2013 24/24