co-funded through eu fp6 dg tren 1 kickoff/meeting, brussels, 16 november 2006 welcome to...
Post on 12-Jan-2016
213 Views
Preview:
TRANSCRIPT
1 Kickoff/Meeting, Brussels, 16 November 2006
Welcome to FREIGHTWISE kick-off
2 Kickoff/Meeting, Brussels, 16 November 2006
Project Management Committee 15.11.06Proposed agenda
1. Discussion of the kick of meeting (agenda presentations etc)
2. Start of the revision and detailing of the time plans for the WPs and the cases (deliverable 1)
3. Identifying urgent areas for cooperation between WP and between Cases
4. Changes in the contracts due to mistakes / new staff /changed distribution between partner.
5. An outline for a project meeting calendar 6. Using a project management support tool for file
transfer and information exchange 7. Aob
3 Kickoff/Meeting, Brussels, 16 November 2006
Kick-off 16.11.06 - Proposed agenda
09:00 Welcome (Lars Källström BMT Transport Solutions) 09:30 FREIGHTWISE and co-modality strategy of the
European Commission (John Berry, CEC DGTREN Unit G3)
10:00 An overview of the main goals, the approach and the structure of FREIGHTWISE (Lars Källström).
10:30 Presentation of the Business Cases and the participating organisations (Business Case Leaders)
12:30 Buffet lunch13:30 Presentation of the horizontal Work Packages and the
participating organisations (WP leaders) 15:00 Contractual and Management issues16:00 Next steps and any other business 17:00 End of meeting
4 Kickoff/Meeting, Brussels, 16 November 2006
FREIGHTWISE starting points
• Timely and correct information is a vital part of any logistic solution
• Internal IT management systems are developing rapidly
• Advanced Information exchange between organisations is still complicated
• “Standardised” solutions are missing
– Technology is not the major issue
– Organisational and commercial issues is more of a problem
• Advancing inter-organisational communication requires some basic “rules of the game” - interaction infrastructure – to support the physical infrastructure.
• Providers of such interaction infrastructure are/could be:
– Standardisation bodies
– European and national initiatives
• FREIGHTWISE supports Commission initiatives in cooperation with the industry
5 Kickoff/Meeting, Brussels, 16 November 2006
FREIGHTWISE supports supply chain management
• SCM is the integration of key business processes from end user through original suppliers, that provides products, services and information that add value for the customer and other stakeholders (Global Supply Chain Forum)
SCM consists of the following elements: • The stakeholder structure - The member firms and their relationships• The business processes - the value adding activities • The management components
– physical and technical – managerial and behavioural
6 Kickoff/Meeting, Brussels, 16 November 2006
A need for transport chain management
7 Kickoff/Meeting, Brussels, 16 November 2006
FREIGHTWISE Framework seeks to integrate three domains
8 Kickoff/Meeting, Brussels, 16 November 2006
Examples of EU policy initiatives
• Safe Sea Net and mandatory ship reporting system (FRS) according to Directive 2002/59/EG
• Telematic Applications for Railfreight as part of Directive 2001/16/EC on the interoperability of the trans-European rail system.
• A proposal for Harmonised River Traffic Information Services in Directive COM 2005/44/EC
• An ongoing initiative to develop a harmonised system for electronic fee collection for road use till 2009
• MARNIS for one stop shop vessel reporting
• FREIGHTWISE to provide input for a Directive (?) on intermodal transport information exchange
9 Kickoff/Meeting, Brussels, 16 November 2006
RIS as an example of a European initiative
• Proposal for a Directive (COM 2005/44/EC) on harmonised River Traffic Information Services (RIS) on inland waterways in the Community
• RIS defines:– Guidelines for architecture and organisation
– Electronic ship reporting
– Notices to skippers
– Tracking & Tracing systems – Inland ECDIS (Electronic Chart
Display and Information Systems)
10 Kickoff/Meeting, Brussels, 16 November 2006
NOTE: This is NOT a System Design. Driver with a Web Enabled Cell Phone
WAGON LOAD
Business Model Wagon Load
Transit Time to Customer
Planning Mode Execution Mode Post Trip Mode
CONSIGNOR CONSIGNEE
Commitment
IM3
Train Order
RU1
RU2 Yard
Operator
IM1
RU4
RU3
Customer
Lead RU Service
Integrator
IM2
ETI
I
TETA
Train Order TET
A
Train Order
ETH
ETI
I TETA
H
ETA
H
ETI
I
ETH
42-45
17
17
17
17-19
20-29
18
Train ready
34 30
01-03
01-03
RUs report to LRU(s)
IM reports train ETA / ETH to next IM and RU
IM sends new train ETA to RU 17. RU sends wagon ETI(s) to LRU(s)
30.and IM sends new train ETH to next IM. 17
no
Customer requests service
(LRU) receives
consignment note inc release time
RUs check resource availability incl; train
paths
collects ETI and
ETA from each RU and creates Trip
plan
Is trip plan acceptable?
receive confirmed wagon
order inc release time, ETI and ETA
and next RU
Wagon departure
prepares train composition data
checks &
updates relevant wagon data
in yard
train control handover
IM to IM+1
monitor train
set route -
command and control (start path)
LRU(s), RU(s) and
IM(s) make real time enquiries
IM and RU manage
Train delay
End of Path
reached
creates preliminary wagon order based on release time, ETI
and ETA for each RU
RU reports to LRU
Train path request
Infrastructure, Rolling stock register
Load, Dangerous goods Rolling stock
register
Infrastructure register, Rolling stock register
Load, Dangerous goods
add train details to paths
verify against contracted paths
Infrastructure and Rollingt stock database,
Dangerous goods
IMs advises RU that train is accepted
ETI and ETA responses
Master contract between LRU and RUs
LRU
Wagon Movement
Release time to Wagon Movement Wagon
movement
IMs IMs RU RU
RU
RU LRU LRUI LRU
RUs
RU sends train composition to its
IM(s) and to next RU
RU
Wagon movement
Train reporting
Advises train ready to leave (RU to IM
handover)
Train reporting Train reporting
IM
Train reporting
IM
IM IMs, RUs, LRUs IM and RU
New ETI
Monitor Wagons
RUs
Wagon Movement
wagons
interchange RU to RU+1
Delivers wagon(s) to Customer location
Wagon Destination?
RU+1 reports wagon ETI(s) to LRU(s)
RU reports to LRU(s) RU
Interchange Point?
RU - RU
Wagon movement
LRU(s) managing wagon exceptions
RU LRU
Wagon reporting
Wagon movement
RU
yes
no
no
yes
yes, RU(s) offer is confirmed
04-10
30
35
11
19
12 or 13
14
14, 15, 16
17-19
36, 37
30 31
30
40
Telematic Applications for Railfreight defines:
• business models, • process descriptions and • data exchanged during these
processes
Relating to: • Real-time monitoring of
freight and trains,
• Marshalling and train composition.
• Path reservation.
• Management of connections with other modes of transport
• Production of accompanying electronic documents.
11 Kickoff/Meeting, Brussels, 16 November 2006
Workpackage structure
12 Kickoff/Meeting, Brussels, 16 November 2006
Project management structure
Demonstrator 1
Steering Committee
High - level Advisory Group
Project Manager
advises
Project Management Committee
Project Office
supports
advises
Thematic experts group
organises
User Community
reports to
Workpackage Leaders
are members of
Demonstration co - ordinators
are members of
WP 11
WP 19 WP
21 WP 26
Demonstrator 7
WP 21
WP 26
are members
of
organises
Case A
General Assembly
High - Level Advisory Board
Project Manager
advises
Project Management Committee
Project Office
supports
advises
Thematic Experts groups
organises
User Community
reports to
Work-Package Leaders
are members of
Case Co-ordinators -
are members of
WP 11
WP 19 WP
21 WP 26
Case J
WP 21
WP 26
are members
of
organises
13 Kickoff/Meeting, Brussels, 16 November 2006
Work-package leaders (horizontal WP)
WP-leader WP No.
WP title
Name Participant short name
Part. No.
11 Freight market characteristics Walter Vasallo AMRIE 24
12 Requirement Generator Konstantinos Antoniou TREDIT 2
13 Framework Architecture Kay Endre Fjörtoft Marintek 5
14 Implementation rules and guidelines Andrea Campagna DITS 35
15 Intermodal management services Rune Hoiseth LogIT 4
16 Dissemination, training and education Thomas Zunder UNEW 6
17 Validation Ronald Jorna Mobycon 17
18 Business Guidelines for Intermodal Mgt.
Chris Rowland Transmodal 59
19 Policy recommendations D. Paraskevadakis HIT 13
14 Kickoff/Meeting, Brussels, 16 November 2006
Business cases
Case co-ordinator Case Id
Case title
Name Participant short name
Part. No.
A NorthWest Inger Gustafsson
BMT 1
B NorthEast Caj Holm Traficon 22
C West Mel Davies BMT 1
D Central Frank Knoors Sequoyah 3
E Benelux Ronald Jorna Mobycon 17
F Elbe Roman Poersch
BMT 1
G SouthEast Dimitrios Papadopoulos Proodos 12
H SouthWest Humberto Moyano
PAG 18
J CentralSouth Rino Rosini ITL 36
15 Kickoff/Meeting, Brussels, 16 November 2006
Thematic Expert Groups (TEG)
Safety & Security • Aim. This TEG identifies common issues related to transport and
information safety. It also supports the cases with respect to security threats that are pertinent to intermodal transport.
Customs and e-government • Aim. Integration of state of the art technologies and procedures to simplify
administrative processes
Traffic information • Aim. Integration of transport and traffic information, to improve transport
performance and information about deviations.
Standardisation• Aim. Internally: Support the application of standards in the project;
externally: Identify necessary additional standardisation and provide input for such activities and incorporate industry needs and standardisation decision makers’ requirements.
16 Kickoff/Meeting, Brussels, 16 November 2006
Horizontal WPs for full duration of project WP Project month 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
Project milestones M1 M2 M3 M4 M5 M6 M7+M8 M9 M10+M11 M12 M13
Project management 0 Project Management
00.1 Administrative coordination00.2 Knowledge management00.3 Dissemination00.4 Stakeholder management00.5 Review and assessmentHorizontal WP and tasks
11 Freight market charachteristics 11.1 Freight market structure11.2 Prices, costs and modal drivers
12 Requirement generator 12.1 RTD findings / recommendations12.2 Requirement handbook12.3 High level formal model
13 Framework architecture13.1 FWF architecture strategy and co-ordination13.2 Sub-domain and interaction process model13.3 Information model and electronic messages13.4 Standardisation
14 Implementation rules and guidelines 14.1 Configuration guidelines14.2 Interfacing business and other related systems14.3 Rule definition space14.4 Business case liaison
15 Intermodal management services 15.1 Technical reference system for intermodal mgt.15.2 Extension of TCMS functionality15.3 Communication plattform15.4 Case specific technical support
16 Dissemination, training and education 16.1 Dessimination plan16.2 Online Portal16.3 Information material16.4 Confeences and presentations16.5 Dissemination, training and education
17 Validation 17.1 Validation framework17.2 Impact assessment17.3 SWOT analysis17.4 Recommendations
18 Business guidelines for intermodal mgt18.1 Process Improvement and cooperation18.2 Organisational options18.3 Technical options18.4 Administrative options
19 Policy recommendations19.1 Overview of related policies and directive initiatives19.2 Policy and legislation recommendations19.3 Proposals for standardisation 19.4 Priorities and identification of Unique Selling Points 19.5 High Level Advisory Board
17 Kickoff/Meeting, Brussels, 16 November 2006
Vertical WPs and
Cases
WP Project month 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18Project milestones M1 M2 M3 M4 M5
Cases, vertical WP and tasks Case with demonstration
21.dem Modelling of current operations D21.dem.0 M21.dem.121.A.1 Requirements definition21.A.2 Process modelling21.A.3 Rules and responsibilities 21.A.4 Improvement options D21.dem.1
22.dem Improvement specification D22.dem.0 M22.dem.122.A.1 Analyses of as-is modelling results22.A.2 Process reengineering 22.A.3 Improvement specifications D22.dem.1
23.dem Integration D23.dem.0 M23.dem.113.1 Customisation D23.dem.113.2 Integration13.3 Installation13.4 Trials and technical validation13.5 Technical/technological manual/training
24.dem Demonstration24.A.1 Organisational demonstration 24.A.2 Technical demonstration
25.dem Evaluation 25.A.1 FREIGHTWISE Evaluation Framework 25.A.2 Logistics efficiency, organisational change25.A.3 Economic assessment25.A.4 Technical assessment25.A.5 Risk assessment25.A.6 Public/private synergy25.A.7 Lessons learned and recommendations
26.dem Full scale operation26.A.1 Deployment decision26.A.2 Implementation sketchCase without demonstration
21.nod Modelling of current operations D21.nod.0 M21.nod.121.F.1 Requirements definition21.F.2 Process modelling21.F.3 Rules and responsibilities 21.F.4 Improvement options D21.nod.1
22.nod Improvement specification D22.nod.0 M22.nod.122.F.1 Analyses of as-is modelling results22.F.2 Process reengineering 22.F.3 Improvement specifications D22.nod.1
23.nod Integration23.F.1 Customisation23.F.2 Integration23.F.3 Installation23.F.4 Trials and technical validation23.F.5 Technical/technological manual
24.nod Demonstration24.F.1 Organisational demonstration 24.F.2 Technical demonstration
25.nod Evaluation D25.nod.025.F.1 FREIGHTWISE Evaluation Framework D25.nod.1 D25.nod.225.F.2 Logistics efficiency, organisational change25.F.3 Economic assessment25.F.4 Technical assessment
26.nod Full scale operation 26.F.1 Deployment decision26.F.2 Implementation sketch
18 Kickoff/Meeting, Brussels, 16 November 2006
Case A NorthWest – Forest products from Scandinavia to the continent
• SCA Transforest • Port of Trelleborg• (Hangartner)• (Green Cargo)
• BMT• LOGIT• MARINTEK• Network Models
• Norske Skog• DFDS TorLine• Port of Göteborg• Swedish National
Rail Administration
19 Kickoff/Meeting, Brussels, 16 November 2006
Main FREIGHTWISE outputs
FREIGHTWISE reference
architecture
FREIGHTWISE virtual transport network (VTN)
FREIGHTWISE Stakeholder framework
• A useful starting point for interoperable software development in the transport & logistics sector
• Hands on examples, i.e. actual systems that are instances of the FREIGHTWISE reference architecture and demonstrate particular business oriented implementations
• A concept for handling a virtual transport network, i.e. defining and managing chains or chain instances composed from the VTN
• A VTN node format with all necessary and sufficient parameters for advertising transport services (e.g., company-internal, on a trusted partners level, or open)
• A set of issues relevant to stakeholder co-operation and transport service integration (ETA monitoring, information transparency, confidentiality, security, etc)
• An inventory of information objects used by stakeholders (tools, documents, methods etc) expressing requirements per issue (e.g. a contract expressing liabilities, or a track & trace function expressing decision making parameters needed)
20 Kickoff/Meeting, Brussels, 16 November 2006
Expected results
FREIGHTWISE reference
architecture
FREIGHTWISE virtual transport network (VTN)
FREIGHTWISE Stakeholder framework
Support to EU policy on promoting co-modality
Support to industry for efficient management solutions
21 Kickoff/Meeting, Brussels, 16 November 2006
Partners (1)Shippers• Norske Skog — Norske Skogindustrier ASA
(NO) • SCA — SCA Transforest AB (SE) • P&G — Procter & Gamble Eurocor NV (BE) • Aceralia — Aceralia Corporación Siderúrgica
S.A. (ES)
Ports• SBO — Sächsische Binnenhäfen Oberelbe
GmbH (DE) • THPA — Thessaloniki Port Authority S.A.
(GR) • BLS — Buss Logistics Systems GmbH (DE) • Trelleborg — Trelleborgs Hamn AB (SE) • POG — Port of Gothenburg AB (SE) • PAG — Port Authority of Gijon (ES) • Port infolink — Port infolink bv (NL)
Public infrastructure operators• BV — Swedish National Rail Administration
(SE) • KYD — The Norwegian Coastal
Administration (NO)
3 or 4 PL & Carriers• Van Dieren — Van Dieren Maritime BV (NL) • Proodos — Greek and International Freight
Transport Company S.A. (GR) • ATG — ATG Autotransport Logistics GmbH
(DE) • DBR — Deutsche Binnenreederei AG (DE) • DFDS TL — DFDS Tor Line AB (SE) • JDR — Jan de Rijk BV (NL) • CS — Continental Surveys NV (BE)• Software and information service providers • Anco — ANCO S.A. Agencies, Commerce &
Industry (GR) • FinRoEn — Finnish Road Enterprise (FI) • Mobisoft — Mobisoft Oy (FI) • Novacom — Novacom Services (FR) • SSS — Shipping and Signalling Services NV
(BE) • Syntens — Syntens, Innovatienetwerk voor
ondernemers (NL) • Tietotalo — Tietotalo Infocenter Oy (FI) • Emsys — Emsys NV (BE) • LogIT — LogIT Systems a.s (NO)
22 Kickoff/Meeting, Brussels, 16 November 2006
Partners (2)• AMRIE — Alliance of Maritime Regional
Interests in Europe (BE) • BMT — BMT Limited (UK). The project
management is provided by BMT Transport Soutions GmbH (DE)
• BTH — Blekinge Institute of Technology (SE)
• CDV — Transport Research Centre (CZ) • CIEM — Centre Interuniversitaire D'Etude
de la Mobilité - Universite Libre de Bruxelles (BE)
• CSPD — Cesko-Saské Prístavy s.r.o. (CZ) • CTIC — Fundación Centro Tecnológico de
la Información y la Comunicación (ES) • DITS — Department of Idraulica, Trasporti,
Strade, University of Rome La Sapienza (IT) • Foor — IB Foor OÜ (EE) • HIT — Centre for Research and Technology
Hellas (GR) • ILIM — Institute of Logistics and
Warehousing (PL) • ITL — Istituto sui trasporti e la logistica (IT)
• Marintek — Norwegian Marine Technology Research Institute (NO)
• Mobycon — Diepens en Okema Groep B.V. Concordis Groep (NL)
• NM — Network Models R&D Ltd (UK) • RI — Reconnaissance International Ltd (UK) • Sequoyah — Sequoyah International
Restructuring N.V.-S.A. (BE) • SETREF — The South East European
Transport Research Forum (GR) • Stratum — Stratum OÜ (EE) • Traficon — Traficon Ltd (FI) • Transmodal — MDS Transmodal Ltd (UK) • Tredit — Trans-European Consultants for
Transport, Development and Information Technology S.A. (GR)
• TuTech — TuTech Innovation GmbH (DE) • TZL — Technik Zentrum Lübeck Förder- und
Grundstücksgesellschaft mbH (DE) • UNEW — University of Newcastle upon Tyne
(UK)
top related