captain alexander jacxsens, ghent port company ampc: demonstration: ghent-terneuzen information...

38
| pag. 1 Presentation GTi-tool (Ghent Terneuzen information tool) 5th IHMA CONGRESS Capt. Alexander Jacxsens 17/05/2012

Upload: informa-australia

Post on 03-Aug-2015

1.195 views

Category:

Business


3 download

TRANSCRIPT

| pag.

1

Presentation GTi-tool (Ghent Terneuzen information tool)

5th IHMA CONGRESS Capt. Alexander Jacxsens

17/05/2012

| pag.

THEORY:

• Reducing througput time (lead time) by optimizing bottlenecks and their interaction,

• Each bottleneck analysis done by bottleneck operator (not 1 authority),

• Scheduling (planning) limited resources (services)

17/05/2012

2

| pag.

1&2: Pilotstations Wandelaar & Steenbank

3: Flushing: exchange seapilot to canalpilot and viceversa

17/05/2012

3

| pag.

BOTTLE NECKS

4

4

5

6

7

8

9

10

4 : anchorage for lighterage on the river Scheldt (Put Terneuzen)

5 : sea lock (Westsluis) Terneuzen

6 : passage area Massagoed

7 : bridge Sluiskil

8 : bridge Sas van Gent

9 : bridge Zelzate

10: passage area Arcelor Mittal

17/05/2012

| pag.

Type of bottle necks

• (Infra)structural: lock / bridge/ (waiting) berth / possibility to cross on the canal, …

• Service: pilots (type: canal/sea, nationality: Fl or Ne), boatsmen (berth/lock), tugs, stevedoring ( loading/unloading), …

• Circumstances: too much/too little water (lock), fog and storm, pilotage: remote pilotage, heli pilot, …

• Interaction & priority between bottle necks

5

17/05/2012

| pag.

Challenge:

>2 ports in 2 countries, each with ctp’s room

> 2 authorities: Dutch & Flemish

>2 tug companies: one Dutch, one Belgian

>2 pilot associations: one Dutch and privatised, one Flemish and not privatised (abt 75/25% share of biz)

>One sealock on Dutch territory

>Only one or 2 deep drafted vessel per high tide pending pilot discretion

17/05/2012

6

| pag.

7

AIM GTi-tool

• Planning traffic in- and outbound to the Ports of Ghent and Terneuzen by the HMO’s

• All stakeholders consult one website: www.gtitool.be, fed by different systems (DB’s) such as LIS, Enigma, IVS/SRK..

• Stakeholders = nautical service providers who inform/consult each other abt their planning, Such as: boatmen, seapilots, canalpilots, VTS lock and bridge operators, shipping agents, tugboats, stevedores, cpt’s room..

• Transparent and congruent to the customer (ship / ships’ owner) and conforming to priority rules and working agreements

• Optimalisation of restrained means (lock, pilots, tugboats, …)

17/05/2012

| pag.

WORK AgreeMENTS 1. lock =key role in the

planning

2. Transparancy of data for all actors

3. Reliability of the planning

4. Neutral Port approach

5. Exchange of slots

6. Same procedure for large inland crafts

7. Planning window fixed for RTA-6h 8. Agreed parameters used in a prediction model 9. Optimalisation of maritime service

providers within the chain.

10. Same priority rules for all ports

8

17/05/2012

| pag.

Operational priority rules

• First priority: ships with a tidal window

• Second priority: liner ships and PCC with wind window (equal priority)

• Third priority: outbound ships which occupy a layberth for an inbound ship

• Fourth priority: inbound schip which can start loading and unloading operations once alongside.

• Fifth priority: ships for a waiting berth

9

17/05/2012

| pag.

Interaction TBT en GTLB

10

• TBT (ToerBeurtTijd): eta at lock gives primary indication of

slot

• GTLB: preferred time of pilot o/b.

• Optimising times based on TBT results in GTLB

• Incoming:

• > ETA-6h = slot is ‘fixed’ .

> rearrange outside that interval = no problem.

> changes within that interval: loss of slot and earliest new

slot only after 6 hours (if busy)

• Outgoing: 3hrs arrangement

17/05/2012

| pag.

Economical virtual priority rules on the by rotation lock time (TBT)

• A ship using a scarce service receives 30’ advantage on the slot time..

• example: 120’ if u are a liner vsl 30’ per used tugboat 30’ per used pilot

11 17/05/2012

| pag.

GTi tool www.gtitool.be

17-5-2012

12

dve

12

17/05/2012

| pag.

13

DISCLAIMER

17/05/2012

| pag.

Total view: outbound/inbound ships +

times bottle necks + central: sea lock

14 17/05/2012

| pag.

Basics of the GTi tool

• Horizontal: ships in- or outbound / estimated, planned and actual time

• Vertical: bottle necks listed geographicaly from sea (top) to quay (bottom) and vice versa

• Top: PAIS: Predicted AIS time passage points on the North Sea Buiten: coastal area or sea pilot station

Loods: seapilot on/off board

• Middle: VR: Flushing Road: canalpilot on/off board Slepers: tugboats available Ank.B/E: anchorage Put Terneuzen Sluis: lock Terneuzen Massagoed/Arcelor: passage points crossing large ships Sluiskil/Sas v. Gent/Zelzate: bridge passages

• Bottom: quay, pilot, tugs, boatmen, loading/unloading

15

15 17/05/2012

| pag.

Toerbeurttijd (TBT) >Primary slot time: calculation pending prediction model based on 5 categories of vessels and algorithms, based on parameters given by primary operators.

16

17-5-2012

16

| pag.

Haven van Gent: prioritering

• True prioritized list only available to

• Terneuzen Traffic Control & cpt’s room Ghent

• To optimise the bottlenecks in a chain, one favours the most restricted bottle neck first.

• Scarce services are first optmized and deployed, then the rest follows,

17-5-2012

17

17

| pag.

> 3de kolom = slot time (TBT) > Priority defined in colom 4 (per pilot/tug 30’ ) gives sequence of colum 5 > Notice: vsl “Doxa D” met TBT 14u54 jumps ahead of vsl “Leiro” with TBT 14u38. > beauty of this system: every “priority” can be modulated per “type/category” vsl & system respects theory how to optimize leadtimes in a chain with bottlnecks. > Priority parameter is defined by economical consideration.

17-5-2012

18

18

| pag.

19

CHAT BOX

17/05/2012

| pag.

How does it work,,

• example: “Leiro” planned to depart at 13u00

• prediction model calculates vsl can be at lock at 14u07

• lockopertor plans slot at 14u30

• reversed predictionmodel calculates that optimal time to depart 12u52

• pilot & stevedore confirm13u00

• pilot boarded early (12u41) and ship departed at 12u58

• ship passed Passage MassaGoed exactly at predictied time of 13u56

17-5-2012

20

20

17/05/2012

| pag.

2de example

• “Tor Petunia” 13u30

• model: at lock at 15u36

• slot set at 16u00

• optimal eparture time was 13u38

• pilot early: 13u22

• 13u25 last line ashore

• 14u14 bidge van Zelzate

• prediction: at 17u32 with PEC canapilot off board and vsl continues without seapilot

• Dedep.time 13u30 is underlined

• if you click on this time = pop up window with additional data (histroy)

17-5-2012

21

21

| pag.

History:

• agent set his ship earlier: 14u00 13u30

• this way vsl gets a slot that is more advantaeous

•Otherwise: 2u40 delay

• agent ‘monitost’ situtation with GTi tool

• the “Seaways” are prioritairy vessels; liners that call 6x/ a week

17-5-2012

22

22

| pag.

Prioritairy vessel:

17-5-2012

23

23

| pag.

Follow-up

Same vsl, entering lock at abt predicted time

ship departed at abt optimal time of 13u23 and corresponding prediction model nearly correct

!: once vsl leaves quay, real times are used in prediction model

17-5-2012

24

24

| pag.

BTV: do not proceed

17-5-2012

25

25

| pag.

GTi filters per objective

26

26 17/05/2012

| pag.

GTi – tool offset

17-5-2012

27

27

| pag.

GTi tool – Middle lock (MST)

28

28 17/05/2012

| pag.

GTi tool – Port/tugs

• Choice of Port: G : Gent T : Terneuzen

• Amount of tugs to be used: 2x SLBT : 2 tugs used

17-5-2012

29

29

| pag.

GTi tool – ligplaats Terneuzen

30

30 17/05/2012

| pag.

Economical consideration:

17-5-2012

31

31

| pag.

If you miss yr slot

• ‘Don Juan’ dep = 22u

• dep too late (lla = 23u50)

• slot planner (lock operator) reacts

• ship sails and anchers ‘Massagoed’ abt 22u30

• tries a new slot at but… 09u00

• thus: 6 uur’back’ because > 30’ late zijn slot

• 30’ due to tugs

17-5-2012

32

32

| pag.

Cpt’s room:

• if dep time altered: ‘bold’ time

• here:“Ohlau” 18u30 to 19u30

• model suggests optimal vdep.time = 19u48

•This because slot is sheduled at 22u00

• thus: 1h pilot time optimized

•No reaction/confirmation fm pilotage thus time remains ‘red’.

17-5-2012

33

33

| pag.

Back in time …

17-5-2012

34

34

| pag.

35

3:45

4:01

1:10

1:48

2:32

2:08

1:44

5:00

0:00 1:12 2:24 3:36 4:48 6:00

Congestie

Geen loods

beschikbaar

Gestaakte

loodsdienst

Laden/Lossen

Overige

Slepers

Sluis

Wachten op loods

Weersomstandighe

den

Mean delay per category

DELAYS OF MORE THEN 30’ PER SERVICE IN Q3 2011 totaal aantal uitgaande reizen 794

% reizen met vertraging 51%

% reizen met > 1 reden vertraging 8%

Eerste reden van vertraging

Classificatie aantal totale duur gemiddelde duur % aantal % totale duur

Congestie 2 7:30 3:45 0,5% 0,8%

Geen loods beschikbaar 30 120:59 4:01 7,4% 13,0%

Gestaakte loodsdienst 3 35:00 11:40 0,7% 3,7%

Laden/Lossen 32 37:49 1:10 7,9% 4,1%

Overige 9 16:18 1:48 2,2% 1,7%

Slepers 19 48:15 2:32 4,7% 5,2%

Sluis 303 650:32 2:08 74,6% 69,7%

Wachten op loods 7 12:10 1:44 1,7% 1,3%

Weersomstandigheden 1 5:00 5:00 0,2% 0,5%

406 933:33 2:17 100,0% 100,0%

17/05/2012

| pag.

Lock (primary bottle neck) knelpunt)

36

17/05/2012

| pag.

Pilots/tugs (secondary bottle neck)

37

17/05/2012

| pag.

Tx & Looking Forward ….

17/05/2012

38