balticit/elogmar

1. www.balticit.com/elogmar Structure of Web portal in transport logistics and demonstration scenarios

2. Deliverable D5 (WP4) Deliverable D7 (WP5) Deliverable D8 (WP6) Structure of Web-portal in transport logistics

3. Structure of Web-portal in transport logistics(continuation) Deliverable D4 (WP3)

4. Technical platform and demonstration scenarios (WP07 and WP08) 1) Demonstrator of Web-based Collaborative Work Environment (CWE) Resp.: LIS, RTU Major partners: LTR, IDC IT • Programming Technologies: PHP language + MySQL • Demonstration scenario: Presented by LTR (deliverable D4) • Location of Web-portal: BRCC server 2) Demonstrator of Mobile Access to CWE Two approaches: • Mobile phone • Personal Digital Assistant - Pocket PC

5. Approaches • Mobile phone (WAP protocols embedded into mobile phone, GPRS): • Restricted set of functions of Web-portal • Simplified way of information presentation in a screen • Simplified demonstration scenario • PDA: • Practically the same set of functions as in Web portal and similar • demonstration scenario • Changes in information presentation • Development: • Mobile phone solution - resp. LIS, RTU • PDA solution - resp. SONEX

6. Cargo owners or their representatives (buyer) Cargo owner (seller) Transportation group DB of alternative solutions Contracts DB DB of transportation group services General model of demonstration scenarios

7. Identif. Title Comments 1 2 3 1. Group of scenarios: Promotion of services and searching of general information in transport logistics & maritime area S1.1 Promotion of services by actors from transportation group S1.2 Searching of general information in IT&T solutions D5 S1.3 Searching of general information in legislation & regulations D7 S1.4 Searching of general information in education & training D8 2. Group of scenarios: Calculating of start-to-finish transportation tariffs and carrier selecting S2.1 On-Line transport Request S2.2 Mobile Transport Request 3. Group of scenarios: Applications of Web-services S3.1 Listing of railway terminals which are considered as terminal of departure for container transports Web service Freightrates: function GetTerminalsWithPrice () S3.2 Listing of all railway terminals which come into question as destination terminals for container transport Web service Freightrates: function GetDestinationTerminals () S3.3 Delivering the freight rates and the conditions for the chosen relation and container length Web service Freightrates: function GetFreightRate () Demonstration scenarios

8. Identif. Title Comments 1 2 3 4. Group of scenarios: Registration S4.1 New user registration as web-portal user S4.2 Expert groups registration This functionality belongs to adjacent Web-site of BRCC and can be used for users involvement in validation process 5. Group of scenarios: Users assessment of carriers service level S5 Users assessment of carriers service level 6. Group of scenarios: Maintenance of data regarding services and tariffs S6 Maintenance of data regarding services and tariffs Demonstration scenarios (continuation)

9. Scenario S1.1: Promotion of services by actors from transportation group ITx Actor from Transportation Group DB of transportation group services Scenario scheme: • Interface tables (ITx): • IT1 (deep sea shipping line): • Shipping company, • Hub Port of departure, • Agent in a Hub port of departure, • Terminals in ports of departure and destination, • Sailing, • Expected transit time. • IT2 , IT3 , IT4 , IT5 have similar structure corresponding to the structures • of Tables 2÷5 of D4 (Chapter 4).

10. Scenario S1.2: Searching of general information in IT&T solutions ● IT L 3,2 - Contents of D5 ● IT L 1,2 - Request on searching ● IT L 2,1 - Reply on request User Web-portal administrator L 1,2 L 3,2 DB of IT&T solutions L 2,1 3 1 2 Scenario scheme: Interface tables:

11. Scenario S1.3: Searching of general information in legislation & regulations L 1,2 L 3,2 L 2,1 3 1 2 ● IT L 3,2 - Contents of D7 ● IT L 1,2 - Request on searching ● IT L 2,1 - Reply on request User Web-portal administrator DB of L&R Scenario scheme: Interface tables:

12. Scenario S2.1: On-Line transport Request ● IT L 1,2 - On-Line Transport Request ● IT L 2,3 - Request to carriers from Transportation Group (Form 3 - Block train, Form 2 – Shipping line, Form 4 – Road) ● IT L 3,2 - Reply on request (filled in Forms 2, 3 and 4) ● IT L 4,3 - Information from DB regarding tariff calculating and carrier selecting ● IT L 3,4 - Request to DB L 1,2 L 2,1 3 2 1 4 L 2,3 L 3,2 L 3,4 L 4,3 Transportation group Web-portal administrator Cargo group DB of Transportation Group Services Scenario scheme: Interface tables:

13. Scenario S3: Applications of Web-services 2 3 1 Railway DB External IS Cargo group Freight Forwarder Transportation group DB of Transportation Group Services 4 Block Train Operator Road carrier Shipping Line Web service Scenario scheme:

14. Scenario S4.1: New user registration as web-portal user ● IT L 1,2 - Company’s information 1 Users (groups K1 or K2) L 1,2 Users DB 2 Scenario scheme: Interface tables:

15. Scenario S5: Users assessment of carriers service level ● IT L 1,3 - User assessment of services level of selected carrier (high, middle, low) ● IT L 2,3 - Request of potential user (actor from cargo group) to DB on statistics data regarding carriers services levels ● IT L 3,2 - Reply on request L 1,3 L 2,3 2 1 L 3,2 3 User from cargo group Potential user from cargo group DB of statistics of carriers services level Scenario scheme: Interface tables:

16. Scenario S6: Maintenance of data regarding services and tariffs ● IT L 1,5 - IF3 (D4, Annex III) ● IT L 2,3 - IF4 (D4, Annex III) ● IT L 3,2 - IF5 L 1,5 ● IT L 4,3 - IF6.2 DB of services and tariffs L 2,5 3 L 3,5 L 4,5 Multimodal Operator Road Carrier Train Operator Shipping Line 4 3 2 1 Scenario scheme: Interface tables: