Equipment

1. Equipment BRIEF Edited by COSCON BPS

2. Brief Overview--- EQP Data Flow Chart IRIS-2 EQP modules EQP data flow only after successful creation / termination of EQP Lease Contract and/or successful EQP creation / termination ( EQP pool ) such that the container status is active

3. Brief Overview • Equipment Data Flow through three “parts”: Internet Equipment Management ( IEM ), IEIS ( locating is Sybase server) and IRIS-2 Equipment Module ( locating in Gemstone server ). • IEM • For event capturing by depots / terminals upon a real equipment movement event at their respective sites. • It provides an enquiry function on booking information before the release of equipment • IEIS • For enquiring, recording, updating and correcting of all equipment movement and its related matters, including Equipment Enquiry, Inventory Enquiry, Event Log Enquiry, Event Edit, Rejection Handling, Report Generation, etc.. • For creation of lease partners and contracts for equipment

4. Brief Overview( continue ) • IRIS-2 • Parking lot handler allows user to fix data problem occurred when data pass from Sybase to Gemstone

5. Brief Overview---Summary Table

6. IRIS-2 EQP Modules

7. Event Capturing in IEM

8. Event Capturing in IEM IRIS-2 EQP modules EQP data flow only after successful creation / termination of EQP Lease Contract and/or successful EQP creation / termination ( EQP pool ) such that the container status is active

9. Event Capturing in IEM • Event capturing • Assistant functions • Using excel file summit EQP event

10. Event Capturing in IEM ---Internet Access for vendor Users who are not COSCON staff can access IEM homepage through COSCON’s Internet IEM homepage. The website is http://inetapp.coscon.com/inetapp/iem-contents/iem-login.asp. Every facility has its own user ID, which is same as its facility code.

11. Event Capturing in IEM ---Service menu

12. Event capturing

13. Equipment Creation Types of Creation (with corresponding TCON movements listed) • New owned EQP • New leased EQP (LSI, ELI, DII) • Shipper-own containers when start of shipment cycle (SOCI) • Lease out return ( LOR ) (SLR) Creation For New leased EQP, like TCON Reference No., you need a right Authorization Number to update EQP Creation in new system, which will be assigned by Business Section of ECD Headquarters. Note: There is no new owned EQP now, so this selection in IEM Creation has been deleted.

14. Contract Number that generated by IRIS-2 automatically when create contract with specific contract type.e Remarks: 1 Refer to Contract Prefix 2. Refer to Opzone Contract Prefix*1, e.g. F for Free-Use, M for Master Lease etc. Number start from 00001 Region Code*2, e.g. SCN Number start from 001 Authorization Number that generated by IRIS-2 automatically when create authorization for a specific region to use ( called on-hire ) the lease in container. User do the creation tasks should be given with this number by trade department or staff who issue authorization number before hand. ---Concept of Authorization

15. 2 3 1 Event capturing ---Event Creation Practically and currently, most of the creation are done in IEIS. It is because it is the most direct and user need to input authorization for the creation, which will be created in IEIS too. However, there we also introduce the creation function of IEM for reference since some of the depots / vendor may also need to do creation. For better view, we just copy the key content screen and paste here for demonstration. • In this creation screen, each event should be input in each individually. There are three major parts for each input event: • 1. Event Date / Time 2. Equipment Details 3. Creation Details. • For Event Date/ Time, the default date is the current date. User could change the date by pointing mouse to the date fill and modifing. Same as year. For month, a scroll box is provided for user to choose from. User also need to input Time into the Time box next to the Year box. • For EQP details, user need to select the type of equipment (only container for region outside NAM). User also need to input the EQP number too. Besides, user need to input the S/T Group and S/T Code too.

16. Unit Number For Leased Unit, Authorization Number should be supplied Activity Date & Time Creation Type Both Unit Size/Type & its ISO SIZE/TYPE Code should be input here For Shipper Owned Unit, No Authorization Number, but Booking Number should be supplied ---Creation online in IEM

17. Press button Rest, system will ignore and clear all data you have input, and waiting for new data input. You could input 1-10 units each time, and press Submit to send out your data. Press button Main menu, system will return back to its main menu, which was shown in page 11 ---Creation online in IEM (continue)

18. Types of Termination (with corresponding TCON movements listed) • Off-hire EQP (LSR, ELR, DIO) • Loss of EQP: ATL, CTL, PTL(LOST) • Shipper-own container after completion of shipment cycle (SOCO) • Lease out to EQP ( LOT ) (SLO) • Sales(SOLD) Termination For Lease Out to EQP (SLO), like TCON Reference No., you need a right Authorization Number to update EQP Termination in new system, which will be assigned by Business Section of ECD Headquarters. Note: For Loss of EQP (LOST) and Sales (SOLD), only ECD Headquarters has here the right to update. Equipment Termination

19. Event capturing ---Termination 3 1 2

20. ---Termination online in IEM Unit Number Termination Type Activity Date & Time For Leased Out to EQP, Authorization Number should be supplied

21. Event capturing ---Gate In / Gate Out Vendor who perform Gate In / Gate Out activities are Outside Depot and Terminal. Each Outside Depot or Terminal is assigned with a specific facility code, e.g. HKG12, HKG01 etc such that gate in / out activity can be traced from the record of Sybase, IEIS. The data to show such a record, similar to creation is input in the following Gate In / Gate Out screen. For each IEM screen -  Enter or select information in the Summary Header fields.  Enter individual events.  Click Submit.

22. Event capturing ---Gate In / Gate Out Vendor who perform Gate In / Gate Out activities are Outside Depot and Terminal. Each Outside Depot or Terminal is assigned with a specific facility code, e.g. HKG12, HKG01 etc such that gate in / out activity can be traced from the record of Sybase, IEIS. The data to show such a record, similar to creation is input in the following Gate In / Gate Out screen. For each IEM screen -  Enter or select information in the Summary Header fields.  Enter individual events.  Click Submit.

23. Event capturing --- Stuff / Devan / Repack Although stuff, devan and repack are sharing the same UI, they are meaning different procedures. For stuff, it means packing LCL cargoes into the container, which is obtained by CFS. For OOCL equipment control, these containers obtained by CFS are issued through empty positioning plan so that container can be traced back. For devan, it means retrieving cargoes out of the container by CFS also. For repack, it means doing stuff and devan. Usually they are done for damage container. Once a repack activity is uploaded through IEM to Sybase, TWO events, stuff and devan will be triggered and stored in IEIS. Input for Repack: The Cntr # field refers to the container that cargo is being removed from. The Repack to Cntr# field refers to the container that cargo is being placed in.

24. Event capturing ---Change Status This screen allows you to change the condition of a piece of equipment, and to assign a sub-condition to it. Remarks: Use of status: user need to know that, if an event flow from IEM to IEIS and eventually to Gemstone and passes the two validations, then the status of the event will be updated when the event is passing back to Sybase from Gemstone.

25. Event capturing ---For North America Region only • Chassis Pool On / Pool Off • Chassis Phase In / Phase Out /Swap • Equipment Link / Unlink

26. Event capturing --- Transaction Log • This is where you specify the date range for the transactions that you wish to view.

27. Event capturing --- Transaction Log This is a sample of the transaction log that is generated based on the criteria entered on the previous screen.

28. Assistant functions

29. 1 • For a booking, it may requires one or more than one container. • General information of the booking. • Check B/L function allow depot user to know container status, for example, number of open slot available for the booking at a specific time point in order to decide whether to allow the empty gate-out / release of empty container for shipper/trucker who comes and request for empty container. • This part specifies any confirmed container number(s) and other useful info, e.g. shipper seal #, customs seal #, type, latest status ( event ) and event date/time ( local ) 2 3 4 The above search result shows that the booking, 67248680 has booked two 20GP containers, and they are already loaded on the vessel of “P&O Nedlloyd Hudson”, with VD to be EU4-PHD-003W. POL is Shanghai and POD is Rotterdam. This two containers do not need to go for transshipment port and therefore it is blank for this field. Assistant functions ---IEM B/L Inquiry

30. Assistant functions --- Change Password To change your password: • Type your old password. • Then type your new password twice. • Click Submit

31. Assistant functions --- Change Password • This screen displays when an external user Logs On for the first time.

32. Using Excel file submit EQP Event

33. Besides using the above functions, user can use a specially prepared excel file to submit EQP event to Sybase, it will be more easy and effective. Please note that the download files from bellow site were not designed to use for dialer user, we will supply Excel File to you solely. Using Excel file submit EQP Event

34. Using Excel file submit EQP Event A template Excel (Internet Equipment Management ver 2.05) sheet will be supplied to all IEM users. • User need to have the following minimum • Hard/Software Requirement: 1.PC connected to Internet 2.Window 95 or Window 97 ( Window 2K not test yet ) 3.Excel 95 or above ( English version ) 4.Internet Explore 4.0 or above

35. IEM pull down menu locate next to Help menu 1 Introduce Excel Marco File 2 4 • This is the excel file layout user will see. • It is divided into 4 major part: • IEM pull down menu • User logon details • Row of input event • Action buttons • Note: This excel file runs with Marco, user need to • click “Enable Macro” before file open 3

36. IEM pull down menu: • User need to enter at least his/her belonging facility code and press tab to activate the • IEM pull Down menu. • Go to IEM pull down menu and four functions are show, they are: • Creation / Termination • Container Movement • Stuff / Devan / Repack • Change Status Introduce IEM Pull Down Menu 2 1 We will go through each of these four function one by one.

37. * * * * * Note: this item will be removed later.

38. Using Excel file submit EQP Event ---Submit event(s) to Sybase Before submission, user need to input facility code, login ID and password. (For internal user, user need to input his/her email ID). For submit is by batch format of batch size of 20 event each time. 2. Submission is done by clicking the submit button. The status of the submitted event(s) will change to successful in case of successful submission. However, if the event fail for data validation, a error message will be returned.3. So, user is advised to use Data Validation first before Submission. 2 3 1

39. Using Excel file submit EQP Event ---Submit event(s) to Sybase 4. User should be careful that not to mis-click the clear button. After a confirmation window for clear, all selected rows of event will be cleared without Undo. In this case, user need to re-do all event(s) again.5. User may also use the “Import File” function for huge amount of events. Details of input field specification please refer to separate sheet. 5 4

40. Management in IEIS IRIS-2 EQP modules EQP data flow only after successful creation / termination of EQP Lease Contract and/or successful EQP creation / termination ( EQP pool ) such that the container status is active

41. Management in IEIS ---Event Precedence Logics • Event captured in IEM should pass the 1st stage of validation done in IEIS – Sybase before it can be updated to IEIS-Sybase. • The 1st stage of validation includes the following checking: • Check the container number against the equipment master file; then • Check the status of container concerned, i.e. active or inactive • Check with the event precedence logics i.e. no load, no discharge, and no gate-in, no gate-out on the same facility. These logics will be further explained in next slide

42. There are two precedence logics that guard the flow of the events into IEIS. They are as below: • No Load, no discharge • No gate-in, no gate-out at the same facility • For “no load, no discharge”, the rationale behind is that a container cannot be discharged in the discharge port without loading onto the vessel beforehand. Sybase, therefore, will reject any discharge event if the previous event is not a loading one. • For “no gate-in, no gate-out”, the rationale behind is that a container can only be issued at the facility if there is a relevant precedent gate-in event of it. • The load, discharge and gate-in, gate-out at the same facility should be happened in pairs with the right sequence. While there is no such requirement for other events type. • For example, a load event can come after a discharge, or without an immediate full gate-in event. In transshipment, a container can be directly transferred from one vessel to another in T/S port, i.e. discharge and then load. • While a full gate-in not necessarily follow after an empty gate-out. In transshipment, the transfer from one vessel to another may be in different ports, thus a full gate-in can follow after a full gate-out, and then by loading.

43. Management in IEIS ---Event Precedence Logics • Scope of the validation: • When user capture or EDI for 'Issue' and 'Receive' events with EP as Doc-type and 'E'mpty as the container status • Empty Plan Number validation: • To validate EP-number (Doc-reference), the system checking are: • Whether the Doc-reference is of 8 alphanumeric in length, if yes, go to point 2 below other go to next slide • The first character of the Doc-reference must not be numeric, and • The EP-number (i.e. based on the Doc-reference) exists in the ODS-EP (after system is reading the data-record)

44. Management in IEIS ---Event Precedence Logics When the Doc-reference is 8 numeric, the supplement logic check is as below: • The system will further check if the EP number is 8 numeric, if yes • Check if the previous move is “Full” move (container with Full status move), if yes • Based on previous move doc-reference above, assign Doc-type to BN to get booking. If failed, assign Doc-type to BM to get BL. If either one successful, then • Get the shipment's IB-End-Leg to check the Empty Return location, if matched with event incoming current location, then • Doc-type will be assigned either BN or BM (depending above) and Doc-reference will be supplemented to this receive event based on the previous move doc-reference above.

45. Management in IEIS--- Functions Provided Equipment Enquiry Event Log Enquiry / Edit IEM/EDI Rejection Log Enquiry / Editing Inventory Summary Enquiry Inventory Detail Enquiry Pre-discharge Enquiry Restricted Use Enquiry Restricted Use Update Lease Contract Enquiry Lease Contract Maintenance Lease Partner Enquiry Lease Partner Maintenance Equipment Creation: Container/Chassis/Genset/Lease out return Equipment Profile Maintenance Equipment Termination Equipment Creation/Termination Undo Parking Lot Event Enquiry Traffic Sheet Download

46. Management in IEIS--- Main Menu Function bar Display user’s update rights

47. Equipment Enquiry

48. Equipment Enquiry After logging on to IEIS, the “Equipment Enquiry” page normally is opened. Otherwise click on Eqp Enquiry at the function bar 5 • Select equipment type you want to enquire. • Enter Equipment number as a search criteria. If Chassis is selected, the State/Lic No will be enabled as well. • Click on “Find” button to start the search. • Click on Clear button to empty all fields. • Click on other tabs to view other aspects of the container concerned. 2 1 3 4

49. Equipment Enquiry---Result sample This page shows the current status of the equipment being enquired. The field values in blue mean that user can further click on them for more corresponding information.

50. Equipment Enquiry---Result sample(continue) This page shows the movement history of the equipment being enquired. The field values in blue mean that user can further click on them for more corresponding information