Sie sind auf Seite 1von 33

All Rights Reserved, Copyright ICT Section 2011 No part of this manual may be reproduced in any form without

permission.

Table of Contents
CHAPTER 1 Preface, 3
1.1 Requirements, 3

CHAPTER 2 Introductions, 4
2.1 Document Purpose, 4 2.2 Document Scope, 4 2.3 Audience, 4 2.4 Convention, 4

CHAPTER 3 Getting Started, 5


3.1 Registration, 5 3.2 Logging In, 5 3.3 The User Interface, 7 3.4 Navigation, 8 3.5 Logging Off, 8

CHAPTER 4 Posting a New Order, 9


4.1 Delivery Operation, 14 4.2 Collection Operation, 15

CHAPTER 5 Billing, 16 CHAPTER 6 Post to iFas, 19 CHAPTER 7 Reports, 20


7.1 Posting Summary, 20 7.2 Daily Summary, 21

CHAPTER 8 Administrations, 23
8.1 Container Supplier, 23 8.2 Destination List, 24 8.3 Operator List, 25 8.4 Prime Movers, 26 8.5 Shipping Agency, 27 8.6 Trailers List, 28 8.7 Forwarding List, 29 8.8 Rate List, 30

CHAPTER 9 Acknowledgements, 31
9.1 Version History, 31 9.2 Versioning, 31 Appendix A: Requesting Assistance, 31 Appendix B: Reporting Bugs, 32 Appendix C: Acronyms & Abbreviations, 32 Appendix D: Glossary, 33
All Rights Reserved, Copyright ICT Section 2011 No part of this manual may be reproduced in any form without permission.

1 Preface
Welcome to Free Zone Internal Haulage User Guide. This documentation provides usage and background information for the Free Zone Internal Haulage System (FZIHS). The documentation is available as a paper document, PDF file, and as online help documentation on the application directory website.

1.1 Requirements
The following is needed to use the Free Zone Internal Haulage System (FZIHS) Application: a. A web browser. b. Local area network connection. JPLIHS is currently in development and is considered a beta. JPLIHS is written in the PHP scripting language and requires a MySQL database and a webserver. JPLIHS has been installed on Windows operating system. Any modern web browser should be able to function as a client. Note: To use the application, JavaScript and Session must be enabled in the browser. a. JavaScript enables web pages to interact with the browser, enhancing your online experience. JavaScript is safe and will not access any of your personal files. b. FZIHSs use of Session allows us to verify that a user has logged in. The FZIHS respects user your privacy and does not share your information nor do we permanently keep track of private data. Session created by the application terminate as soon as you close your browser.

2 Introductions
2.1 Document Purpose
This documentation is intended for use by staff of JP Logistics Sdn Bhd with a manual to assist them in their understanding and use of the Free Zone Internal Haulage System (hereaft referred to as (hereafter the FZIHS web application). Features and Benefits: a. Easy to install b. Web based c. Platform independent

2.2 Document Scope


This documentation will explain how to use the FZIHS, including step by step explanations of all the major functional process that Free Zone must perform within the application.

Page | 3

2.3 Audience
This guide is written for individuals who wish to use and understand the FZIHS system, namely Free Zone staff and related JPL personnel.

2.4 Conventions
Please familiarise yourself with the following conventions used throughout this documentation: Buttons, fields, and other system elements - All system elements are highlighted in Bold , text. Hyperlinks - There are hyperlinks from all topics in the contents of the user guide. Click refers to pressing the primary mouse button (Usually the left mouse button) button). Double click refers to pressing the primary mouse button twice. Right click refers to pressing the secondary mouse button.

Page | 4

3 Getting Started
This chapter will lead you through an example use of JPLIHS, which hopefully will allow you to get started using JPLIHS with your daily routine.

3.1 Registration
You must have a valid FZIHS user account to access the FZIHS application. To request an account: a. Click on the Request an Invite button on the homepage of the applicati directory. Request application b. Fill out and submit the FZIHS account request form (see figure 1 Registration form below). Note: All textbox mark with the * symbol are compulsory textbox. You will not be able to access FZIHS until you have a valid accou account.

Figure 1: Registration form.

3.2 Logging In
The application directory can be reach by two different addresses: a. The public domain address ( (http://apps.jplogistics.com.my/jplihs) a. The public IP address (http://202.184.111.243/jplihs http://202.184.111.243/jplihs) To log on to the application. Type the following address in your Web browser and press your Enter.

Page | 5

Figure 2: The JPL application server login page. On the homepage of the application directory you can see the login section section: a. Enter your Staff ID and password. b. Click Login. If you enter a valid staff ID and password, you will be taken to the Welcome page. If you enter invalid information, you will be shown the invalid u page: user

Figure 3: Invalid user page. If you receive this page, use the back button to return to the login page or wait for the auto auto-direct to redirect you back to login page and attempt to enter your information again. If you continue to have problems logging in please consult: a. Emran Osman (emran@johorport.com.my emran@johorport.com.my) b. Khairi Juri (khairi@johorport.com.my khairi@johorport.com.my)

Page | 6

You may also receive this page if your session has timed out. If this occurs, click the back button to log in again and restart your session. If you forget your staff ID or password you can do as follow: password, a. If your current email address is listed in our system, you can use our automated retrieval system to obtain your staff ID and password. b. Email the ICT Section at emran@johorport.com.my, khairi@johorport.com.my or call 07-253 5888, ext 770 to ask for a password reset. When the authentication and authorization process is successful, the Home page displays, allowing you to access the applications functions (see figure 4: Dashboard).

3.3 The User Interface


Refer to this section to familiarise yourself with the FZIHS interface, how to login and how to logout from the System. At the top of the dashboard area is a Menu Bar. The icons shown in this area assist the user by performing specific functions. 1. 2. 3. 4. 5. Home. Click to go back to the Homepage of the application directory. ck Application. Click to open a drop down mega-menu of other applications. Settings. Click to open a drop drop-down menu, such as the log off link. Order Request. A list containing Order request and Conta Container status. Billing. A search form with auto complete, which user can use to search all submission auto-complete, number from database. 6. Report. A report form with a date date-picker, which user can use to search the posting summary. Figure 4: Dashboard

Page | 7

3.4 Navigation
Accessing the various areas of the FZIHS application is accomplished via the navigation bar on the left hand portion of the browser. Depending upon you account permissions and other FZIHS options, some of the links may not be available. Dashboard
1. 2. 3. 4. 5. 6. New Order. Click to register a new order and add new containers. Order List. Click to view the order list. Delivery. Click to update the delivery container. Collection. Click to update the container collection. Finished. Click to view all finished container status. Billing. Click to view all billing advice for each order.

Administration
7. 8. 9. 10. 11. 12. 13. 14. Container Supplier. Click to view, add or remove container supplier from database. Destination list. Click to view, add or remove destination list from database. Operator List. Click to view, add or remove operator list from database. Prime Movers. Click to view, add or remove prime movers from database. Shipping Agency. Click to view, add or remove shipping agency from database. Trailers List. Click to view, add or remove trailers list from database. Forwarding List. Click to view, add or remove forwarding list from database. Rate List. Click to view, add or remove rate from database. r

Figure 5: Navigation Bar Note: If some of the above links do not appear when logged in, then you do not have permissions to access that feature. The Dashboard feature will be covered on page 7. The Administration feature will be covered on page 21.

3.5 Logging Off


When you have finished using the application, be sure to log off. Click Good Bye on the menu bar. A confirmation message displays. For maximum security, close confirmation your browser (see figure 4: Dashboard : Dashboard). Note: You are automatically logged off the FZIHS Web Application after a period of inactivity. Page | 8

4 Posting a New Order


When you click on the New Order link from the navigation bar you will be redirected to the New New Order Order screen. 1. Submission No cannot be left blank, user need to choose either FZ or JPLW. If left blank an blank, alert will appear on user screen (see figure 7: Alert). 2. When user click on the planning date textbox, a date-picker will appear (see figure 8: Date planning date picker Picker). 3. The Import and Export radio button when clicked will toggle the Closing Time and the Demurrage Charges textboxes.

1 2

Figure 6: New Order

Page | 9

Figure 7: Alert appeared if submission no is left blank. :

Figure 8: Date Picker will appear when user click on the planning date textbox. When user finish filling all required textbox, they can click on the Save button to continue to the next step.

3 12 Figure 9: Step 2 Pending order list. After user click Save, they will be redirected to the pending order list screen. Now, user can either: , 1. Add Container. Click to start adding new container to the order list. 2. Remove Order. Click to delete order from database. 3. Containers. You can see the number of containers in each order list.

Page | 10

Figure 10: Step 3 - Adding Container After clicking on the Add new container icon (See figure 9), user will be redirected to the Add new ), container screen. Here user can continue to the next step by clicking on the New Container link New to open a modal window (see figure 1 New container modal window). 11:

Page | 11

1 2

Figure 11: New container modal window. As you can see from the figure above the Destination from textbox and the Destination to Destination to textbox are compulsory. The Additional checkboxes are optional; these choices will determined Additional other extra charges apply to the container. Wh user finish filling in all the fields above; they can When click on the Save button to continue to step 4.

Page | 12

1 2 3

Figure 12: Step 4 Add, Edit, Remove container. The figure above will list all, the container added and user can add, edit or remove those containers by: 1. Add Container. Click to add new container (see figure 11). 2. Edit Container. Click to edit existing con container. 3. Delete Container. Click to delete container from database. After completing this step, user can click on the Update button to continue to step 5 the delivery operation screen. Note: As you see the red circled on figure 12 above, only pending container can be amend.

Page | 13

4.1 Delivery Operation


On the left side of the browser, click on the Delivery link on the accordion menu. After clicking it, you will be redirected to the pending delivery list screen (see figure 14 below).

Figure 13: The accordion menu

1 2

Figure 14: Pending delivery list.

On the pending delivery list above you can see the pending status circled in red and two icons on the right are: 1. Update icon. Click to update the delivery status. 2. Delete icon. Click to delete from database. Clicking on the update icon will redirect you to the next step (see figure 15).

Page | 14

Figure 1 Step 5 Delivery operation screen. 15:

4.2 Collection Operation


From the figure above user can fill in all, the necessary fill and click on the Update button. After update, user needs to click the Collection link on the accordion menu to go to the collection status list.

Figure 16: Accordion menu

Figure 17: Collection status list. You can see the container status circled above which automatically changed each time user updated the container. From this screen user can continue to the next step by clicking the Update icon on the right hand side of the screen. When clicked user will be redirected t the final step of the to process. Page | 15

Figure 18: Step 6 the final step. The final step of the process: 1. The Container Number textbox is compulsory. If left blank, an error will appear (see figure he 20 below). 2. You will notice when you choose OFDCK (Off Dock) from the Container Destination selectbox; the collection operator, collection PM and collection TR are disabled and a Through Ondock checkbox will appear. 3. The Last Destination selectbox is compulsory. Also when you choose OFDCK (Of Dock) a (Off Temporary stay at Ondock checkbox will appear. If you tick the selectbox and click the dock Update button, you will be redirected to the Repo Screen (see figure 19 below). 4. When you clicked on the submission no listed on the Repo Screen, the re modal Screen, repo window will appear (see figure 20 below) below).

Figure 19: Repo Screen

Page | 16

Figure 20: the Repo modal window Notes: 1) The Repo screen only appear when you chose OFDCK as your last destination. 2) Once you click on the Update or Submit button you wont be able to edit. The Update button will t disappear and you are now ready to move on to the next step. Billing.

Figure 21: Container no alert.

5 Billing

Figure 22: Billing The billing screen above can be found on the dashboard (see figure 4: Dashboard User only Dashboard). needs to type the submission number and an auto-complete will appear where you can click to search. You will be redirected to the submission number verification screen below. All the submission numbers are manually verified. Once verified, user can proceed to the billing advice. verified.

Page | 17

Figure 23: Submission number verification screen.

2 3

Figure 24: Billing advice

Page | 18

The billing advice above (see figure 2 Billing advice) will list all charges for each container. The see 24: rate and amount textbox will be automatically filled by the system, but user can still change them. 1. Debtor Code. Select the debtor code and the address of the forwarding agency will be added to the address textbox. 2. Job Implementation Date. Click to choose date from the date date-picker. 3. Add New Item. Click to add new item textboxes to the billing advice so that user can add other charges. 4. Calculate. User can click Calculate to automatically calculate the total am amount. 5. Confirm. Click Confirm if they satisfied with the billing advice (see figure 22 below) below).

Figure 25: Billing confirm Note: When you click Confirm you can still click back to make changes. Once you click Save record will be saved to database. Once you click Save you can go to the accordion menu and click the Billing link to go to the billing list screen.

Page | 19 Figure 26: Accordion menu

6 Post to iFas
123

Figure 27: Post to iFas To post the item above to iFas is simple. All you have to do is clicked the checkbox above and click the Post to iFas button (see figure 24 above). Once you click the Post to iFas button the item wil will disappear from the list above and now can be found on iFas (see figure 25: iFas below).

Figure 28: iFas

Page | 20

7 Reports
7.1 Posting Summary

Figure 29: Report The report screen above can be found on the dashboard (see figure 4: Dashboard) User can click dashboard Dashboard). the date textbox and a date-picker will appear. Choose the date and click the Search button and picker Search user will be redirected to the posting summary screen below.

Figure 30: Posting summary

Page | 21

6.2 Daily Summary

Figure 31: Daily Summary Click on the Daily summary textbox to display the popup calendar. Choose a date, and click the magnifying glass icon on the right to list all submission based on the date right, -picker (see figure 29 below).

Figure 32: Daily summary list Figure 29 above shows all daily submission based on a given date. If at a certain date, no submission rtain were found, user will be notified with a simple No record found message.

Page | 22

8 Administrations
The administration section only appeared to user with administrative privilege set by Super Admin. This section is hidden to ordinary user. nary Note: By using Adobe Reader, you can zoom in to the images below to see the details.

8.1 Container Supplier List Screen

B
3

4 5

Figure 33: Container supplier list The Container supplier list screen contains the following: 1. Pagination menu. User can easily browse the entire list by clicking the next or previous button. 2. Edit. Click to open the edit modal window. User can update the container supplier and the supplier code from here. 3. Add New. Click to open add new modal window. 4. Save. Click to add new container supplier and supplier code to the database. 5. Close. Click to close the modal window.

Page | 23

8.2 Destination List


1 2

A
4

Figure 34: Destination List The Destination list screen contains the following: 1. Pagination menu. User can easily browse the entire list by clicking the next or previous button. 2. Edit. Click to open the edit modal window. User can update the destination and the destination code from here. 3. Update. Click to update records. 4. Add New. Click to open add new modal window. 5. Save. Click to add new destination and destination code to the database. 6. Close. Click to close the modal window.

Page | 24

8.3 Operator List

B
3

Figure 35: Operator List The Operator list screen contains the following: 1. Pagination menu. User can easily browse the entire list by clicking the next or previous button. 2. Edit. Click to open the edit modal window. User can update the operator, staff no and company from here. 3. Add New. Click to open add new modal window. 4. Save. Click to add new operator, staff no and company to the database. 5. Close. Click to close the modal window.

Page | 25

8.4 Prime Movers List

B
3

Figure 36: Prime movers list The Prime Movers list screen contains the following: 1. Pagination menu. User can easily browse the entire list by clicking the next or previous button. 2. Edit. Click to open the edit modal window. User can update all the fills from here. 3. Add New. Click to open add new modal window. 4. Save. Click to add new prime mover information to the database. 5. Close. Click to close the modal window.

Page | 26

8.5 Shipping Agency List

B
3

Figure 37: Shipping agency list The Shipping Agency list screen contains the following: 1. Pagination menu. User can easily browse the entire list by clicking the next or previous button. 2. Edit. Click to open the edit modal window. User can update all the fills from here. fills 3. Add New. Click to open add new modal window. 4. Save. Click to add new shipping agency information to the database. 5. Close. Click to close the modal window.

Page | 27

8.6 Trailer List

B
3

Figure 38: Trailer list The Trailer list screen contains the following: 1. Pagination menu. User can easily browse the entire list by clicking the next or previous button. 2. Edit. Click to open the edit modal window. User can update all the fills from here. 3. Add New. Click to open add new modal window. 4. Save. Click to add new trailer information to the database. 5. Close. Click to close the modal window.

Page | 28

8.7 Forwarding List

B
3

Figure 39: Forwarding list The Forwarding agency list screen contains the following: 1. Pagination menu. User can easily browse the entire list by clicking the next or previous button. 2. Edit. Click to open the edit modal window. User can update all the fills from he here. 3. Add New. Click to open add new modal window. 4. Save. Click to add new forwarding agency information to the database. 5. Close. Click to close the modal window.

Page | 29

8.8 Rate List

B
3

Figure 40: Rate list The rate list screen contains the following: 1. Pagination menu. User can easily browse the entire list by clicking the next or previous button. 2. Edit. Click to open the edit modal window. User can update all the fills from here. 3. Add New. Click to open add new modal window. 4. Save. Click to add new rate information to the database. 5. Close. Click to close the modal window.

Page | 30

9 Acknowledgments
This document was prepared by the ICT Section, headed by Emran Osman. The first version of this document is written by Khairi Juri on 21 June 2011 (Read the revision history for detail). We would like to thank Mr Razak Sariaat from Free Zone for his assistance to the Free Zone Internal e Haulage System -- his enthusiasm drove us to the completion of this system.

9.1 Revision History


Revision 1.1 - Added Repo Screen & changed Billing screen - 18 July 2011 Revision 1.0 - Initial release for JPLIHS - 21 June 2011

9.2 Versioning
The release numbering convention we use is major.minor.micro (eg. 0.15.8). Major - Indicates a very large change in the core package; Rewrites or major milestones. Minor - Significant amount of feature addition/modification; anything that requires an upgrade script. Micro - Mostly bug fixes or minor features We will release a new version for a significant bugfix as often as monthly. Currently, JPLIHS is considered beta software. Version 2.0.10 will be used when we consider JPLIHS to be production quality. This means it should be feature full and stable enough for full production use.

Appendix A: Requesting Assistance


For general or specific question about Free Zone Internal Haulage System, contact ICT. Software and Database Unit Mr Emran Osman (emran@johorport.com.my emran@johorport.com.my) 07-253 5888 ext. 770 Mr Khairi Juri (khairi@gmail.com.my khairi@gmail.com.my) 07-253 5888 ext. 770 Head of ICT Section Mr Yohannes Nazwir (yoenaz@johorport.com.my yoenaz@johorport.com.my) 07-253 5888 ext. 746 To ask for support and hardware troubleshooting for your peripherals, please contact the following. Technical and Infrastructure Unit Mr Muhamad Riza Yusof ( (riza@johorport.com.my) 07-253 5888 ext. 746 Mr Mohd Shah Johan Mohamad Supian ( (johan@johorport.com.my) 07-253 5888 ext. 746

Page | 31

Appendix B: Reporting Bugs


The fact that bugs are unavoidable does not mean that they should be passively accepted. We are interested in your bug reports an in general in your comments. Please send your comments and and feedback to the people listed above. Please include your operating system version and your browser include software and version. If you can, please also include any specific error message you may have received.

Appendix C: Acronyms & Abbreviations :


JPL ICT FZ FZIHS WH CSS JP Logistics Sdn Bhd Information Communication Technology ommunication Free Zone Free Zone Internal Haulage System Warehouse Cascading Style Sheet

Page | 32

Appendix D: Glossary
Application Server: A software server, normally using HTTP, which has the ability to execute dynamic web applications. Also known a middleware, this piece of software is normally installed on or near the web server where it can be called upon. See also Web Application, Web Server. Authentication: The process of verifying the : identity or location of a user, service or application. Authentication is performed using at least one of three mechanisms: something you have, something you know or something you are. The authenticating application may provide cating different services based on the location, access method, time of day, etc. See also Insufficient Authentication. Authorization: The determination of what : resources a user, service or application has permission to access. Accessible resources can be cessible URLs, files, directories, servlets, databases, execution paths, etc. See also Insufficient Authorization. Session: Small amount of data sent by the web : server, to a web client, which can be stored and retrieved at a later time. Typically session are used to keep track of a users state as they traverse a web site. Debug Commands: Application debugging features : or commands that assist in identifying programming errors during the software development process. : HyperText Transfer Protocol: (Acronym HTTP) A protocol scheme used on the World Wide Web. HTTP describes the way a web-client requests data client and how a web server responds to those requests. See also Web Server, Web Browser. Insufficient Authentication: When a web site : permits an attacker to access sensitive content or rmits functionality without verifying their identity. See also Authentication. : Insufficient Authorization: When a web site permits an attacker to access sensitive content or functionality that should require inc increased access control restrictions. See also Authorization. Insufficient Session Expiration When a web site Expiration: permits an attacker to reuse old session credentials or session IDs for authorization. See also Session Replay, Session Credential, Session ID, and Session Manipulation. Insufficient Process Validation When a web site Validation: permits an attacker to bypass or circumvent the intended flow control of an application. JavaScript: A popular web browser client : client-side scripting language used to create dyna dynamic web page content. See also Active X, Java Applets, Client-Side Scripting. : Web Browser: A program used to display HyperText markup language (HTML) web pages sent by a web server. See also ActiveX controls, Cookie, Java Applets, JavaScript, Client-Side Scripting. Web Server: A general-purpose software purpose application that handles and responds to HTTP requests; A web server may utilize a web application for dynamic web page content. See also Web Application, Application Server, HyperText Transfer Protocol. ransfer Web Service: A software application that uses : Extensible Markup Language (XML) formatted messages to communicate over HTTP. Typically, software applications interact with web services rather than normal users. See also Web Server, Web Application, Application Server, HyperText Transfer Protocol.

Page | 33

Das könnte Ihnen auch gefallen