CARGO TRACKING SYSTEM IN LOGISTICS COMPANY

ABSTRACT

This project deals with the Cargo Tracking System. The system is used for
daily activities such as booking a courier, maintain employee details, process
payroll of employees, maintain hub details, maintain company details etc. The
system is used for daily activities such as booking, non-delivery, out return,
company details and pickup centers. It is very difficult to do this process manually.
Hence it is recommended to computerize the process by developing the relative
software as the world is turning into information and technology; computerization
becomes necessity in all walks of life.
Cargo management computerization is the incorporate of appropriate
technology to help administrator manage information. Technology is considered
appropriate, when it utilizes the most abundant domestic resources and conserves
capital and skilled personnel”.
This project deals with the maintenance of booking details, incoming courier
details, courier non delivery details and courier return details etc.., the main aim of
this project is to computerize the maintenance of courier management
FRONT END – PHP
BACK END - MYSQL
 CHAPTER I
INTRODUCTION

1.1 ABOUT THE PROJECT

This project deals with the Cargo Tracking System. The system is used for

daily activities such as booking a courier, maintain employee details, process

payroll of employees, maintain hub details, maintain company details etc. The

system is used for daily activities such as booking, non delivery, out return,

company details and pickup centers. It is very difficult to do this process manually.

Hence it is recommended to computerize the process by developing the relative

software as the world is turning into information and technology; computerization

becomes necessity in all walks of life.

1.2 SCOPE

Cargo management computerization is the incorporate of appropriate

technology to help administrator manage information. Technology is considered

appropriate, when it utilizes the most abundant domestic resources and conserves

capital and skilled personnel”.

1.3 OBJECTIVES

This project deals with the maintenance of booking details, incoming courier

details, courier non delivery details and courier return details etc.., the main aim of

this project is to computerize the maintenance of courier management.

 To understand the importance of logistics in supply chain management of an

organization.

To offer best service to customers.

To reduce the cost of operations.

To maintain transparency in operations.

2.2 EXISTING SYSTEM

The existing system is not totally automated. Though the system is computerized to a

particular extent, it has to do a lot of manual work. Nowadays, people are very busy and they

don’t find much time to go to a dealer to get products. But they need to buy products. And most

of the people are accessing Internet.

DRAWBACKS OF EXISTING SYSTEM

 To maintain details of bookings manually.

 Calculate salaries of the employees.

 To maintain details of the incoming parcels.

 To maintain returns details.

 To maintain out return details.

Due to these drawbacks of the existing system, there is a need for computerization.
2.3 PROPOSED SYSTEM

This project deals with the Cargo Tracking System. The proposed system is a change

to expand or improve business performance and competitive achievements. The proposed system

with an extensive background and understanding of cargo tracking, increasing the productivity

and proper workflows to process your work in the most efficient way possible. Because of their

extensive background in this industry they have created the first process driven system to ever be

designed. That data can be accessed by authorized persons. By this new system general user can

know that statical data about parcel information in particular cargo tracking.

FEATURES OF PROPOSED SYSTEM

 Reduces the amount of time taken for preparing courier statements and maintaining

accounts.

 All possible reports are being generated.

 It reduces the burden of staff.

 It improves customer satisfaction due to the improvement in the stitches.

 It also minimizes the errors in the data entry.

 CHAPTER 3
3. SYSTEM SPECIFICATION

3.1 HARDWARE SPECIFICATION

This section gives the details and specification of the hardware on which the

system is predictable to work.

Processor : Intel (R) core (TM) i3-21000

Clock speed : 1.7 GHz

RAM : 1 GB

Hard disk : 160 GB

Monitor : VGA/SVGA

Keyboard : Logitech

Mouse : Logitech (3 Buttons)

3.2 SOFTWARE SPECIFICATIONS

This section gives the details and specification of the software on which the

system is expected development environment.

Operating System : Windows XP

Front end : PHP

Back end : MYSQL

 CHAPTER IV
4 . SYSTEM DESIGN AND DEVELOPMENT

4.1 INPUT DESIGN

Input design is a part of overall system design which requires very careful attention.

Collection of input data is the most expensive part of the system. Any errors in the system will

be magnified and carry throughout the projects.

The main objectives of input design are as follows

 To produce a cost effective method of input

 To achieve the highest possible level of accuracy

 To ensure that the input is acceptable to and understood by the user

The input design process is to design the input needs into a machine-oriented format. The

objective of input design is to create an input layout that is easy to follow user friendly and to

avoid operator errors.

Login Details

The Login form user enter values for user name and password. The login button is used

to go to next form as based on the username and password.

Booking Details

The Booking details such as customer name, Item name, Item unit, origin, destination

address and etc., are maintained in the table. The required input of the customer details are given

in the corresponding textbox control.

4.2 OUTPUT DESIGN

Computer output is the most important direct source of information to the user.
Outputs computer are required primarily to communicate the results of the processing to the
users. They are also used to provide permanent copy of these results for r rate reference. Thus it
is designed in a user-friendly way to avoid user burden. The output design refers to the results
and information that is generated by the system forms many end users. To produce the outputs
which are displayed in a screen. Efficient and intelligent output design improves the system
relationships with the users and help in decision making. The output of the system is in the form
of reports.

The forms are designed in PHP with various features, which make the console output
more pleasing. Form design elaborate the way output is presented and the layout available for
capturing information.

Output design includes the following output form as,

 Branch location

 Goods Details

BRANCH LOCATION

The Branch location form contain state and location’s are display to select the option

automatically displayed the branch location information’s.

GOODS DETAILS

This goods details form contain the tracking id. To enter the tracking id retrieved from

the database to produce the single entry makes the multiple output generated forms to track the

goods details.
4.3 DATABASE DESIGN

Database is the storage media where the data given by the user are stored as such or processed and

stored. The system accepts data from the database to generate required information for the user database

determines the purpose and exact application of the system. While designing decided which facts are to

be stored in it and divide the subjects & create tables for each subject and determine the relationship

between the data in one table to other. Verify the data by entering the sample records to produce the

results.

 Easy of learning and use.

 Data independence.

 More information at low cost.

 Accuracy and integrity.

 Recovery from failure.

 Privacy and security.

 Performance.

DATA INTEGRATION

In a database, information from several files are coordinated, accessed operated upon as

through it is in a single file. Logically, the information are centralized, physically, the data may

be located on different devices, connected through data communication facilities.

DATA INTEGRITY

Data integrity means storing all data in one place only how each application to access it.

This approach results in more consistent information, one update being sufficient to achieve a

new record status for all applications, which use it. This leads to less data redundancy; data items

need not be duplicated; a reduction in the direct access storage requirement.

DATA INDEPENDENCE

Data independence is the insulation of application programs from changing aspects of

physical data organization. This objective seeks to allow changes in the content and organization

of physical data without reprogramming of applications and to allow modifications to application

programs without reorganizing the physical data.

The tables needed for each module were designed and the specification were designed

and specification of each and every column was given based on the records and details collected

during record specification of each and every column was given based on the records details

collected during record inspection during system study.

SYSTEM DEVELOPMENT

The System Development phase consists of the following steps:

 Testing the software with sample data.

 Correction of any errors if identified.

 Creating the files of the system with actual data.

 Making necessary changes to the system to find out errors.

 Training of user personnel.

The system has been tested with sample data, changes are made to the user requirements

and run in parallel with the existing system to find out the discrepancies. The user has also been

appraised how to run the system during the training period.

Each program is tested individually at the time of development using the data and has

verified that this program linked together in the way specified in the programs specification, the

computer system and its environment is tested to the satisfaction of the user. The system that has
been developed is accepted and proved to be satisfactory for the user. And so the system is going

to be implemented very soon. A simple operating procedure is included so that the user can

understand the different functions clearly and quickly.

Initially as a first step the executable form of the application is to be created and loaded

in the common server machine which is accessible to the entire user and the server is to be

connected to a network. The final stage is to document the entire system which provides

components and the operating procedures of the system.

 4.4 DATA FLOW DIAGRAM

LEVEL 0

Cargo tracking System

Administrator User

LEVEL 1

Booking Details
Booking
Table

Customer Service Cancel Details

Customer Cancelling
Table

Tracking Details
Tracking
Table
 LEVEL 2

New Office
Booking
Table

Manager Road Details

Admin Cancelling
Table

Road Map
Details Tracking
Table

Truck Details
Truck Table
4.5 DESCRIPTION OF MODULES
The purpose of code is to facilitate the identification and retrieval of data from the database.

 Administrator

 Courier Module

 Employee Module

 Report Module

ADMINISTRATOR

Administration is the main person of this system. It have all the privileges to do anything

in this system. Admin can get the information regarding Booking details and various sources.

For that administrator need to send a request for that particular authority throw web services.

COURIER MODULE

Courier module contains bookings, incomings, non delivery, company details, and pickup

centers details.

The following are the forms that exist in this module

 Booking Form

 Incoming Form

 Non delivery Form

 Company details Form

Booking Details

Booking details contains the operations such as parcel booking from customer. Through

booking operation, it allows to book the date for the customer .When the parcel is booked, store

the booking parcel source address, destination address, weight, amount details and all details in

table.
Incoming Details

Incoming details contains the operations such as booking the parcels. The incoming form

contains the details like source address and destination address the date of delivery.

Non Delivery Details

Non delivery form contains the operation such as non delivery details .In the non delivery

form like forward date, in date, source address and destination address.

Company Details

In company details module, the menus of company and view details are available.

Company Details form contain the branch office details and also maintain the new office details.

In this form contain office name, address and etc..,

EMPLOYEE MODULE

This module deals with the details about the employees who are working in the

organization and their payroll details

The following are the forms that exist in this module

 Employee details form

 payroll form

Employee form contains the different text fields, list boxes and buttons to enter the

details like employee number, name, and address, date of join, assigned area, and phone number.

REPORT MODULE

This module produce the various reports for booking and employee and various reports

etc. It also provides for preparing report according to the requirement of the user.
 CHAPTER V

5. SYSTEM TESTING AND IMPLEMENTATION

5.1 SYSTEM TESTING

Testing refers to the activities that are carried out to ensure that the final system meets the

requirements that the system is intended to satisfy. The system testing aimed at exercising the

system as a whole. The focus during the system testing is on stressing the system under extreme

conditions and ensuring that if there is any failure, it will manage. The following test cases are

carried out after the development of the system.

5.2 TYPES OF TESTING

UNIT TESTING

Unit test is considered as an adjunct to coding step. After source level code has been

developed, reviewed and verified for correct syntax, unit test is started. After the development of

the module is over, unit testing is done to test the individual units like various screens, reports

and processes. Module testing is important and major part of the project. In this system three

modules are available namely Schedule module, Recovery module and Report Generation

module. To test these each and every module individually by giving all possible test data.

INTEGRATION TESTING

Integration testing is done to test if the individual modules work together as one single

unit. In integration testing, the individual modules that are to be integrated are available for

testing. Thus the manual test data that used test the interfaces replaced by that which in generated

automatically from the various modules and can be used for testing how the modules would
actually interacting this system three modules are available namely Schedule module, Recovery

module and Report Generation module. These modules are integrated and tested to reveal the

problem interfaces.

VALIDATION TESTING:

The final step involves Validation testing, which determines whether the software

function as the user expected. The end-user rather than the system developer conducts this test.

Most software developers use a process called “Alpha and Beta Testing” to uncover that only the

end user seems able to find.

The compilation of the entire project is based on the full satisfaction of the end users. In

the project, validation testing is made in various forms.

TEST CASES

Test case is defined as to test the conditions and the functionalities of the proposed

system to determine whether the logical and syntactical operations are going in the determined

way.

LOGIN FORM

Test Case Name :login_form.

Input Types :Provide the required ‘username and password’.

Expected Result :Prompt the message ’Valid Username or Password

required’.

Actual Result :Success, It moves to the login page of the users or admin.

Otherwise, it prompts the message “Login Failed”.

 CHAPTER VI
6. SYSTEM MAINTENANCE

Implementation is the process of having systems personnel check out and put new

equipment into use, train users, install the new application depending on the size of the

organization that will be involved in using the application and the risk associated with its use,

system developers may choose to test the operation in only one area of the firm, say in one

department or with only one or two persons. Sometimes they will run the old and new systems

together to compare the results. In still other situation, developers will stop using the old system

one-day and begin using the new one the next. As we will see, each implementation strategy has

its merits, depending on the business situation in which it is considered. Regardless of the

implementation strategy used, developers strive to ensure that the system’s initial use is trouble-

free.

Once installed, applications are often used for many years. However, both the

organization and the users will change, and the environment will be different over weeks and

months. Therefore, the application will undoubtedly have to be maintained; modifications and

changes will be made to the software, files, or procedures to meet emerging user requirements.

Since organization systems and the business environment undergo continual change, the

information systems should keep pace. In this sense, implementation is ongoing process.

Evaluation of the system is performed to identify its strengths and weakness. The actual

evaluation can occur along any of the following dimensions.

 CHAPTER VII
7. CONCLUSION
It has been a great pleasure for me to work on this exciting and challenging project. This

project proved good for me as it provided practical knowledge of not only programming in PHP

and.NET web based application and no some extent Windows Application and MYSQL Server,

but also about all handling procedure related with “CARGO TRACKING SYSTEM”. It also

provides knowledge about the latest technology used in developing web enabled application and

client server technology that will be great demand in future. This will provide better

opportunities and guidance in future in developing projects independently.

B.TABLE DESIGN

TABLE NAME : Login Table

PRIMARY KEY : Uid

FIELD NAME DATA TYPE DESCRIPTION

Uid Nvarchar User ID

Passwrd Nvarchar Pass word

TABLE NAME : tbl_courier_officers

PRIMARY KEY : ID

FIELD NAME DATATYPE DESCRIPTION

cid Int New User ID
officer_name Varchar Full Name
off_pwd Varchar User Name
address Varchar Gender
email Varchar Account Type
ph_no Varchar Password
office Varchar Conform Password
reg_date Int Phone Number

TABLE NAME : Office

PRIMARY KEY : NID

FIELD NAME DATATYPE DESCRIPTION

NID Int New ID
off_name Varchar Name
address Varchar Address 1
Pno1 int Phone Number 1
City Varchar City
office_time Date/Time Office time
contact_person Varchar Handles

TABLE NAME : Branch Location

PRIMARY KEY : Branchid

FIELD NAME DATATYPE DESCRIPTION

Branchid Int Branch Id
State Varchar State
Location Varchar Location

TABLE NAME : tbl_courier

PRIMARY KEY : Bid

FIELD NAME DATATYPE DESCRIPTION

cid Int Booking ID
cons_no Varchar Customer Name
ship_name Varchar Item Name
phone Varchar Item Unit
s_add Varchar Office Sender
rev_name Varchar Office Receiver
r_phone Varchar Receiver address
r_add Date/Time Expected Delivery Date
weight Varchar Origin
invice_no Varchar Country
qty int State
book_mode
freight
mode
pick_date
pick_time
status
comments
book_date