Project Report on :-

Haulage
Management System
By :-
Palash Karmaker
Roll No. :-
23123101003
Registration No. :-
123051011003
of 2001 – 2002
Under The Guidance of :-
Mr. P.B. Ghosh,
Senior Software Engineer.
Mr. Nilanjan Ganguli,
Senior Software Engineer.
From :-

HCL TECHNOLOGIES LIMITED

SDF Building, 1st Floor,
Module 212-214, Block GP,
Sector V, Salt Lake City,
Kolkata – 700091
West Bengal, India.
 HAULAGE MANAGEMENT SYSTEM

1 Synopsis of the project

A haulage company manages the transportation of cargo from one place to another place. It
requires meticulous planning for effective operations. Most of the haulage operators function in
an ad-hoc manner, and are either not computerized or use obsolete technology which results in
Unstructured business processes, a lot of paperwork in Requesting for Transportation, Planning
and Reporting, Poor coordination between operators and their customers and Lack of Trailer
Monitoring.
HCL proposes to solve the problems of haulage management and cater to the functional
requirements of haulage management with a centralized, online, web based application. The
system will be built using Microsoft Technology (ASP, Visual Basic) and Oracle 8i as the
RDBMS.
Haulage mgmt provides services –collection, delivery, staging and diversion to internal users and
registered customers.
Customer uses these services for his convenience & requirements for the consignment when he
place order or view bill details, planner uses to allocate, arrange or plan CDA’S for the voyage
and an accountant uses for billing.
Customer place/update/cancel his orders through ROT (request of transportation) and then Cost
of order is calculated as a background process. For one order there can be at most 4 CDA’S.
CDA’S (jobs) are generated from job queue as a background process that is fired at periodic
intervals & then CDA’S are assigned to Prime Movers.
Planning is the important area of Haulage Management System. The system allow planners to
plan for the consignment of same day or the next day .The planning start at 00.00 hrs and end on
23.59 hrs. The system displays a list of CDA’S to be planned for a specific day. Master
Maintenance, Prime Mover, Trailer & Driver mgmt information details are provided while
planning.
Accountant manages the invoice information with respect to order & date recording the payment
for an order from customer database by accountant
Bill is made from customer & accountant point of view. Report is generated about commissioned
or scrapped PM ‘S, trailers, on status of CDA’S and bill & payment details.

2
2 Certificate

3
3 Acknowledgement

We have benefited a lot from the constructive criticism and suggestions given to us by our guide
Mr. P.B.Ghosh, Mr. Nilanjan Ganguli in

HCL TECHNOLOGIES LIMITED

SDF Building, 1st Floor,
Module 212-214, Block GP,
Sector V, Salt Lake City,
Kolkata – 700091
West Bengal, India

He gives us constant support and proper guidance for making a clear concept about our project
‘Haulage Management System’.

3.1 Background of the Organization (HCL Technologies Ltd.)

HCL Technologies Ltd. is one of India’s leading global IT services and product engineering
companies, providing value-added, software-led IT solutions and services to large and medium
scale organizations.
At HCL Technologies, we don’t stop asking ourselves some basic questions: Is there a better
solution? Is there a different approach? Is there any new technology? Is there a more viable
process? Is there a more cost-effective proposition?
The testimony of our technological process lies in the dedicated Offshore Development Centers
we operate for some of the world’s leading organizations. Our clientele includes over 370
prestigious organizations in the world, including 40 Fortune 500 companies.
We continue to reiterate our key imperatives of focusing on our technology competencies and
keeping pace with continuous growth and learning. We believe that in technology there are no
half-measures.
Our growth has been a result of our unique business model and clearly defined growth strategies.
Offshore-led, technology-centric, powered by domain expertise and a comprehensive
understanding of diverse business verticals, HCL Technologies’ growth has been balanced and
keeps exploring new dimensions.
The company’s principal services include:
• Technology Development Services
• Application Services
• Designing Technology
• Business Process Outsourcing

The company delivers these services to technology companies and other large- and medium-sized
organizations through its offshore infrastructure in India comprising 16 software development
centers, one network operations center and a global marketing network comprising 26 offices in
14 countries.

4
Contents
HAULAGE MANAGEMENT SYSTEM....................................................................................................2
1 SYNOPSIS OF THE PROJECT................................................................................................................2
2 CERTIFICATE............................................................................................................................................3
3 ACKNOWLEDGEMENT..........................................................................................................................4
3.1 BACKGROUND OF THE ORGANIZATION (HCL TECHNOLOGIES LTD.)..................................................................4
4 INTRODUCTION.......................................................................................................................................9
4.1 PURPOSE...................................................................................................................................................9
4.2 SCOPE.......................................................................................................................................................9
5 OVERVIEW OF HAULAGE ..................................................................................................................11
5.1 OVERVIEW OF HAULAGE OPERATIONS.........................................................................................................11
5.2 PROBLEM STATEMENTS OF THE HAULAGE INDUSTRY.....................................................................................11
5.3 OVERVIEW OF HAULAGE RESOURCES..........................................................................................................11
5.3.1 Prime Movers...............................................................................................................................11
5.3.2 Trailers........................................................................................................................................11
5.3.3 Side Loaders................................................................................................................................11
5.3.4 Containers....................................................................................................................................11
5.4 OVERVIEW OF HAULAGE LOCATIONS...........................................................................................................12
5.4.1 Base..............................................................................................................................................12
5.4.2 Depot............................................................................................................................................12
5.4.3 Interchange..................................................................................................................................12
5.4.4 Port..............................................................................................................................................12
6 SYSTEM OVERVIEW.............................................................................................................................13
7 SYSTEM PLANNING...............................................................................................................................13
8 METHODOLOGY ADOPTED................................................................................................................15
8.1 SOFTWARE USED:.....................................................................................................................................15
8.2 HARDWARE USED:...................................................................................................................................15
9 SYSTEM MAINTENANCE & EVALUATION.....................................................................................15
10 COST AND BENEFIT ANALYSIS.......................................................................................................16
11 ASSUMPTIONS & DEPENDENCIES..................................................................................................17
12 FUNCTIONAL SPECIFICATIONS.....................................................................................................18
12.1 MODULE WISE FUNCTIONALITY...............................................................................................................18
12.1.1 Master Maintenance Module.....................................................................................................18
12.1.2 Prime Mover Management Module...........................................................................................27
12.1.3 Trailer Management Module.....................................................................................................28
12.1.4 Request for Transportation (ROT) Module...............................................................................30
12.1.5 CDA Module..............................................................................................................................36
12.1.6 Planning Module.......................................................................................................................40
12.1.7 Billing & Invoicing Module.......................................................................................................42
12.1.8 Reporting Module ....................................................................................................................45
13 DESIGN SPECIFICATIONS.................................................................................................................46
13.1 CONTEXT LEVEL / 0- LEVEL DFD............................................................................................................46
13.2 FIRST LEVEL DFD...............................................................................................................................47
13.3 FLOW CHART OF HAULAGE MANAGEMENT SYSTEM ..............................................................................48
13.4 ENTITY RELATIONSHIP DIAGRAM (ERD)..................................................................................................51
13.5 WEB PAGE DESIGN SPECIFICATIONS.........................................................................................................53

5
13.5.1 General Features.......................................................................................................................53
13.5.2 HMS Homepage.........................................................................................................................53
13.5.3 Customer Registration...............................................................................................................54
13.5.4 Add New Customer Premises Details........................................................................................55
13.5.5 Administrator Homepage..........................................................................................................59
13.5.6 Planner Homepage....................................................................................................................61
13.5.7 Accounts Homepage..................................................................................................................62
13.5.8 Customer Homepage.................................................................................................................64
13.5.9 Maintain Users..........................................................................................................................64
13.5.10 Maintain User Role Mapping .................................................................................................65
13.5.11 Map Role/Page Access............................................................................................................66
13.5.12 Maintain Prime-Movers...........................................................................................................67
13.2.12.1 View Prime-Movers .............................................................................................................67
13.2.12.2 Add Prime-Movers................................................................................................................69
Maintain Trailers.................................................................................................................................73
13.2.14 Add Trailers.............................................................................................................................75
13.2.15 Maintain Locations..................................................................................................................77
13.2.15.1 View Locations......................................................................................................................77
13.2.15.2 Add Locations.......................................................................................................................79
13.2.16 Maintain Ports.........................................................................................................................82
13.2.16.1 View Ports.............................................................................................................................82
13.2.16.2 Add Ports..............................................................................................................................84
13.2.17 Maintain Drivers.....................................................................................................................87
13.17.2.1 View Drivers.........................................................................................................................87
13.2.18 Maintain Premises...................................................................................................................92
13.18.2.1 View Premises.......................................................................................................................92
13.2.19 Maintain Services....................................................................................................................96
13.19.2.1 View Services........................................................................................................................96
13.2.20 Maintain Parameters...............................................................................................................99
13.20.2.1 View Parameters...................................................................................................................99
13.2.21 Maintain Distance Matrix......................................................................................................102
13.21.2.1 View Distance Matrix.........................................................................................................102
13.21.1.2 Add Distance Matrix...........................................................................................................103
13.2.22 Maintain Prime Movers Availability.....................................................................................105
13.2.23 Maintain Prime Movers Maintenance...................................................................................106
13.2.24 Maintain Driver Availability.................................................................................................107
13.2.25 Maintain Trailer Maintenance..............................................................................................108
13.2.26 Maintain Trailer Monitoring.................................................................................................109
13.2.27 New Request Page.................................................................................................................111
13.2.28 New Order Page....................................................................................................................117
13.2.29 Update Request – Request Number Entry Page....................................................................124
13.2.30 Update Request –Detailed Page............................................................................................124
13.2.31 View Request – Request Number Entry Page........................................................................130
13.2.32 View Request – View Next to Filled Up Order......................................................................131
13.2.33 View Request – Detailed Page...............................................................................................132
13.2.34 Cancel ROT...........................................................................................................................137
13.2.35 Estimated Order Cost Page...................................................................................................138
13.2.36 Detailed CDA.........................................................................................................................140
13.2.37 Update CDA...........................................................................................................................142
13.2.38 Replan CDA...........................................................................................................................144
13.2.39 Plan for CDAs........................................................................................................................146
13.2.40 Assignment of Trailer to Prime Mover .................................................................................148
13.2.41 View Status for CDAs............................................................................................................151
13.2.42 View status of CDAs Assigned To a particular Prime Mover...............................................152
13.2.43 View Plan for a particular Prime Mover...............................................................................153
13.2.44 View Plan for a particular Prime Mover (Showing Details)................................................154
13.2.45 Update Plan For CDAs.........................................................................................................156
13.2.46 Cancel Plan for CDAs...........................................................................................................159

6
 13.2.47 Date Wise Billing Information – Request Page (Customer Point Of View)..........................159
13.2.48 Date Wise Billing Information – Response Page (Customer Point Of View)........................160
13.2.49 Order Details For Billing(Customer Point Of View)............................................................161
13.2.50 Order Wise Billing Information – Request Page (Customer Point Of View)........................162
13.2.51 Order Wise Billing Information – Response Page (Customer Point Of View)......................163
13.2.52 Customer Wise Billing Information-Request Page................................................................164
13.2.53 Customer Wise Billing Information-Response Page ............................................................166
13.2.54 Customer Order Details .......................................................................................................166
13.2.55 Date Wise Billing Information – Request Page (Accountant Point Of View) – Not Required
............................................................................................................................................................167
13.2.56 Date Wise Billing Information – Response Page (Accountant Point Of View) – Not Required
............................................................................................................................................................168
13.2.57 Order Details For Billing(Accountant Point Of View)..........................................................169
13.2.58 Order Wise Billing Information – Request Page (Accountant Point Of View).....................170
13.2.59 Order Wise Billing Information – Response Page (Accountant Point Of View)...................171
13.2.60 Payment Status.......................................................................................................................172
13.2.61 Order Details ........................................................................................................................173
13.2.62 Payment Details ....................................................................................................................174
13.2.63 List of Customers...................................................................................................................175
13.2.64 List Of Internal Users............................................................................................................176
13.2.65 List Of Prime Mover Commissioned......................................................................................177
13.2.66 List Of Prime Mover Commissioned Details.........................................................................178
13.2.67 List Of Trailer Commissioned...............................................................................................179
13.2.68 List Of Trailer Commissioned Details...................................................................................180
13.2.69 List Of Scrapped Trailers......................................................................................................181
13.2.70 List Of Scrapped Trailers Details..........................................................................................182
13.2.71 List Of Scrapped PMs............................................................................................................183
13.2.72 List Of Scrapped Prime Mover Details.................................................................................184
13.2.73 Location Wise Customer List.................................................................................................185
13.2.74 Location Wise Customer List Details....................................................................................186
13.2.75 List Of Break Down Prime Mover.........................................................................................187
13.2.76 List Of Break Down Prime Mover Details............................................................................188
13.2.77 Prime Mover Maintenance....................................................................................................189
13.2.78 Prime Mover Maintenance Details........................................................................................190
13.2.79 List Of Executed CDAs..........................................................................................................191
13.2.80 List Of Executed CDA Details...............................................................................................192
13.2.81 List Of Replanned CDA.........................................................................................................193
13.2.82 List Of Replanned CDA Details.............................................................................................194
13.2.83 List Of Cancelled Orders.......................................................................................................195
13.2.84 List Of Cancelled Orders Details..........................................................................................196
13.2.85 List Of Pending CDA.............................................................................................................197
13.2.86 List Of Cancelled Orders.......................................................................................................198
13.2.87 List Of Cancelled Orders Details..........................................................................................198
13.2.88 List Of Request.......................................................................................................................200
13.2.89 Request Status Details...........................................................................................................200
13.2.90 Payment Status Request.........................................................................................................201
13.2.91 Payment Status Details..........................................................................................................202
13.2.92 Account Invoice Payment Status............................................................................................203
13.2.93 Invoice Payment Deatils........................................................................................................203
13.2.94 Generated Invoice Status.......................................................................................................204
13.2.95 Generated Invoice Details.....................................................................................................205
13.3 DATABASE DESIGN...............................................................................................................................206
13.3.1 User Master.............................................................................................................................206
13.3.2 Employee Master.....................................................................................................................206
13.3.3 Role Master..............................................................................................................................207
13.3.4 User Role Map.........................................................................................................................207
13.3.5 Functionality Master...............................................................................................................208
13.3.6 Functionality Role Map...........................................................................................................208

7
 13.3.7 Customer Master.....................................................................................................................209
13.3.8 Prime Mover Master................................................................................................................210
13.3.9 Trailer Master..........................................................................................................................211
13.3.10 Location Master.....................................................................................................................212
13.3.11 Port Master............................................................................................................................213
13.3.12 Driver Master........................................................................................................................215
13.3.13 Premises Master....................................................................................................................216
13.3.14 Service Rate Master...............................................................................................................217
13.3.15 Parameter Master..................................................................................................................217
13.3.16 Distance Master....................................................................................................................218
13.3.17 Trailer Location ....................................................................................................................219
13.3.18 Request Details......................................................................................................................219
13.3.19 Order Details.........................................................................................................................220
13.3.20 Service Details.......................................................................................................................220
13.3.21 Consignment Details ............................................................................................................222
13.3.22 Container Details...................................................................................................................224
13.3.23 Voyage Details .....................................................................................................................224
13.3.24 Vessel Details.........................................................................................................................225
13.3.25 CDA.......................................................................................................................................226
13.3.26 Plan Audit .............................................................................................................................228
13.3.27 Plan........................................................................................................................................229
13.3.28 Plan_ PM...............................................................................................................................230
13.3.29 PM_Availability.....................................................................................................................231
13.3.30 Plan_Table_Audit..................................................................................................................232
13.3.31 Logged_Planner....................................................................................................................233
13.3.32 Driver_Shift...........................................................................................................................233
13.3.33 Bill Details.............................................................................................................................234
13.3.34 Payment History....................................................................................................................234
13.3.35 Draft/Cheque Details.............................................................................................................235
13.3.36 Bill_Dummy...........................................................................................................................236
14 METHODOLOGY TO BE USED FOR TESTING...........................................................................237
14.1 SYSTEM TESTING........................................................................................................................237
14.2 INTRODUCTION:..........................................................................................................................237
14.3 MODULE TESTING:......................................................................................................................237
14.4 INTREGRATION TESTING:.........................................................................................................237
14.5 DOMAIN TESTING: .............................................................................................................237
14.6 TEST REPORT......................................................................................................................................238
15 LIST OF ABBREVIATIONS...............................................................................................................239
16 REFERENCES......................................................................................................................................240
16.1 BIBLIOGRAPHY.....................................................................................................................................240

8
4 Introduction

4.1 Purpose
The purpose of this document is to explain the System Scope, lay down the Requirement
and Design Specifications of the Haulage Management System .
This project is a realization of effective computerization of Haulage Management
System .

This system is developed based on industrial knowledge and industrial requirement of

Haulage System for Haulage Management Companies .

This system allows the customer to place their order online through ROT(Request On
Transportation) page.

4.2 Scope

The scope of the project is to provide the system requirement specification document .
HCL proposes to solve the problems of haulage management and cater to the functional
requirements of haulage management with a centralized, online, web based application.
The system will be built using Microsoft Technology (ASP, Visual Basic) and Oracle 8i
as the RDBMS.

Authorized internal users as well as registered customers who request for haulage
services will use the Haulage Management System.

Internal users will use the system for the following purposes:
 Maintaining Master Information of various haulage resources, locations, shifts, etc
 Managing Prime Movers
 Monitoring & Managing Trailer movement
 Generating Job Advices (CDA)
 Assigning Jobs to Prime Movers
 Billing & Invoicing
 Reporting

Registered customers of the system will use it for the following purposes:
 Request for Transportation
 View Billing Details

The scope of work for building the product will be:

 Preparation of Requirement and Design Specifications
 Construction of the Haulage Management System
 Preparation of Test Plans & System Testing
 Preparation of User Manual
 Packaging & Release of the final product

9
10
5 Overview of Haulage

5.1 Overview of Haulage Operations

A haulage operator provides the following main services:
• Collection - Containers are collected from customers’ premises to be hauled towards
ports or depots.
• Delivery - Containers are delivered from ports or depots to customers.
• Diversion - Diversion is done when a prime mover has to go to more than one places
of the same customer for loading or unloading.
• Staging - Staging refers to temporary storage of containers at the base. Containers are
staged at the base and it is usually requested by the customer due to many reasons, for
example insufficient space at customer’s warehouse, change of vessel and customer’s
not available during the delivery of the container.

5.2 Problem Statements of the Haulage Industry

Haulage is a very complicated process. It requires meticulous planning for effective
operations. Most of the haulage operators function in an ad-hoc manner, and are either
not computerized or use obsolete technology.

The following are the major ailments of most of the haulage operators and their
customers
 Unstructured business processes. Processes are mostly ad-hoc in nature
 A lot of paperwork is also involved in Requesting for Transportation, Planning and
Reporting.
 Poor coordination between operators and their customers
 Lack of Trailer Monitoring

5.3 Overview of Haulage Resources

5.3.1 Prime Movers

Prime Movers are used to haul Trailers.

5.3.2 Trailers
Trailers are used to carry laden or empty containers. There are 20’ Trailers and 40’
Trailers. 20-footer trailers can only carry 20-footer containers. 40’ foot trailer can either
carry two 20-footer containers (back to back), one 40-footer container or one 20-footer
container.

5.3.3 Side Loaders

A side loader is a special trailer, which has the capabilities to offload or load container
onto the trailer. The trailer of a side loader is not detached from the Prime Mover.

5.3.4 Containers
There are various types of containers, categorized as below:
• Normal Container
• Refrigerated Container

11
 • Dangerous Container
o Direct Dangerous Container
o Normal Dangerous Container.

5.4 Overview of Haulage Locations

5.4.1 Base
Base is a place where a Prime Mover starts and ends its route. There may be one or more
bases.

5.4.2 Depot
Depot is a place where the empty containers are stored. The Haulage Operator or Third
Parties may maintain depots.

5.4.3 Interchange
An interchange is used to stage outstation containers.

5.4.4 Port
A Port is a place where containers are loaded/unloaded to/from vessels.

12
6 System Overview
HCL’s Haulage Management System will solve the problems of Haulage Management
and cater to the functional requirements with a centralized, online, web based application.

Authorized internal users, namely Planners, Accountants and Administrators as well as

registered customers who request for haulage services will use the Haulage Management
System.

Internal users will use the system for the following purposes:
 Maintaining Master Information of various haulage resources, locations, shifts, etc
 Managing Prime Movers
 Monitoring & Managing Trailer movement
 Generating Job Advices (CDA)
 Assigning Drivers to Prime Movers
 Assigning Jobs to Prime Movers
 Assigning Trailers to Prime Movers
 Billing & Invoicing
 Reporting

Registered customers of the system will use it for the following purposes:
 Place Orders for Transportation and Services
 View Billing Details

Figure 1: System Overview

7 System Planning

13
To define the complete program structure and system planning the PERT ( Program Evaluation
Review Technique) is the only way .It is the cost and time management system . The PERT chart
is the graphical representation of managing and controlling each task on proper time schedule .
The PERT chart of our project is given below:

14
 15th Feb-2004 28th Mar-2004
7th Jan-2004 15th Jan-2004 Design Coding
Project Project
Start
28th May-2004 Planning
Integration

30th June-2004 1st June-2004

1st June-2004
Implementa Testing
Help Manual tion

30th June-2004

Finish

7.1.1.1.1.1.1 PERT Chart

8 Methodology Adopted
The details of the minimum software and hardware used to implement the system.

8.1 Software Used:

1. GUI Tools: Visual Studio 6.0 , Photoshop
2. Platform: Microsoft Windows 98
3. Technology: Active Server Pages(ASP), Personal Web Server (PWS)
4. RDBMS: Oracle 8.0
5. Internet: HTML , JavaScript

8.2 Hardware Used:

1. Pentium-III: 1.1GHZ , 128 MB RAM
2. Color SVGA Monitor
3. 104 Keys Keyboard
4. Desk Jet Printer
5. Personal Web Server for website

9 System Maintenance & Evaluation

The first step for system maintenance is proper feasibility study of the system .Feasibility is
mainly occurred to make the system feasible . For this system mainly three basic feasibilities are
maintained. They are-
1) Economic Feasibility
2) Technical Feasibility
3) Legal Feasibility.

15
The system is handled only by the persons in haulage company, who are computer literate to
manage the system properly (e .g – Administrator , Planner , Accountant).So from the economic
point of view there is no such investments on money for improper use of computer .The internal
users of the system can handle the machine so the recurring cost of operation is minimized .
From the technical point of view ,if it is necessary to change certain criteria or print the different
format there should have one programmer to prepare the report format.
From the legal point of view ,the service rate of al type of CDAs should be legally permitted for a
particular distance either local or outstation and the bill generation for the customer should be
legal according to the service rate.

10 Cost and benefit Analysis

It is very difficult to define the actual cost of the project preperation . So in this system only two
types of costing is considered .
a. Project Preparation Cost
b. Project Recurring Cost

The project preparation cost implies the outdoor survey cost , project guide remuneration,
Printing cost of the project .The machine use cost, current and other costs are treated as project
recurring cost.

16
11 Assumptions & Dependencies

 There is only one Base.

 Back to Back will involve only the same customer.
 There is no Delivery Staging when From Premise is a Depot
 There is no Collection Staging when To Premise is a Depot
 For Local Trips, CDA is generated 12.00 hrs prior to the required Time of CDA
execution.
 For Outstation Trips, CDA is generated 18.00 Hrs prior to the required Time of CDA
execution.
 There is a planning time of 6.00 hrs. Prior to the Operational Preparation Time.
 There is an Operational Preparation Time of 2.00 Hrs prior to the Negative Time
Difference
 There will be a parameter driven Negative Time Difference prior to the CDA Time
Range
 All CDAs will be categorized into the following time ranges:
o 8.00 hrs – 16.00 hrs
o 16.00 hrs – 00.00 hrs
o 00.00 hrs – 8.00 hrs
 Any Prime mover can cover any distance( i.e. all prime movers have national permit)
 A ROT can not be changed once the CDAs are generated
 The staging is always done at the base
 Container is always offloaded during staging
 All Prime Movers should always start from base.
 All Prime Movers should come back to base after CDA execution.
 There are three shifts for planner, driver, and prime mover. The time schedule for
three shifts are-
o 8.00 hrs – 16.00 hrs
o 16.00 hrs – 00.00 hrs
o 00.00 hrs – 8.00 hrs
o System Planning

17
12 Functional Specifications

12.1 Module Wise Functionality

The functional modules of the Haulage Management System are:

 Master Maintenance – This module inserts in, updates, deletes data from all master
tables. The information of the master tables are required by the all the internal users
(Administrators, planners, Accountants).
 Prime Mover Management – This module maintains the information about all the
prime movers and checks the validity of all the information (e.g. date of
commissioned, date of decommissioned, date of scrap, date of purchase etc.).
 Trailer Management – This module maintains the information about all the trailers
and checks the validity of all the information (e.g. date of commissioned, date of
decommissioned, date of scrap, date of purchase etc.).
 Administration – This module is only handled by administrator. Administrator has
full access on all the pages and modules.
 Request For Transportation (ROT) – This module is accessed by customers to request
orders online.
 Collection and Delivery Advice (CDA) – This module is used to generate CDA
according to the customer request filled in the ROT module.
 Planning – After generation of CDA this module is used by the planner to plan the
CDA to execute within the required time.
 Billing & Invoicing –This module gives details of all the billing information of the
customer.
 Reporting – This module gives reports of all the information from four aspects (e.g.
customer point of view , administrator point of view , planner point of view ,
accountant point of view ,

12.1.1 Master Maintenance Module

12.1.1.1 Prime Mover Master Maintenance

The system will provide a user friendly GUI to do the following tasks
 Add New Prime Mover Information
 View Prime Mover Information
 Update existing Prime Mover Information
 Delete existing Prime Mover Information, only if the Prime-Mover has not been
commissioned.
The following information will be captured:

 Prime Mover Number

 Vehicle Registration Number
 Year of Vehicle Registration
 Manufacturer Name
 Vehicle Model
 Engine Number

18
 Chassis Number
 Purchase Price
 Date of Purchase
 Kilometers traveled at Purchase Date
 Date of Commissioning
 Kilometers traveled at Date of Commissioning
 Whether Prime-Mover has been decommissioned or not
 Date of Decommissioning
 Kilometers traveled at Date of Decommissioning
 Whether Prime-Mover has been scrapped or not
 Date of Scrap
 Scrap Value
 Weight

The system will ensure the following:

• No two Prime Movers can have the same Registration Number.

• No two Prime Movers can have the same Engine number.
• Chassis number for a Prime Mover is unique.
• The Purchase price cannot be negative.
• Date of Commissioning cannot be before the Date of Purchase.
• Date of Decommissioning cannot be before the Date of Commissioning
• Date of Scrap cannot be before the Date of Decommissioning
• Scrap Value cannot be negative

12.1.1.2 Trailer Master Maintenance

The system will provide a user friendly GUI to do the following tasks :
 Add New Trailer Information
 View Trailer Information
 Update existing Trailer Information
 Delete existing Trailer Information, only if the trailer has not been commissioned.
The following information will be captured.

 Trailer Number
 Trailer Size
 Manufacturer’s Name
 Date of Purchase
 Purchase Price
 Date of Commissioning
 Whether Trailer has been decommissioned or not
 Date of Decommissioning
 Whether Trailer has been scrapped or not
 Date Of Scrap
 Scrap Value

19
 Weight
 Side Loader

The system will ensure the following:

• The Trailer Number is unique.

• The Purchase price cannot be negative.
• Date of Commissioning cannot be before the Date of Purchase.
• Date of Decommissioning cannot be before the Date of Commissioning
• Date of Scrap cannot be before the Date of Decommissioning
• Scrap Value cannot be negative
• Side Loader information is marked as ‘Yes’ or ‘No’

12.1.1.3 Location Master Maintenance

The system will provide a user friendly GUI to do the following tasks.

 Add New Location Information

 View Location Information
 Update existing Location Information
 Delete existing Location Information
The following information will be captured.

 Location Code
 Location Name
 Standard Time
 Latitude – Degree, Minute, Seconds
 Latitude Direction – North/South
 Longitude – Degree, Minute, Seconds
 Longitude Direction – East/West
 Local X Coordinate
 Local Y Coordinate
 Local or Outstation Trip

The system will ensure the following:

• The Location Code is unique.

• The Location of the Customer can be Outstation or Local. A Local trip is denoted
by True and an Outstation trip by False.
• Local X and Y coordinates are usually taken into account if the information about
Latitude and the Longitude are not present to calculate the time that will be taken
by prime-mover.

20
12.1.1.4 Port Master Maintenance
The system will provide a user friendly GUI to do the following tasks.
 Add New Port Information
 View Port Information
 Update existing Port Information
 Delete existing Port Information
The following information will be captured.

 Port Code
 Port Name
 Port Address
 Location of the Port
 Import Opening Time for Dangerous Cargo
 Import Opening Time for Normal Cargo
 Import Opening Time for Refrigerated Cargo
 Import Closing Time for Dangerous Cargo
 Import Closing Time for Normal Cargo
 Import Closing Time for Refrigerated Cargo
 Export Opening Time for Dangerous Cargo
 Export Opening Time for Normal Cargo
 Export Opening Time for Refrigerated Cargo
 Export Closing Time for Dangerous Cargo
 Export Closing Time for Normal Cargo
 Export Closing Time for Refrigerated Cargo
 Export Shut Time

The system will ensure the following:

• No two ports will have the same code.

• Port Address will be stored with address, city and country clearly specified.
• Location of the Port will be depicted by existing location code in Location
Master.
• The Port Code and the Location of the Port will together be unique.

21
12.1.1.5 Driver Master Maintenance
The system will provide a user friendly GUI to do the following tasks :
 Add New Driver Information
 Search & View Driver Information
 Update existing Driver Information
 Delete existing Driver Information
The following information will be captured.
 Driver Code
 Driver Name
 Driver Age
 Driver Address
 Driver Phone Number
 Driver Mobile Number
 Driver Passport Number
 Driver License Number
 Driver License Validity Date
 Date of Joining
 Accident Record
 Driver Basic Wage

The system will ensure the following:

• The Driver Code is unique.

• A Driver is allotted not more than one license
• The license has a validity period, i.e. license validity date should exceed Date of
joining.

22
12.1.1.6 Premises Master Maintenance
The system will provide a user friendly GUI to do the following tasks:

 Add New Premises Information

 View Premises Information
 Update existing Premises Information
 Delete existing Premises Information
The following information will be captured.

 Premise Code
 Premise Name
 Premise Address
 Location Code of the Premise
 Customer Code of the Premise
 Premise Type
 Full Day Working
 Number of Shifts
 First Shift Opening Time
 First Shift Closing Time
 Second Shift Opening Time
 Second Shift Closing Time
 Third Shift Opening Time
 Third Shift Closing Time

The system will ensure the following:

• The Premise Code and the Location Code will together be unique. If the premise
is owned by the customer then the Premise Code, Location Code and the
Customer Code will identify the premise with its customer. No two Premises will
have the same code.
• Location of the Premises will be depicted by existing location code in Location
Master.
• Premises Type can be any of the Base, Depot, Interchange or Customer Premises.
• Number of shifts in the Premises can be minimum of 1 and maximum of 3.
• First Shift Opening Time is mandatory.
• First Shift Closing Time is mandatory and should be after First Shift Opening
Time.
• Second and Third Shift Opening Time and Closing Time are optional depending
on Number of shifts.
• Second Shift Opening Time should be considered only after First Shift Opening
Time is specified.
• Third Shift Opening Time should be considered only after Second Shift Opening
Time is specified.

23
 12.1.1.7 Service Master
The system will provide a user friendly GUI to do the following tasks

 Add New Service Information

 View Service Information
 Update existing Service Information
 Delete existing Service Information
The following information will be captured.

 Service Code
 Service Type
 Rate Of Service
 Unit Of MeasurementThe system will ensure the following.

• No two Services will have the same code.

• Service Type can be of type :-
 Direct Delivery
 Direct Collection
 Direct delivery/Direct Collection
 Direct Collection/Direct Delivery
 Staging Delivery /Staged Delivery
 Staging Collection /Staged Collection
 Direct delivery/Staging Collection + Staged Collection
 Direct Collection/Staging Delivery+ Staged Delivery
 Staging Delivery + Staged Delivery/Staging Collection + Staged Collection
 Staging Collection + Staged Collection/Staging Delivery+ Staged Delivery
 Empty Trailer Collection
• Rate of Service cannot be negative.
• The Rate depends on the service provided.
• Unit of measurement will be based on:
 Km
 Hours
• Billing is done according to these parameters.

24
12.1.1.8 Parameter Master Maintenance
The system will provide a user friendly GUI to do the following tasks:

 Add New Parameter Information

 View Parameter Information
 Update existing Parameter Information
 Delete existing Parameter Information
The following information will be captured:
 Parameter Code
 Parameter Name

Following Parameters will be entered:-

 Shift 1 Timings
 Shift 2 Timings
 Shift 3 Timings
 Lunch Break Time
 Dinner Break Time
 Average Speed of Prime Mover for Local Trip
 Average Speed of Prime Mover for Outstation Trip
 Time Window Difference in Minutes (Positive)
 Time Window Difference in Minutes (Negative)
 Loading time at Depot
 Unloading time at Depot
 Coupling Time at Depot
 Decoupling Time at Depot
 Waiting Time at Depot
 Loading Time at Base
 Unloading Time at Base
 Coupling Time at Base
 Decoupling Time at Base
 Waiting Time at Base
 Loading Time at Port
 Unloading Time at Port
 Coupling Time at Port
 Decoupling Time at Port
 Waiting Time at Port
 Loading Time at Customer Premise
 Unloading Time at Customer Premise
 Coupling Time at Customer Premise
 Decoupling Time at Customer Premise
 Waiting Time at Customer Premise
 Loading Time at Interchange

25
  Unloading Time at Interchange
 Coupling Time at Interchange
 Decoupling Time at Interchange
 Waiting Time at Interchange
 Waiting Time at an outstation location
 Minimum traveling time between two premises (Buffer Traveling Time)
 Value1
 Value2
 Unit of measurement will be:
 Km/Hour
 Hours
The system will ensure the following.
• Parameter codes will be unique.
• Value1 is mandatory and Value2 is optional.

12.1.1.9 Distance Master

The system will provide a user friendly GUI to do the following tasks.
 Add New Information about distances and time taken between two locations.
 View Distance Information.
 Update existing Distance Information.
 Delete existing Distance Information.
The following information will be captured.

 From Premise
 To Premise
 Distance
 Time taken
The system will ensure the following.

• From Premise and to Premise together will be unique.

• The Time taken will be calculated based on the Distance between the two
premises entered by user and the average speed of Prime-Mover.

12.1.1.10 Customer Master Maintenance

The system will provide a user friendly GUI to do the following tasks.

 Add New Customer Information

 Search & View Customer Information
 Update existing Customer Information
 Delete existing Customer Information
The following information will be captured.

 Customer Code
 Customer Name

26
 Customer UID
 Customer Address
 Customer Fax
 Customer Phone Number
 Customer Email
 Customer Contact Person
 Customer Priority
 Credit Limit
 Credit Rating

The system will ensure the following:

• The Customer Code is unique

• A Customer can have more than one premise in a single location .This Location
be identified by the Location Name and the Location Code.
• The Customer UID is the username by which he is registered with the system.

12.1.1.11 Role Master Maintenance

Roles will be maintained separately for each and every user. Administrator will have the
privilege to assign role(s) to all users.

Major attributes of Role are:

• Role Code
• Role Name

12.1.1.12 Functionality Master Maintenance

Major attributes of Functionality are:
• Functionality Code
• Functionality Name

12.1.1.13 Access Right Master Maintenance

Each Role will be granted with some Access Rights.
Major attributes of Access Right are:
• Access Right Code
• Access Right Name

12.1.2 Prime Mover Management Module

12.1.2.1 Prime Mover Maintenance Scheduling

The system will provide a user friendly GUI to do the following tasks:

 Add New Prime Mover Maintenance Information

 View Prime Mover Maintenance Information
 Update existing Prime Mover Maintenance InformationThe following information
will be captured.

27
 Prime Mover Number
 Maintenance Type
 From Date
 To Date
The system will ensure the following:

• The prime mover numbers are auto generated by the system.

• The type of maintenance is either routine maintenance or breakdown
maintenance, change of tyres etc. A Prime Mover can undergo one or more kinds
of maintenance.
• The ‘From Date’ field is a date between the Date of Commissioning and the Date
of Decommissioning.
• The ‘To Date’ field is a date between the Date of Commissioning and the Date of
Decommissioning.

12.1.2.2 Prime Mover Availability

The system will provide a user friendly GUI to do the following tasks.
 Add New Prime Mover Availability Information
 View existing Prime Mover Availability Information
 Update existing Prime Mover Availability Information
The following information will be captured

 Prime Mover Number

 Availability in Shift 1
 Availability in Shift 2
 Availability in Shift 3
 Reason Of Unavailability

The system will ensure the following.

• The Prime Mover numbers are auto generated by the system.
• The Availability in the shifts is marked as ‘Yes’ or ‘No’.
• If a Prime Mover is not available in any of the shifts, then the Reason for its
Unavailability is provided.

12.1.3 Trailer Management Module

12.1.3.1 Trailer Maintenance Scheduling

The system will provide a user friendly GUI to do the following tasks.
 Add New Trailer Maintenance Information
 View Trailer Maintenance Information
 Update existing Trailer Maintenance Information
The following information will be captured

28
 Trailer Number
 Maintenance Type
 From Date
 To Date
The system will ensure the following

• The Trailer numbers are auto generated by the system.

• The type of maintenance is either routine maintenance or breakdown
maintenance. A trailer can be undergoing one or more of them.
• The ‘From Date’ field is a date between the Date of Commissioning and the Date
of Decommissioning.
• The ‘To Date’ field is a date between the Date of Commissioning and the Date of
Decommissioning.

12.1.3.2 Trailer Availability

The system will provide a user friendly GUI to do the following tasks:

 Add New Trailer Availability Information

 View existing Trailer Availability Information
 Update existing Trailer Availability Information
The following information will be captured.

 Trailer Number
 Availability
 Reason Of Unavailability
The system will ensure the following.
• The Trailer numbers are auto generated by the system.
• The Availability in the shifts is marked as ‘Yes’ or ‘No’.
• If a Trailer is not available, then the Reason for its Unavailability is provided.

12.1.3.3 Trailer Monitoring

The system will provide a user friendly GUI to do the following tasks.

 View existing Trailer Present Location and Ageing Information

 Update existing Trailer Present Location and Ageing Information

The following information will be captured:

➘ Trailer Number
➘ Present Location
➘ From Date
➘ Ageing (Not Empty)
➘ Ageing (Failed Collection)
➘ Collection Date (Target )

29
➘ Collection Date (As informed by the customer)

The system will ensure the following:

• This interface provides a facility to get information about the current location and
ageing of the existing Trailers. The Trailer Numbers are auto generated by the
system. The ‘From Date’ is used to enter the date since which the trailer is present
at that location.
• The ‘Collection Date (Target)’ is the date at which the customer is supposed to
release the Trailer.
• There can be two kinds of Ageing associated with a Trailer.
• When the trailer has not been released by the customer within the target collection
date, then the ageing is auto generated and advances by 1 for every consecutive day.
• When the Haulage System fails to collect the Trailers within the specified time,
then ageing due to this factor comes into play. This is then auto generated and
advances by 1 for every consecutive day.
• The ‘Collection Ready Date’ is the date at which the customer proposes to release
the Trailer. This can be before or after the Target Collection Date.
• The CDAs for Empty Trailer Collection will be generated according to this date.

12.1.3.4 Empty Trailer Collection Scheduling

The system will provide a user friendly GUI to do the following task.

 View Empty Trailer Information

The following information will be captured.

➘ Trailer Number
➘ Present Location
➘ From Date
➘ Ageing (Not Empty)
➘ Ageing (Failed Collection)

➘ Collection Date (Target )

➘ Collection Date (As informed by the customer)
The system will ensure the following.

• This interface provides information about the current location and ageing of the
empty Trailers. The Trailer Numbers are auto generated by the system.
• The CDAs for Empty Trailer Collection will be generated according to the
Collection Date as informed by the customer.

12.1.4 Request for Transportation (ROT) Module

ROT is the primary customer interface using which customers will be able to do the
following:

30
  Submit New Requests/Orders
 Modify Existing Requests/Orders
 Cancel Existing Requests/Orders
 Search & View Existing Requests/Orders

12.1.4.1 New Request/Order

The system will provide user friendly GUI to capture the following ROT information:

 Request Header Information

o Request Number
o Request Date
 Order Header Information
o Order Number
o Order Date
o Order Type (Simple or Compound – mutually exclusive)

12.1.4.1.1 Service Required Details – Simple Order

Service Type Information - Customers will be able to select the following types of
services.

 Service Type
• Direct Delivery
• Direct Collection

• Staging Delivery & Staged Delivery

• Staging Collection & Staged Collection
o From Premise
o To Premise
o Whether Delivery Offload is Required (for Direct Delivery and Staged
Delivery)
o Whether Delivery Waiting is Required (for Direct Delivery and Staged
Delivery)
o Delivery Waiting Time (in minutes)
o Whether Diversion is required (for Direct Delivery)
o Diversion Second Premise

o Diversion Second Premise Waiting Option

o Diversion Second Premise Waiting Time
 Consignment Details
o Consignment No.
o Consignment Type
o Import-Export
o Consignment Weight

31
 o Consignment Quantity
o Unit of Measurement
o Consignment Value
o Consignor Name
o Consignor Address
o Consignor Contact Number
o Consignor Contact Person
o Consignee Name
o Consignee Address
o Consignee Contact Number
o Consignee Contact Person
 Container Details
o Container No.
o Container Size
o Container Type (Normal/Refrigerated)
o Container Owner
o Container Status (Laden / Empty)
 Voyage Details
o Voyage Number
o Voyage Origin
o Voyage Destination
o Port Code
o Vessel Number
o ETA Date
o ETA Time
 Vessel Details
o Vessel No.
o Vessel Name
o Vessel Type
o Vessel Country Of Origin

o Shipping Line
o Vessel Capacity
o Voyage No.

12.1.4.1.1.1 Determination of Back-To-Back CDAs

The system will determine Back-To-Back CDAs and prompt the user for acceptance. If
the user accepts Back-To-Back, then only the Orders will be treated as Back-To-Back.

The system will determine whether two CDAs can be delivered Back-To-Back based on
the following conditions.

 The CDA is a Direct Delivery CDA – Back-To-Back will only be possible only when
the Order is a Direct Delivery Order

32
 The Consignment Types in the respective containers are not mutually conflicting
 The From Premise and To Premise of the CDAs are same
 The Delivery Required Time of both the Orders are within 6 hours of each other
 The Voyage Numbers of both orders should be the same
 The Vessel Numbers of both orders should be the same

12.1.4.1.1.2 Calculation of Delivery Staging Period

The system will judge whether Staging is required and calculate the Staging Period.
Delivery Staging Period will be the difference between ETA Date/Time of Vessel and the
Delivery Required Date/Time.

12.1.4.1.1.3 Calculation of Collection Staging Period

The system will judge whether Staging is required and calculate the Staging Period.
Collection Staging Period will be the difference between Collection Required Date
Date/Time of Vessel and the ETA Date/Time

12.1.4.1.2 Job Types

There are 11 types of jobs to be performed .The names of them are given below
1) Direct Delivery
2) Direct Collection
3) Direct delivery/Direct Collection
4) Direct Collection/Direct Delivery
5) Staging Delivery /Staged Delivery
6) Staging Collection /Staged Collection
7) Direct delivery/Staging Collection + Staged Collection
8) Direct Collection/Staging Delivery+ Staged Delivery
9) Staging Deli9very + Staged Delivery/Staging Collection + Staged Collection
10) Staging Collection + Staged Collection/Staging Delivery+ Staged Delivery
11) Empty Trailer Collection

12.1.4.1.3 Service Required Details – Compound Order

 Service Type Information - Customers will be able to select the following types of
services.
o Service Type
 Direct Delivery with Direct Collection
 Direct Collection with Direct Delivery
 Direct Delivery with Staging Collection & Staged Collection
 Direct Collection with Staging Delivery & Staged Delivery

33
  Staging Delivery & Staged Delivery with Staging Collection & Staged
Collection
 Staging Collection & Staged Collection with Staging Delivery &
Staged Delivery
o From Premise
o To Premise
o Drop Premise
o Whether Delivery Offload is Required (for Direct Delivery and Staged
Delivery)
o Whether Delivery Waiting is Required (for Direct Delivery and Staged
Delivery)
o Delivery Waiting Time (in minutes)
o Whether Diversion is required (for Direct Delivery)
o Diversion Second Premise
o Diversion Second Premise Waiting Option
o Diversion Second Premise Waiting Time
 Consignment Details – for Delivery as well as Collection
o Consignment No.
o Consignment Type
o Import-Export
o Consignment Quantity
o Unit of Measurement
o Consignment Value
o Consignor Name
o Consignor Address
o Consignor Contact Number
o Consignor Contact Person
o Consignee Name
o Consignee Address
o Consignee Contact Number
o Consignee Contact Person
 Container Details – for Delivery, as well as Collection
o Container No.
o Container Size
o Container Type (Normal/Refrigerated)
o Container Owner
o Container Status (Laden / Empty)
 Voyage Details – for Delivery as well as Collection
o Voyage Number
o Port
o Vessel Number
o ETA Date
o ETA Time

34
 Vessel Details – For Delivery as well as Collection
o Vessel No.
o Vessel Name
o Vessel Type
o Vessel Country Of Origin
o Shipping Line

12.1.4.2 Modification of Request/Order

The system will provide a user-interface to query for an existing request. The system will
retrieve the request from the database and present request to the authorized user. The
following information in the ROT will be editable:
The system will allow modification of Orders under the following circumstances.
 When no CDAs pertaining to the Order have been generated.

12.1.4.3 Cancellation of Request/Order

The system will provide a user-interface to query for an existing request. The system will
retrieve the Request from the database and present Request to the authorized user.
The system will allow cancellation of Requests under the following circumstances.

 When none of the Orders in the Request have been executed.

 When none of the CDAs pertaining to Orders in the Request have been executed
The system will allow cancellation of Orders under the following circumstances.

 When the particular Order is not executed.

 When none of the CDAs pertaining to the Order have been generated

12.1.4.4 Search & View Request/Order

The system will provide a user-friendly facility to search for existing Requests and view
their details
The following information is available to the users

 Request Number
 Request Date
 Request Status
 Request Closed Date (if a Request is closed)
For each Request, the following Order Details will be visible
 Order Number
 Order Date
 Order Status
 Order Value
For each Order, the following details will be shown
 Jobs Completed with completion date
 Jobs pending

35
12.1.5 CDA Module

12.1.5.1 CDA
A CDA (Collection & Delivery Advice) is a job to be performed by a Prime Mover.
CDAs are generated on a day-to-day basis based on
 Customer Orders
 Empty Trailer Collection Requirements

12.1.5.1.1 CDA Impex Type

CDAs can be of classified into two types based on import/export types:
 Import CDA
 Export CDA
 Others – Relevant for Empty Trailer Collection CDA

12.1.5.1.2 CDA Service Type

There are two CDA Service Types:
 Delivery CDA
 Collection CDA

12.1.5.1.3 CDA Service Sub-Type

For Delivery & Collection CDA types there will always be a CDA sub type. Empty
Trailer Collection CDA will not have any sub-type

CDA Sub-types are:

 Direct
 Staging
 Staged

For each Staging CDA there will be a corresponding Staged CDA.

12.1.5.1.4 Diversion Option

 Diversion Required
 Diversion Not Required
If Diversion is required, the following information needs to be captured by the system
 Diversion Second Premise
 Diversion Second Premise Waiting Time

12.1.5.1.5 Offload Option

 Offload Not Required

36
 Offload Required
If Diversion is required, the following points need to be taken into consideration
 Offload takes place by default at the Diversion First Premise
 If Offload Not Required is selected, Offload does not take place at the Diversion
Second Premise1

12.1.5.2 CDA Generation

CDA will be generated / regenerated based on pre-defined rules. The following
information should be stored in the form of CDAs and presented to planners for planning
purposes.
 Interim Status - Whether Not Started, Started or Done
 CDA Status – Whether Executed or Not
 CDA Number - Unique for a CDA
 Request Number – The Request Number pertaining to the Order from which the CDA
is generated.
 Order Number - The Order Number pertaining to the Order from which the CDA is
generated.
 CDA Impex Type – Whether Import or Export
 Required Date & Time
 Service Type (Delivery or Collection)
 Service Sub-Type (Direct or Staging)
 Offload Option
 Waiting Time
 Diversion Option
 Diversion Second Premise (Relevant only if Diversion is required for delivery)
 Diversion Second Premise Waiting Time (Relevant only if Diversion is required for
delivery)
 Diversion Second Premise Offload Option
 Container Number – The Container number of the container to be collected, if any
 Container Size - The Container size of the container to be collected. If no container is
to be collected, the Container Size is zero.
 Back-To-Back CDA Option – Whether there is a Back-To-Back CDA associated with
the current CDA
 Back-To-Back CDA Number – CDA Number of the Back-To-Back CDA associated
with the current CDA
 ETA Date & Time
 From Premise
 To Premise
 Side Loader Option – Whether Side Loader is required
 Collection Ready Date & Time – This will store the Collection Ready Date & Time
as informed by Customer
 Empty Trailer Collection Date – This date will be calculated as Delivery Required
Date plus 5 days.
 Consignment Type
 Local or Outstation

37
12.1.5.2.1 CDA Generation Rules
12.1.5.2.1.1 Simple Vs Compound Orders

12.1.5.2.1.1.1 Simple Orders

 Empty trailer collection
 Direct Delivery – One Order One CDA based on Required Date/Time
 Direct Collection – One Order One CDA based on Required Date/Time
 Staging & Staged Delivery - One Order Two CDAs.
o For Staging Delivery, CDA is generated based on ETA Time as adjusted by
the Port opening & closing time for the relevant Consignment Type (Normal,
Refrigerated, Dangerous, etc).
o For Staged Delivery, CDA is generated based on Required Time.
 Staging & Staged Collection – One Order Two CDAs
o For Staging Collection, CDA is generated based on Required Time
o For Staged Collection, CDA is generated based on ETA Time as adjusted by
the Port opening & closing time for the relevant Consignment Type (Normal,
Refrigerated, Dangerous, etc).

12.1.5.2.1.1.2 Compound Orders

 Direct Delivery with Direct Collection – One Order Two CDAs
o Direct Delivery
o Direct Collection
 Direct Collection with Direct Delivery – One Order Two CDAs
o Direct Collection
o Direct Delivery

 Direct Delivery with Staging Collection & Staged Collection - One Order Three
CDAs
o Direct Delivery
o Staging Collection
o Staged Collection
 Direct Collection with Staging Delivery & Staged Delivery – One Order Three CDAs
o Direct Collection
o Staging Delivery
o Staged Delivery
 Staging Delivery & Staged Delivery with Staging Collection & Staged Collection –
One Order Four CDAs

38
 o Staging Delivery
o Staged Delivery
o Staging Collection
o Staged Collection
 Staging Collection & Staged Collection with Staging Delivery & Staged Delivery –
One Order Four CDAs.
o Staging Collection
o Staged Collection
o Staging Delivery
o Staged Delivery

12.1.5.2.1.2 Time Range

The system will consider CDA Time Range pertaining to the Required Date/Time. The
system will consider the following time ranges for this purpose:
 8.00 hrs – 16.00 hrs : For all CDAs having Required Date/Time in this range
 16.00 hrs – 00.00 hrs : For all CDAs having Required Date/Time in this range
 00.00 hrs – 8.00 hrs : For all CDAs having Required Date/Time in this range

12.1.5.2.1.3 Local & Outstation Orders

The system will have backend processes that will be run at periodic intervals to generate
CDAs from Orders.

12.1.5.2.1.3.1 For Local Orders

The system will consider the lower limit of the corresponding CDA Time Range, the
Operational Preparation Time and the Planning Time for the CDA.

CDA Generation Time = Lower Limit of Range – Negative Time Difference -

Operational Preparation Time – Planning Time.

Example:
For an Order with Required Time 10.00 am on 20 January, the CDA Generation Time =
8.00 - 4.00 – 2.00 – 6.00 = 20.00 Hrs on 19 January.

12.1.5.2.1.3.2 For Outstation Orders

The system will consider the lower limit of the corresponding CDA Time Range, the
Operational Preparation Time and the Planning Time for the CDA.

CDA Generation Time = Lower Limit of Range – Negative Time Difference -

Operational Preparation Time – Planning Time.

Example:
For an Order with Required Time 10.00 am on 20 January, the CDA Generation Time =
8.00 - 4.00 – 2.00 – 18.00 = 8.00 Hrs on 19 January.

12.1.5.2.2 Re-plan CDA

39
Replan CDAs are those CDAs the Required Date of which get changed subsequent to the
generation of the CDA.

12.1.5.2.2.1 Re-plan Due To Customer Request

Required Date of CDAs may get changed as a result of communication from customer. In
such cases, the ageing of CDAs is calculated from the Re-plan Date as communicated by
the customer.

If a customer requests for a re-plan subsequent to a re-plan by the Planner, then the
ageing will be calculated from the re-plan date as communicated by the customer.

12.1.5.2.2.2 Re-plan by Planner

In certain cases the Planner has to Re-plan the execution date of CDAs. In such cases, the
ageing of the CDA is calculated based on the original Required Date of the CDA if the
CDA has not re-planned been earlier due to communication from customer.

If the CDA has been replanned by planner subsequent to a re-plan request by the
customer, then the ageing will be calculated based on the re-plan date as asked by the
customer

12.1.5.2.3 Pending CDA

Pending CDAs will be aged with respect to the Delivery Required Date or Collection
Required date, as the case may be.
Pending CDAs will be shown in a different color coding – Pending 1 – 3 days yellow
background, 4-6 days orange background, 7 days or more in a red background.

12.1.5.2.4 Empty Trailer Collection CDA

When a trailer is decoupled at any customer premise by any prime mover and stayed at
that customer premise then to collect the empty trailer to the base a new CDA is
generated which is called Empty Trailer Collection CDA.

12.1.5.3 View CDA

Shows the details of the generated CDA and the fields can not be modified.

12.1.5.4 Update CDA

CDAs can be updated within a specified time limit.
Only internal users can update CDAs.

12.1.5.5 Cancel CDA

CDAs can be cancelled within a specified time limit.
Only internal users can cancel CDAs.

12.1.6 Planning Module

Default screen will show how the CDAs to be planned for the planning day.

40
12.1.6.1 CDAs To Be Planned
This gives the list of CDAs which are to executed and planned for the particular planning
day according to the CDA required time and required date.

12.1.6.2 Assignment of CDAs to Prime Movers

CDAs can be assigned only to those Prime Movers that are available. Prime Movers are
considered to be available under the following situations.
 When they have not yet been decommissioned
 When they are not scheduled for maintenance
 When Permits of the Prime Movers are valid

Back-To-Back CDAs – When the first CDA is planned the corresponding Back-To-Back
CDA should be automatically assigned to the same Prime Mover by the application.

12.1.6.3 Assignment of Trailers to Prime Movers

Trailers can be assigned only to those Prime Movers that are available. Trailers are
considered to be available under the following situations.
 When they have not yet been decommissioned
 When they are not scheduled for maintenance
 When Permits of the Prime Movers are valid

Back-To-Back CDAs – The system should automatically assign an available 40’ Trailer
to Prime Movers starting with Back-To-Back CDAs. The system should not allow
assignment of 20’ Trailer to Prime Movers associated with any Back-To-Back CDA.

12.1.6.4 View Plan

This shows all the details of the plan which is done for the particular CDAs (e.g. which
trailer, driver and prime mover are allocated for the particular CDA). For each prime
mover one plan should be done.

Within one plan more than one CDAs can be planned .This also shows the interim status
of the CDA, visit no. of the prime mover etc.

The following information will be captured.

♦ Container Size
♦ Container No.
♦ Prime Mover No.
♦ CDA No.
♦ Driver
♦ Visit No.
♦ Premise
♦ Visit Start Date
♦ Visit Start Time

41
 ♦ Start Trailer Size
♦ Start Trailer No.
♦ End Trailer Size
♦ End Trailer No.
♦ Interim Status
• Started
• Not Started
• Done

12.1.6.5 Update Plan

The plan for a CDA can be updated when planner needs to do it. Only the following
fields can be updated-
• Visit Number
• Prime Mover allocated for a particular CDA
• Trailer allocated for a particular CDA
• Driver assigned for a particular CDA

12.1.6.6 Mark Executed CDAs

The CDAs which are already executed, the planner manually marks them as executed and
these CDAs are called Mark Executed CDAs.

12.1.6.7 Mark Replan CDAs

The system should provide a user-friendly facility to enable planners to identify CDAs
that could not be executed during the course of an operational day. For this an interactive
list of such CDAs is required. The planner should be able to select such CDAs that are to
be re-planned, along with the following information:
 Replan Date – By default the re-plan date should be the day following the required
date of the original CDA. The system should allow the user to capture the re-plan
date. CDAs will be regenerated for the date entered.
 Replan Priority – The system should allow the planner to select the re-plan priority.
Thre priorities are considered.
• High
• Medium
• Low

12.1.7 Billing & Invoicing Module

This module describes all billing details for any CDA; any order containing more than
one CDA. The order which contains more than one CDA, when all CDAs are executed
then only the bill for the order is generated. Bill generation is a background process. The
bill status can be accessed by the
• Accountants
• Customers

12.1.7.1 Billing of Back To Back Orders

Do not give discounts on first order. Give discounts on the second order.

42
 12.1.7.2 Administration Module
This will be the main page of the Application.
The Homepage will contain links to access functionalities of the application. These links
will depend on the Role of the user who has logged in.

12.1.7.3 Login Validation

A user has to login to the system to access the Haulage Management System.

The user will login to the HMS through Login screen where the user will have to input
Username and Password.

A user may be assigned to multiple roles. In such a scenario, the system will determine
the roles of the user and provide the appropriate access privileges. The system will lead
the user to the appropriate Homepage depending on the role.

The system will validate the login information with the user information maintained at
the central data repository.

The system will notify the user about invalid login information, in any event of invalid
login.

12.1.7.4 Customer Registration/Profile Information

The system will provide a user-friendly facility to new customers to register themselves
before accessing the functionalities offered by the system.

The following information will be captured by the system during this process:
 UID
 Password
 Customer Name
 Customer Billing Address
 Customer Phone Number
 Customer Fax Number
 Customer Email
 Customer Contact Person

Each customer may have one or more premises. Customer needs to enter details of all
such Premises. The following information needs to be captured:
 Premise Name
 Premise Address
 Location of the Premise
 Full Day Working
 Number of Shifts
 First Shift Opening Time
 First Shift Closing Time
 Second Shift Opening Time

43
 Second Shift Closing Time
 Third Shift Opening Time
 Third Shift Closing Time

12.1.7.5 User Registration

The system will provide a user-friendly facility to Administrators to register Planners,

Accountants and other Internal Users (if any) so as to enable them to access the system
and perform their tasks.
The following information will be captured by the system during this process:
 Name of the Employee (User)
 Department of the Employee
 Designation of the Employee
 UID
 Password

12.1.7.6 User-Role Mapping

The system will map the users to their respective roles. Information for this mapping will
be obtained from the database. This database is maintained by the Administrator. Users
will be granted access privileges according to their mapped roles. User-Role Mapping is a
background process.

12.1.7.7 User-Role Access Privileges

The system will provide a user-friendly GUI, accessible only to the Administrator to
grant or revoke access to Functionalities to Roles.

Each functionality will be mapped to one or more roles, as for example:

# Functionality Accessible To Access Right

1 Login
2 Planner Homepage Planners Full
Administrators Full
3 Accounts Homepage Accountants Full
Administrators Full
4 Administrator Homepage Administrator Full
5 Customer Homepage Customer Full
Administrator Full

44
12.1.8 Reporting Module
This module gives reports of all the information from four aspects
 Customer point of view
♦ List of orders cancelled during a period
♦ Payment status during a period
 Administrator point of view
♦ List of registered Customers
♦ List of registered Planners
♦ List of registered Account Users
♦ List of PHs commissioned
♦ List of Trailers commissioned
♦ List of PHs scrapped
♦ List of Trailers scrapped
 Planner point of view
♦ Locationwise customer list
♦ List of breakdown PMs during a period
♦ List of PMs that have been undergone maintenance during a period
♦ List of executed CDAs (customer wise) during a period
♦ List of replanned CDAs during a period
♦ List of orders cancelled (customer wise) during a period
♦ List of pending CDAs as on a particular date
 Accountant point of view ,
♦ Invoice Payment Status (customer wise and date wise)
♦ Customer Credit rating
♦ Invoices generated during a period

45
13 Design Specifications
13.1 Context level / 0- level DFD

Customer

Haulage
User
Management
System

Planner

Administrator

46
 13.2 First Level DFD

CDA Planning,
ROT Modul Billing &
Modul e 3.0 Reporting
e 2.0 4.0

Customer
Admin &
User Master
Maintenanc
e 1.0
Planner

Administrator

47
 13.3 Flow Chart of Haulage Management System

Start

No

Yes Is
Want to
registered
exit
No Yescustomer
E

F
No

Input Yes
Registration Input choice as
information UserID &
for new password
customer Want to
exit
No

Is choice
Yesvalid

Yes

Is choice =
B
administrator

Yes No
Is
Is choice = No choice=
C
Yes Planner Accounta
nt
D
48
A
 A

No Want to
place new
request?

Yes

Enter new
request

Want to Want to
update No cancel
request request
? ?

Yes
Update ROT No Yes

View ROT (order placed)

Calculation for cost of ROT

49
 B CDA generation from job queue
C (every 1-hr)

User role modification Yes

& role assignment Update CDA Want to
update?
No
Enter/update Master
maintenance Info, PM View List of
mgmt ,Trailer mgmt and executed CDA’S
Driver mgmt info
If
Make
Replanned
plan
Yes Yes CDA? No
Is Yes
View details of
planner
Breakdown PM’S,PM’S
?
&Trailers under
maintenance & MM Info View plan
No From database
Assigning CDA’S to PM’S

Assigning trailers to PM’s

View details of
commissioned
trailers, scrapped
trailers & PM’S Yes
from database Update plan Want to
update
No

View plan
R

View bill/invoice
details of all
customers D
View bill details of
particular customer

View payment
View Report

Insertion of bill
details into database Update database when 1

F order is complete (all CDA’s

execution status =DONE)

Stop E 50
 13.4 Entity Relationship Diagram (ERD)

Rests Base
At
UID
Type
Container Passwor
Trailer d
User

Load
Coupl s Maintains
es role And
PMNo d Access
Prime Mover Privilege

Allocat
Nam
es
e
Allocat Phon
es e
Planner Customer Loade
Administrator
d from
Gener
Orders Premises
ates
Addres
s
Plac
Allocat es
es
Has
Driv
es Service Dete
rmin
Customer
e
Driver Premises

Port
ROT
Plans

CDA
Has d

51
52
13.5 Web Page Design Specifications

13.5.1 General Features

Every page subsequent to the login page will have the following items displayed
horizontally at the top of every page
• Name of the user who has logged on
• Role of the user who has logged on
• A logout link
The Menu pertaining to the role of the user

13.5.2 HMS Homepage

Page Id: 01-00 Page Name: APPLICATION HOME PAGE
Style Sheet: Called from:
Screenshot

Functionality
1. This page will be accessible to all interested person.
2. This page will have the following controls :
 A LABEL to display Login.
 A TEXTBOX to capture user id.
 A PASSWORDBOX to capture user’s password.
 A HYPERLINK to help about Forgotten Password.
 A HYPERLINK to Register new User/Customer.
 A HYPERLINK to display the default page about Haulage Company.
 A HYPERLINK to display the Customers’ List.
 A HYPERLINK to display the Financial Background of the Haulage Company.
 A HYPERLINK to display the FAQs.

53
 Remarks

13.5.3 Customer Registration

Page Id: 01-00 Page Name: NEW CUSTOMER REGISTRATION

Style Sheet: Called from: HMS Home Page
Screenshot

Functionality

54
 1. This page will be accessible to all customer visiting the HMS Home Page. This Page will be
opened by a link from the HMS Home Page.
2. This page will have two interface , in the first interface there will be the following controls:
➘ A TEXTBOX to capture name of the customer.
➘ A TEXTBOX to capture ADDRESS1 of the customer.
➘ A TEXTBOX to capture ADDRESS2 of the customer.
➘ A DROPDOWN to select CITY.
➘ A DROPDOWN to select COUNTRY.
➘ A TEXTBOX to capture PIN CODE.
➘ A TEXTBOX to capture FAX No.
➘ A TEXTBOX to capture E-MIL ID.
➘ A TEXTBOX to capture PHONE No.
➘ A TEXTBOX to capture COTACT PERSONS’ NAME.
➘ A TEXTBOX to capture USER ID.
➘ A TEXTBOX to capture CUSTOMER CODE.
➘ A PASSWORD to capture the PASSWORD VALUE.
3. This page will have the following BUTTONS:
➘ Customer Details.
➘ Premise Details.
➘ Submit.
➘ Reset.
4. The second BUTTON is the link to open the second interface from the first
interface and it will be hidden in the second interface. The first BUTTON is
the link move back to the first interface and it will be hidden in the first
interface.
4. The second interface will have the following controls:
➘ A TEXTBOX to capture CUSTOMER PREMISE CODE.
➘ A TEXTBOX to capture CUSTOMER NAME.
➘ A TEXTBOX to capture CUSTOMER ADDRESS1.
➘ A TEXTBOX to capture CUSTOMER ADDRESS2.
➘ A DROPDOWN to select CITY.
➘ A DROPDOWN to select COUNTRY.
➘ A TEXTBOX to capture LOCATION CODE.
➘ A RADIO BUTTON to capture the choice of FULL DAY
WORKING.
➘ A CHECKBOX to capture the choice of NUMBER OF SHIFTS.
➘ Six MASKEDEDITBOX to capture the OPPENNING AND CLOSING TIME of
the three shifts.
5. After submitting information to server a message will come along with three
BUTTONS to navigate to the other pages.
Viz: UPDATE: to update the Customer Registration Information.
BACK: to move back to the HMS Home Page.
ADD MORE PREMISE: to add more premise details of the
Customer.
Remarks

13.5.4 Add New Customer Premises Details

Page Id: 01-00 Page Name: PREMISE DETAILES
Style Sheet: Called from: CUSTOMER REGISTRATION AND
CUSTOMER HOME PAGE

55
Screenshot

56
 Functionality:

1. This page will be accessible to Customers to add Premises Master Information.

2.This page will have the following controls :

 A LABEL for displaying Premise Code.

 Premise Code will be auto generated by the system and displayed in a
TEXTBOX.
 A LABEL for displaying Premise Name.
 A TEXTBOX for capturing Premise Name.
 A LABEL for displaying Premise Address.
 A LABEL for displaying Address1
 A TEXTBOX for capturing Address1
 A LABEL for displaying Address2
 A TEXTBOX for capturing Address2
 A LABEL for displaying City
 A DROP-DOWN for selecting City
 A LABEL for displaying Country
 A DROP-DOWN for selecting Country.
 A LABEL for displaying Location Code of the Premise.
 A Drop-Down for capturing Location Code of the Premise.
 A LABEL for displaying Premise Type.
 A DROP-DOWN for selecting Premise Type.
 A LABEL for displaying Number of Shifts.
 A TEXTBOX for capturing Number of Shifts.
 A LABEL for displaying First Shift Opening Time.
 A TEXTBOX for capturing First Shift Opening Time.
 A LABEL for displaying First Shift Closing Time.
 A TEXTBOX for capturing First Shift Closing Time.
 A LABEL for displaying Second Shift Opening Time.
 A TEXTBOX for capturing Second Shift Opening Time.
 A LABEL for displaying Second Shift Closing Time.
 A TEXTBOX for capturing Second Shift Closing Time.
 A LABEL for displaying Third Shift Opening Time.
 A TEXTBOX for capturing Third Shift Opening Time
 A LABEL for displaying Third Shift Closing Time.
 A TEXTBOX for capturing Third Shift Closing Time

3. The entries in Drop-down for City will be corresponding to the entries in Drop-
Down for
Country.

44. The Location Code will correspond to only existing Locations in Location
Master.

57
 5. Premises type Drop-down will contain entries as:
 Base
 Depot
 Interchange
 Customer Premises

a. 6. Number of shifts can be minimum of 1 and maximum of 3.

7. First Shift Closing Time is mandatory and should be after First Shift Opening
Time.

8. Second and Third Shift Opening Time and Closing Time are optional
depending on
Number of shifts.

9.Third Shift Opening Time should be considered only after Second Shift
Opening Time is
specified.

10.Second Shift Closing Time should be after Second Shift Opening Time.

11.Third Shift Closing Time should be after Third Shift Opening Time.

12.All mandatory fields will be marked by an asterik “ * ”.

Remarks

58
13.5.5 Administrator Homepage
Page Id: 02-00 Page Name: Administrator Homepage

Style Sheet: Called from: Application Home Page

Screenshot

Functionality

59
 1. This page will be accessible to Administrator.
2. This page will have the following controls :
• A TEXTBOX to display Currently Logged User’s Id which will be disabled.
• A HYPERLINK to display the Administrator Homepage.
• A HYPERLINK to display the Planner Home Page.
• A HYPERLINK to display the Accounts Home Page.
• A HYPERLINK to display the Administrators related FAQs.
• A HYPERLINK to Logout.
• A HYPERLINK to maintain Internal User’s Data(UID & Password).
• A HYPERLINK to enter Access Privileges to the Internal User.
• A BUTTON“Master Maintenance” with the following Masters:
o A HYPERLINK to access Prime Mover Master.
o A HYPERLINK to access Trailer Master.
o A HYPERLINK to access Location Master
o A HYPERLINK to access Premises Master.
o A HYPERLINK to access Parameter Master
o A HYPERLINK to access Port Master.
o A HYPERLINK to access Driver Master.

o A HYPERLINK to access Distance Metrics Master.

o A HYPERLINK to access Maintenance Master.
• A BUTTON “Prime Mover Management “ with the following modules:
o A HYPERLINK to access Prime Mover Availability
o A HYPERLINK to access Prime Mover Maintenance Scheduling
• A BUTTON “Trailer Management “ with the following modules:
o A HYPERLINK to access Trailer Availability
o A HYPERLINK to access Trailer Maintenance Scheduling
o A HYPERLINK to access Trailer Location Monitoring
o A HYPERLINK to access Empty Trailer Collection
• A HYPERLINK to access Driver Management
2. A BUTTON to access “ Administrative Reports” with the following modules:
o A HYPERLINK to access Customer List
o A HYPERLINK to access Internal User List.
o A HYPERLINK to access Commissioned Prime Mover.
o A HYPERLINK to access Commissioned Trailer.
o A HYPERLINK to access Scrapped Prime Mover.
o A HYPERLINK to access Scrapped Trailer.

Remarks
1.

60
13.5.6 Planner Homepage
Page Id: 03-00 Page Name: Planner Homepage

Style Sheet: Called from: Application Home Page

Screenshot

Functionality

61
 1. This page will be accessible to Planners & Administrators.
2. This page will have the following controls :
• A TEXTBOX to display Currently Logged User’s Id which will be disabled.
• A HYPERLINK to display Application Home Page.
• A HYPERLINK to display Planner Home Page.
• A HYPERLINK to display the Accounts Home Page.
• A HYPERLINK to display the Planner related FAQs.
• A HYPERLINK to Logout.
• A BUTTON “Plannning” with the following hyperlinks:
o A HYPERLINK to Make Plan
o A HYPERLINK to View Plan
o A HYPERLINK to Update Plan
o A HYPERLINK to Cancel Plan
• A BUTTON “CDAs To Be Planned” with the following hyperlinks:
o A HYPERLINK to Make Plan.
o A HYPERLINK to View Plan.
o A HYPERLINK to Update Plan.
o A HYPERLINK to Cancel Plan.
• A BUTTON “Other Information” with the following hyperlinks:
o A HYPERLINK to access Prime Mover Availability.
o A HYPERLINK to access Trailer Availability
o A HYPERLINK to access Parameter View.
• A BUTTON “Reports” with the following hyperlinks:
o A HYPERLINK to access Loocatoinwise Customer.
o A HYPERLINK to access Breakdown P.M.
o A HYPERLINK to access P.M. Maintenance.
o A HYPERLINK to access Executed CDAs.
o A HYPERLINK to access Replanned CDAs.
o A HYPERLINK to accessCancelled Order.
o A HYPERLINK to access Pending CDAs.
Remarks
1.

13.5.7 Accounts Homepage

Page Id: 04-00 Page Name: Accounts Homepage

Style Sheet: Called from: Application Home Page

62
Screenshot

Functionality
• This page will be accessible to the Accountants & Administrators.
• This page will have the following controls :
• A TEXTBOX to display Currently Logged User’s Id which will be disabled.
• A HYPERLINK to display Application Home Page.
• A HYPERLINK to display Planner Home Page.
• A HYPERLINK to display the Planner related FAQs.
• A HYPERLINK to Logout.
• A BUTTON “View Invoice” with the following hyperlinks:
o A HYPERLINK to access Customer wise Invoice.
• A BUTTON “ROT Wise” with the following hyperlinks:
o A HYPERLINK to access Order Wise
o A HYPERLINK to access Date Wise.
• A BUTTON to access Payment History.
• A BUTTON “Report “with the following hyperlinks:
o A HYPERLINK to access Payment Status.
o A HYPERLINK to access Generated Invoice.
Remarks
1.

63
13.5.8 Customer Homepage
Page Id: 05-00 Page Name: Customer Homepage

Style Sheet: Called from: Application Home Page

Screenshot

Functionality
1. This page will be accessible to Customers & Administrators.
2. This page will have the following controls :
• A LABEL to display Currently Logged User’s Id.
• A HYPERLINK to display Application Home Page.
• A HYPERLINK to display Customer Home Page.
• A HYPERLINK to display the Customers related FAQs.
• A HYPERLINK to Logout.
• A BUTTON to enter data about ROT:
o A HYPERLINK to enter New Request Entry.
o A HYPERLINK to Update Request.
o A HYPERLINK to Cancel Request.
• A BUTTON to display Order Status:
o A HYPERLINK to display Pending Orders.
o A HYPERLINK to display Cancelled Orders.
• A BUTTON to display Billing:
o A HYPERLINK to display Date wise Billings.
o A HYPERLINK to display Requst/Orderwise Billings.
• A BUTTON to display Reports with the following hyperlinks:
o A HYPERLINK to display Cancel Order.
o A HYPERLINK to display Request Status.
o A HYPERLINK to display Payment Status.

Remarks
1.

13.5.9 Maintain Users

Page Id: 06-00 Page Name:

Style Sheet: Called from:

64
 Screenshot

Functionality
1. This page will be accessible to Administrator to capture Employee Master Data into the
system.
2. This page will have the following controls :
a. A TEXTBOX to capture Employee Code,which is unique.
b. A TEXTBOX to capture Employee Name.
c. A TEXTBOX to capture Employee Designation.
d. A TEXTBOX to capture User Id.
e. BUTTONS
o BACK.
o SUBMIT.
o CANCEL.
o RESET.
o MORE ENTRY.
 Administrator can enter information about more than one Employee at a time by
clicking the “MORE ENTRY “ button after each entry and finally can submit all
the entries.

Remarks
1.

13.5.10 Maintain User Role Mapping

Page Id: 07-00 Page Name:

Style Sheet: Called from:

65
 Screenshot

Functionality
1. This page will be accessible to Administrator to map Functionalities with
different Roles.
2. When there is no User(Employee) and this page is launched, the page will
display a message “No Users exist. Please enter Username before
mapping”.
3. This page will have the following controles:
• A DROPDOWN – This will contain a list of all Username, from where
Administrator can select one Username.
• TWO DROPDOWN – This will contain the Role Id, from where
Administrator can select one for each User. Some User may have more
than one Role , for that reason there exist two Dropdown.
• BUTTONS
o SUBMIT
o CANCEL
o RESET
o ADD NEW
• Administrator can enter information about more than one
Employee at a time by clicking the “ADD NEW “ button
after each entry and finally can submit all the entries.

Remarks
1.

13.5.11 Map Role/Page Access

Page Id: 09-00 Page Name: Functionality-Role Mapping

Style Called from: 00-00

Sheet:
Screenshot

Functionality
1. This page will be accessible to Administrator to map Page Access

66
 with different Roles.
2. When there is no Role defined and this page is launched, the page
will display a message “No Roles exist. Please enter Roles before
mapping”
3. There will be a DROPDOWWN from where Administrator can
select a Role.
4. When Roles are duly defined in the system and this page is
launched, the following controls will be available in the page:
• There will be two LISTBOX headed by “NOT
AVAILABLE” and “AVAILABLE” containing
respective page names applicable to the
specified Role.
• A SUBMIT BUTTON
• A CANCEL BUTTON

1. By default, Administrator will have access to all Pages and Reports

2. Administrator will be able to Grant or Revoke access to
Pages/Reports to other Roles using the specified BUTTONS
provided.
3. All updated data will be submitted to the database when the
SUBMIT BUTTON is pressed.
4. Pressing on the CANCEL BUTTON will reset all unsaved
information.

Remarks

13.5.12 Maintain Prime-Movers

13.2.12.1 View Prime-Movers

Page Id: 09-00 Page Name: View Prime Mover

Style Sheet: Called from:

67
 Screenshot:

Functionality:

1.This page will be accessible to Administrator to view Prime-Mover Master Information.

2.This page will have the following controls :

 A table to view all the field names in the header and the information of
each record in a separate row.
 Each row will contain:
 A checkbox to select a particular Prime-Mover record.
 Columns for displaying information of Prime-Mover no,
Regn.No.,Regn.Year, Manufacturer’s Name , Model, Engine
No.,ChassisNo.,Purchase Price ,Purchase Date, Kms traveled before Purchase
Date,Date of commissioning, Kms traveled before Commissioning Date,
Wheteher decommissioned or not, Date of decommissioning , Kms traveled till
Decommissioning Date, Wheteher scrapped or not, Date of scrap, Scrap Value
and Weight.
 A button for going back to the previous page (update or addnew page).
 A button for adding a new record .
 A button for deleting one or more records.
 A button for updating a single record at a time.

3. Both update and delete buttons get disabled when more than no record is selected.

4. The update button get disabled when more than 1 record is selected.

68
13.2.12.2 Add Prime-Movers

Page Id: 09-00 Page Name: Add Prime Mover

Style Sheet: Called from:

69
Screenshot

70
Functionality

1. This page will be accessible to Administrators to view Prime Mover Master

Information.
2. This page will have the following controls :

 Prime Mover Number will be auto-generated by the system and displayed to

the user.
 A LABEL to display Vehicle Registration Number.
 A TEXTBOX to enter Vehicle Registration Number.
 A LABEL to display Year of Vehicle Registration.
 A TEXTBOX to enter Year of Vehicle Registration.
 A LABEL to display Manufacturer Name.
 A DROPDOWN to select the Manufacturer Name. This DROPDOWN will
contain the values like:
 Volvo
 DCM Toyota
 A LABEL to display Vehicle Model.
 A TEXTBOX to capture Vehicle Model.
 A LABEL to display Engine Number.
 A TEXTBOX to capture Engine Number.
 A LABEL to display Chassis Number .
 A TEXTBOX to enter the Chassis Number .
 A LABEL to display Purchase Price .
 A TEXTBOX to capture Purchase Price .
 A LABEL to display Date of Purchase.
 Date of Purchase will be captured in a text-box clicking on which will allow
the user to select date from a Calendar.
 A LABEL to display Kilometers traveled at Purchase Date.
 A TEXTBOX to capture Kilometers traveled at Purchase Date.
 A LABEL to display Date of Commissioning.
 Date of Commissioning will be captured in a text-box clicking on which
will allow the user to select date from a Calendar.
 A LABEL to display Kilometers traveled at Date of Commissioning.
 A TEXTBOX to capture Kilometers traveled at Date of Commissioning.
 A LABEL to display Prime-Mover Decommissioned.
 A CHECKBOX to be checked if the prime-mover has been
decommissioned.
 A LABEL to display Date of Decommissioning.
 Date of Decommissioning will be captured in a text-box clicking on which
will allow the user to select date from a Calendar.
 A LABEL to display Kilometers traveled at Date of Decommissioning.
 A TEXTBOX to capture Kilometers traveled at Date of Decommissioning.
 A LABEL to display Prime-Mover Scrapped.
 A CHECKBOX to be checked if the prime-mover has been scrapped.
 A LABEL to display Date of Scrap
71
  A LABEL to display Scrap Value .
 A TEXTBOX to capture Scrap Value .
 A LABEL to display Weight.
 A TEXTBOX to capture Weight.

 A BUTTON to submit all the added records at a time.

 A BUTTON to cancel the form .
 A BUTTON to reset the form.
 A BUTTON to add a new record.

3. No two Prime Movers can have the same Prime-mover number or Regn. number.
4. No two Prime Movers can have the same Engine number.
5. Chassis number for a Prime Mover will be unique.
6. The Purchase price cannot be negative.
7. Date of Commissioning will be allowed to be entered only after the Date of
Purchase.
8. Date of Decommissioning will be allowed to be entered only if the
decommissioned box is checked.
9. Date of Scrap will be allowed to be entered only if the scrapped box is checked.
10. Date of Scrap should be allowed to be entered only after the Date of
Decommissioning
11. Scrap Value cannot be negative and will be allowed to be entered only if scrapped
checkbox is checked.
12. All the mandatory fields are marked with “ * “ .

72
13.2.13 Maintain Trailers

13.1 View Trailers

Page Id: 12-00 Page Name: View Trailer
Style Sheet: Called from:
Screenshot

73
Functionality:

1.This page will be accessible to Administrators to view Trailer Master Information.

2.This page will have the following controls :

 A table to view all the field names in the header and the information of
each record in a separate row.
 Each row will contain:
 A checkbox to select a particular trailer record.
 Columns for displaying information of Trailer No, Trailer Size, Manufacturer’s name,
Purchase price , Purchase date, Date of commissioning , Whether decommissioned or
not, Date of decommissioning , Whether scrapped or not, Date of scrap, Scrap value,
Weight and Side-Loader.
 A button for going back to the previous page (update or addnew page).
 A button for adding a new record .
 A button for deleting one or more records.
 A button for updating a single record at a time.

3.Both update and delete buttons get disabled when more than no record is selected.

4.The update button get disabled when more than 1 record is selected.

74
13.2.14 Add Trailers

Page Id: 12-00 Page Name: Add Trailers

Style Sheet: Called from:
Screenshot

75
Functionality

1.This page will be accessible to Administrators to maintain Trailer Master Information.

2.This page will have the following controls :

 A LABEL to display Trailer Number.

 Trailer Number will be autogenerated and displayed .
 A LABEL to display Trailer Size.
 Two RADIO buttons to select Trailer Size - 20’ or 40’.
 A LABEL to display Manufacturer’s Name.
 A DROPDOWN to select the Manufacturer Name.
 A LABEL to display Purchase Price.
 A TEXTBOX to capture Purchase Price.
 A LABEL to display Date of Purchase.
 Date of Purchase will be captured in a text-box clicking on which will
allow the user to select date from a Calendar.
 A LABEL to display Date of Commissioning.
 Date of Commissioning will be captured in a text-box clicking on which
will allow the user to select date from a Calendar.
 A LABEL to display Trailer Decommissioned?
 A CHECKBOX which should be checked for trailer which has been
decommissioned.
 A LABEL to display Date of Decommissioning.
 Date of Decommissioning will be captured in a text-box clicking on which
will allow the user to select date from a Calendar.
 A LABEL to display Trailer Scrapped?
 A CHECKBOX which should be checked for trailer which has been
scrapped.
 A LABEL to display Date of Scrap .
 Date of Scrap will be captured in a text-box clicking on which will allow
the user to select date from a Calendar.
 A LABEL to display Scrap Value .
 A TEXTBOX to capture Scrap Value .
 A LABEL to display Weight.
 A TEXTBOX to capture Weight.
 A LABEL to display Side-Loader .
 A CHECKBOX indicating presence or absence of Side-Loader ,checked if
present.
 A BUTTON to submit all the added records at a time.
 A BUTTON to cancel the form .
 A BUTTON to reset the form.
 A BUTTON to add a new record.

3. No two Trailers can have the same number.

4. The Purchase price cannot be negative.

76
 6. Date of Decommissioning will be allowed to be entered only if the
decommissioned box is checked and must be after Date of Commissioning.

7. Date of Scrap will be allowed to be entered only if the scrapped box is checked and
must be afterDate of Scrap must be after the Date of Decommissioning.

8. Scrap Value cannot be negative.

9. All the mandatory fields are marked with “ * “ .

Remarks

13.2.15 Maintain Locations

13.2.15.1 View Locations

Page Id: 13-00 Page Name: Location Master Maintenance

Style Sheet: Called from:
Screenshot :

77
Functionality:

1.This page will be accessible to Administrators to view Location Master

Information.

2.This page will have the following controls :

 A table to view all the field names in the header and the
information of each record in a separate row.
 Each row will contain the following information :
 A checkbox to select a particular location record.
 Location code, Location name, Standard time, Latitude - Direction,
degree,minutes,seconds, Longitude - Direction,
degree,minutes,seconds, Local X coordinate, Local Y coordinate,
Local or Outstation.
 A button for going back to the previous page (update or add-
new page).
 A button for adding a new record.
 A button for deleting one or more records.
 A button for updating a single record at a time.

3.Both update and delete buttons get disabled when more than no record is
selected.

4.The update button get disabled when more than 1 record is selected.

78
13.2.15.2 Add Locations

79
Page Id: 13-00 Page Name: Location Master Maintenance
Style Sheet: Called from:
Screenshot

80
Functionality

1.This page will be accessible to Administrators to maintain Location Master

Information.

2.This page will have the following controls :

 A LABEL for displaying Location Code.

 Location Code will be autogenerated and displayed.
 A LABEL for displaying Location Name.
 A TEXTBOX for capturing Location Name.
 A LABEL for displaying Standard Time.
 A DATE-TIME PICKER for capturing Standard Time.
 A LABEL for displaying Latitude.
 A LABEL for displaying Direction.
 Two LABEL s for displaying North and South.
 Two RADIO Buttons for capturing the direction - North/South.
 A LABEL for displaying Degree.
 A DROPDOWN for capturing Degree.
 A LABEL for displaying Minutes.
 A DROPDOWN for capturing Minutes.
 A LABEL for displaying Seconds.
 A DROPDOWN for capturing Seconds.
 A LABEL for displaying Longitude.
 A LABEL for displaying Direction.
 Two LABEL s for displaying East and West.
 Two RADIO Buttons for capturing the direction – East/West.
 A LABEL for displaying Degree.
 A DROPDOWN for capturing Degree.
 A LABEL for displaying Minutes.
 A DROPDOWN for capturing Minutes.
 A LABEL for displaying Seconds.
 A DROPDOWN for capturing Seconds.
 A LABEL for displaying Local X Coordinate.
 A TEXTBOX for capturing Local X Coordinate.
 A LABEL for displaying Local Y Coordinate.
 A TEXTBOX for capturing Local Y Coordinate.
 A LABEL for displaying Local or Outstation.
 A CHECKBOX for finding Local or Outstation , checked for Local and
unchecked for outstation.
 A BUTTON to submit all the added records at a time.
 A BUTTON to cancel the form .
 A BUTTON to reset the form.
 A BUTTON to add a new record.

3. Location codes will be unique.

81
 Remarks

13.2.16 Maintain Ports

13.2.16.1 View Ports

Page Id: 15-00 Page Name: Port Master Maintenance

Style Sheet: Called from:
Screenshot :

82
Functionality:

1.This page will be accessible to Administrators to view Port Master Information.

2.This page will have the following controls :

 A Table to view all the field names in the header and the information of
each record in a separate row.
 Each row will contain the following information:
 A checkbox to select a particular port record.
 Port code, Port name, Port Address, Location of port, Import opening time,
Import closing time ,Export opening time, Export closing time for each Normal,
Dangerous & Refrigerated Cargos and Export shut time.
 A button for going back to the previous page (update or add-new page).
 A button for adding a new record.
 A button for deleting one or more records.
 A button for updating a single record at a time.

3.Both update and delete buttons get disabled when more than no record is selected.

4.The update button get disabled when more than 1 record is selected.

83
13.2.16.2 Add Ports

Page Id: 15-00 Page Name: Port Master Maintenance

Style Sheet: Called from:
Screenshot :

84
Functionality:

1. This page will be accessible to Administrators to maintain Port Master

Information.

2. This page will have the following controls :

 A LABEL for displaying Port Code .

 Port Code will be autogenerated and displayed.
 A LABEL for displaying Port Name .
 A TEXTBOX for capturing Port Name .
 A LABEL for displaying Port Address.
 A LABEL for displaying Address1.
 A TEXTBOX for capturing Address1.
 A LABEL for displaying Address2.
 A TEXTBOX for capturing Address2.
 A LABEL for displaying City.
 A DROP-DOWN for selecting City.
 A LABEL for displaying Country.
 A DROP-DOWN for selecting Country.
 A LABEL for displaying Location Code of the Port.
 A DROP-DOWN for capturing Location Code of the Port.
 A LABEL for displaying Import Opening Time for Dangerous
Cargo .
 A DATE-TIME PICKER for capturing Import Opening Time for
Dangerous Cargo .
 A LABEL for displaying Import Opening Time for Normal Cargo .
 A DATE-TIME PICKER for capturing Import Opening Time for
Normal Cargo .
 A LABEL for displaying Import Opening Time for Refrigerated
Cargo .
 A DATE-TIME PICKER for capturing Import Opening Time for
Refrigerated Cargo .
 A LABEL for displaying Import Closing Time for Dangerous Cargo .
 A DATE-TIME PICKER for capturing Import Closing Time for
Dangerous Cargo .
 A LABEL for displaying Import Closing Time for Normal Cargo .
 A DATE-TIME PICKER for capturing Import Closing Time for
Normal Cargo .
 A LABEL for displaying Import Closing Time for Refrigerated Cargo
.
 A DATE-TIME PICKER for capturing Import Closing Time for
Refrigerated Cargo .
 A LABEL for displaying Export Opening Time for Dangerous Cargo.
 A DATE-TIME PICKER for capturing Export Opening Time for
Dangerous Cargo.

85
  A LABEL for displaying Export Closing Time for Normal Cargo .
 A DATE-TIME PICKER for capturing Export Closing Time for Normal
Cargo .
 A LABEL for displaying Export Closing Time for Refrigerated Cargo
.
 A DATE-TIME PICKER for capturing Export Closing Time for
Refrigerated Cargo .
 A LABEL for displaying Export Shut Time.
 A DATE-TIME PICKER for capturing Export Shut Time.
 A BUTTON to submit all the added records at a time.
 A BUTTON to cancel the form .
 A BUTTON to reset the form.
 A BUTTON to add a new record.

3. Port Code along with Location code will be unique.

4. The Location Name will correspond to only existing Locations in Location

Master.

5. The entries in Drop-down for City will be corresponding to the entries in

Drop-Down
for Country.

6. All the mandatory fields are marked with “ * “.

Remarks :
1.

86
13.2.17 Maintain Drivers

13.17.2.1 View Drivers

Page Id: 10-00 Page Name: View Driver Master Maintenance

Style Sheet: Called from:
Screenshot

87
Functionality:

1.This page will be accessible to Administrators to view Driver Master

Information.
2.This page will have the following controls :

 A table to view all the field names in the header and the
information of each record in a separate row.
 Each row will contain:
 A checkbox to select a particular driver record.
 Columns for displaying Driver Code, Driver name, Age ,Address, Phone
no., Mobile no, Passport No, Joining Date, License no, License validity
date, Accident record and Basic wages.
 A button for going back to the previous page (update or addnew
page).
 A button for adding a new record .
 A button for deleting one or more records.
 A button for updating a single record at a time.

3.Both update and delete buttons get disabled when more than no record is
selected.

4.The update button get disabled when more than 1 record is selected.

Remarks

88
6.2.14.2 Add Drivers

Page Id: 10-00 Page Name: Driver Master Maintenance

Style Sheet: Called from:
Screenshot

89
Functionality

1.This page will be accessible to Administrators to maintain Driver Master Information.

2.This page will have the following controls :

 A LABEL to display Driver Code.

 Driver Code will be auto-generated by the system and displayed to the user .
 A LABEL to display Driver Name.
 A TEXTBOX to capture Driver Name.
 A LABEL to display Driver Age.
 A TEXTBOX to capture Driver Age.
 A LABEL to display Driver Address.
 A LABEL for displaying Driver Address.
 A LABEL for displaying Address1
 A TEXTBOX for capturing Address1
 A LABEL for displaying Address2
 A TEXTBOX for capturing Address2
 A LABEL for displaying City
 A DROP-DOWN for selecting City
 A LABEL for displaying Country
 A DROP-DOWN for selecting Country.
 A LABEL to display Driver Phone Number.
 A TEXTBOX to capture Driver Phone Number.
 A LABEL to display Driver Mobile Number.
 A TEXTBOX to capture Driver Mobile Number
 A LABEL to display Driver Passport Number.
 A TEXTBOX to capture Driver Passport Number.
 A LABEL to display Driver License Number.
 A TEXTBOX to capture Driver License Number.
 A LABEL to display Driver License Validity Date.
 License Validity Date will be captured in a TEXT-BOX clicking on which
will allow the user to select date from a Calendar.
 A LABEL to display Date of Joining.
 Date of Joining will be captured in a TEXT-BOX clicking on which will
allow the user to select date from a Calendar.
 A LABEL to display Accident Record.
 A DROPDOWN to capture Accident Record.
The dropdown will have following values:
 Good
 Bad
 Average
 Best
 A LABEL to display Driver Basic Wage.
 A TEXTBOX to capture Driver Basic Wage.

90
 3. Driver Code should be unique.

4. Driver Basic Wages cannot be negative.

5. A Driver is allotted not more than one license.

6. The license has a validity period, ie, license validity date should exceed
Date of joining.

7. The entries in Drop-down for City will be corresponding to the entries in

Drop-Down for Country.

8. All the mandatory fields are marked with “ * “.

Remarks

91
13.2.18 Maintain Premises

13.18.2.1 View Premises

Functionality:

1.This page will be accessible to Administrators to view Premises Master Information.

2.This page will have the following controls :

 A table to view all field names in the header and the information of each record in a
separate row.
 Each row will contain the following information :
 A checkbox to select a particular premises record.
 Premise code, premise name, Address, Premise type, No of shifts which was
selected,
opening time, closing time, loading time, unloading time, coupling time,
decoupling time.

 A button for going back to the previous page (update or add-new page).
 A button for adding a new record.
 A button for deleting one or more records.
 A button for updating a single record at a time.

3.Both update and delete buttons get disabled when more than no record is selected.

4.The update button get disabled when more than 1 record is selected.

6.2.15.2 ADD PREMISES

Page Id: 14-00 Page Name: Premises Master Maintenance

Style Sheet: Called from:

92
Screenshot

93
 Functionality:

1.This page will be accessible to Administrators to maintain Premises Master

Information.

2.This page will have the following controls :

 A LABEL for displaying Premise Code.

 Premise Code will be autogenerated by the system and displayed in a
TEXTBOX.
 A LABEL for displaying Premise Name.
 A TEXTBOX for capturing Premise Name.
 A LABEL for displaying Premise Address .
 A LABEL for displaying Address1
 A TEXTBOX for capturing Address1
 A LABEL for displaying Address2
 A TEXTBOX for capturing Address2
 A LABEL for displaying City
 A DROP-DOWN for selecting City
 A LABEL for displaying Country
 A DROP-DOWN for selecting Country.
 A LABEL for displaying Location Code of the Premise.
 A Drop-Down for capturing Location Code of the Premise.
 A LABEL for displaying Premise Type.
 A DROP-DOWN for selecting Premise Type.
 A LABEL for displaying Number of Shifts.
 A TEXTBOX for capturing Number of Shifts.
 A LABEL for displaying First Shift Opening Time.
 A TEXTBOX for capturing First Shift Opening Time.
 A LABEL for displaying First Shift Closing Time.
 A TEXTBOX for capturing First Shift Closing Time.
 A LABEL for displaying Second Shift Opening Time.
 A TEXTBOX for capturing Second Shift Opening Time.
 A LABEL for displaying Second Shift Closing Time.
 A TEXTBOX for capturing Second Shift Closing Time.
 A LABEL for displaying Third Shift Opening Time.
 A TEXTBOX for capturing Third Shift Opening Time
 A LABEL for displaying Third Shift Closing Time.
 A TEXTBOX for capturing Third Shift Closing Time

3. The entries in Drop-down for City will be corresponding to the entries in Drop-
Down for
Country.

4 4. The Location Code will correspond to only existing Locations in Location

Master.

94
 5. Premises type Drop-down will contain entries as:
 Base
 Depot
 Interchange
 Customer Premises

b. 6. Number of shifts can be minimum of 1 and maximum of 3.

7. First Shift Closing Time is mandatory and should be after First Shift Opening
Time .

8. Second and Third Shift Opening Time and Closing Time are optional
depending on
Number of shifts.

9.Third Shift Opening Time should be considered only after Second Shift
Opening Time is
specified.

10.Second Shift Closing Time should be after Second Shift Opening Time.

11.Third Shift Closing Time should be after Third Shift Opening Time.

12.All mandatory fields will be marked by an asterik “ * ”.

Remarks

95
13.2.19 Maintain Services

13.19.2.1 View Services

Functionality:

1.This page will be accessible to Administrators to view Service Master Information.

2.This page will have the following controls :

 A table to view all the field names in the header and the information of each record in a
separate row.
 Each row will contain the following information :
 A checkbox to select a particular premises record.
 Service rate code, service type, rate of service ,unit of measurement(uom).
 A button for going back to the previous page (update or add-new page).
 A button for adding a new record.
 A button for deleting one or more records.
 A button for updating a single record at a time.

3.Both update and delete buttons get disabled when more than no record is selected.

4.The update button get disabled when more than 1 record is selected.

96
6.2.16.2 ADD SERVICES

Page Id: 16-00 Page Name: Service Master Maintenance

Style Sheet: Called from:
Screenshot:

97
 Functionality:

1. This page will be accessible to Administrators to maintain Service Master

Information.
2. This page will have the following controls :

 A LABEL for displaying Service Rate Code.

 Service Rate Code will be autogenerated and displayed.
 A LABEL for displaying Service Type .
 A DROP-DOWN for selecting Service Type containing :
 Direct Delivery
 Direct Collection
 Direct delivery/Direct Collection
 Direct Collection/Direct Delivery
 Staging Delivery /Staged Delivery
 Staging Collection /Staged Collection
 Direct delivery/Staging Collection + Staged Collection
 Direct Collection/Staging Delivery+ Staged Delivery
 Staging Delivery + Staged Delivery/Staging Collection + Staged
Collection
 Staging Collection + Staged Collection/Staging Delivery+ Staged
Delivery
 Empty Trailer Collection
 A LABEL for displaying Rate Of Service.
 A TEXTBOX for capturing Rate Of Service.
 A LABEL for displaying Unit Of Measurement.
 A DROP-DOWN for selecting Unit Of Measurement.
Unit of measurement will be:
 Km
 Hours

3. No two Services will have the same code.

4. Rate Of Service cannot be negative.

5. The Rate depends on the service provided.

6. Billing is done according to these parameters.

7. All the mandatory fields are marked with “ * “ .

Remarks

98
13.2.20 Maintain Parameters

13.20.2.1 View Parameters

Functionality:

1.This page will be accessible to Administrators to view Parameters Master Information.

2.This page will have the following controls :

 A table to view all field names in the header and the information of each record in a
separate row.
 Each row will contain the following information :
 A checkbox to select a particular parameter record.
 Parameter code, Parameter name, Value1, Value2, Unit of Measurement.

 A button for going back to the previous page (update or add-new page).
 A button for adding a new record.
 A button for deleting one or more records.
 A button for updating a single record at a time.

3.Both update and delete buttons get disabled when more than no record is selected.

4.The update button get disabled when more than 1 record is selected.

99
6.2.17.2 ADD PARAMETERS

Page Id: Page Name: Parameter Master Maintenance

Style Sheet: Called from:
Screenshot

100
Functionality:

1. This page will be accessible to Administrators to maintain Parameter Master

Information.

2. This page will have the following controls :

 A LABEL for displaying Parameter Code.

 A TEXTBOX for displaying autogenerated Parameter Code.
 A LABEL for displaying Parameter Name.
 A TEXTBOX for capturing Parameter Name.
 A LABEL for displaying Value1 of Parameter.
 A TEXTBOX for capturing Value1 of Parameter.
 A LABEL for displaying Value2 of Parameter.
 A TEXTBOX for capturing Value2 of Parameter.
 A LABEL for displaying UOM .
 A DROPDOWN for capturing UOM .
Unit of measurement will be:
 Km/Hour
 Hours
2. Parameter codes will be unique.

3. Value1 is mandatory and Value2 is optional.

4. All the mandatory fields are marked with “ * “ .

Remarks:

101
13.2.21 Maintain Distance Matrix

13.21.2.1 View Distance Matrix

Functionality:

1.This page will be accessible to Administrators to view Distance Matrix Master

Information.

2.This page will have the following controls :

 A table to view all field names in the header and the information of each record in a
separate row.
 Each row will contain the following information :
 A checkbox to select a particular parameter record.
 From Premise, To Premise, Distance,Time.
 A button for going back to the previous page (update or add-new page).
 A button for adding a new record.
 A button for deleting one or more records.
 A button for updating a single record at a time.

3.Both update and delete buttons get disabled when more than no record is selected.

4.The update button get disabled when more than 1 record is selected.

102
13.21.1.2 Add Distance Matrix
Page Id: Page Name: Distance Matrix Maintenance
Style Sheet: Called from:
Screenshot

103
Functionality:

1. This page will be accessible to Administrators to maintain Distance Matrix

Master
Information.

2. This page will have the following controls :

 A LABEL for displaying From Premise .

 A DROPDOWN for capturing From Premise.
 A LABEL for displaying To Premise.
 A DROPDOWN for capturing To Premise.
 A LABEL for displaying Distance.
 A TEXTBOX for capturing Distance.
 A LABEL for displaying Time.
 A TEXTBOX for capturing Time.

3. From Premise and to Premise together will be unique.

4. The Time taken will be calculated based on the Distance between the two
premises entered by user and the average speed of Prime-Mover.

5. All the mandatory fields are marked with “ * “ .

Remarks:

104
13.2.22 Maintain Prime Movers Availability
Page Id: 18-00 Page Name: Prime Mover Availability
Information
Style Sheet: Called from:
Screenshot

Functionality
1. This page will be accessible to Administrators and Planners to maintain
Prime Mover Availability Information.
2. This page will have the following controls

 The Serial Number is auto-generated

 Prime Mover Number will be auto-generated by the system and displayed to
the user.
 A CHECKBOX to enter Availability in first Shift
 A CHECKBOX to enter Availability in second Shift
 A CHECKBOX to enter Availability in third Shift
 The Reason Of Unavailability is displayed automatically by taking the
information form
the prime mover Maintenance database
 A COMMAND BUTTON to clear the input text on the form
 A COMMAND BUTTON to update the database information
Remarks
5.

105
13.2.23 Maintain Prime Movers Maintenance
Page Id: 19-00 Page Name: Prime Mover Maintenance
Information
Style Sheet: Called from:
Screenshot

Functionality

106
 1. This page will be accessible to Administrators and Planners to maintain
Prime Mover Maintenance Information.
2. This page will have the following controls

 The Serial Number is auto-generated

 Prime Mover Number will be auto-generated by the system and displayed to
the user.
 A LISTBOX to select the type of maintenance. The LISTBOX will
have the following values
o Routine Maintenance
o Breakdown Maintenance
o Change Of Tuyeres
 A TEXTBOX to enter the date from which the prime mover is under
Maintenance
 The date upto which the prime moverr will be under Maintenance is auto
generated depending on the number of days taken by the Maintenance to complete
 A COMMAND BUTTON to clear the input text on the form
 A COMMAND BUTTON to update the database information
Remarks
1.

13.2.24 Maintain Driver Availability

Page Id: 20-00 Page Name: Driver Availability
Information
Style Sheet: Called from:

107
 Screenshot

Functionality
1. This page will be accessible to Administrators and Planners to maintain
Driver Availability Information.

2. This page will have the following controls

 The Serial Number is auto-generated

 Driver Code will be auto-generated by the system and displayed to the
user.
 A CHECKBOX to enter Availability in first Shift
 A CHECKBOX to enter Availability in second Shift
 A CHECKBOX to enter Availability in third Shift
 The Reason Of Unavailability is displayed automatically
 A COMMAND BUTTON to clear the input text on the form
 A COMMAND BUTTON to update the database information
Remarks

13.2.25 Maintain Trailer Maintenance

Page Id: 21-00 Page Name: Trailer Maintenance
Information
Style Sheet: Called from:

108
 Screenshot

Functionality
1. This page will be accessible to Administrators and Planners to maintain
Trailer Maintenance Information.
2. This page will have the following controls

 The Serial Number is auto-generated

 Trailer Number will be auto-generated by the system and displayed to the

user.
 A LISTBOX to select the type of maintenance. The LISTBOX will
have the following values
o Routine Maintenance
o Breakdown Maintenance
o Change Of Tuyeres
 A TEXTBOX to enter the date from which the trailer is under Maintenance
 The date upto which the trailer will be under Maintenance is auto generated
depending on the number of days taken by the Maintenance to complete
 A COMMAND BUTTON to clear the input text on the form
 A COMMAND BUTTON to update the database information
Remarks
2.

13.2.26 Maintain Trailer Monitoring

Page Id: 22-00 Page Name: Trailer Monitoring
Style Sheet: Called from:

109
Screenshot

Functionality

110
 1. This page will be accessible to Administrators and Planners to maintain Trailer
Monitoring Information.
2. This page will have the following controls

 The Serial Number is auto-generated

 Trailer Number will be auto-generated by the system and displayed to the user.
 The present location will be fetched from the database and displayed to the
user.It is the premise where the Trailer is present now
 The From Date will be fetched from the database and displayed to the
user.This is the date since which the Trailer is present at the given Location
 The To Date will be fetched from the database and displayed to the user.This is
the date after which the Trailer should leave its present location to return
 The Target Collection Date will be fetched from the database and displayed to
the user.This is the date upto which the Trailer can be present at the location.Any
Trailer collected after this date introduces Ageing
 The Ageing(Customer) is auto generated by the system.If the customer fails to
empty the Trailer by the Target Collection Date then this field is calculated by
subtracting the current date from the Target Collection Date.However, if the Customer
Ready Date is greater than the Target Collection Date , then the former is taken into
consideration while calculating the Ageing.
 The Ageing(Failed Collection) is auto generated by the system.If the customer
releases the Trailer by the Target Collection Date but the Haulage System fails to
collect the empty Trailer by then this field is calculated by subtracting the current date
from the Target Collection Date. However, if the Customer Ready Date is greater than
the Target Collection Date , then the former is taken into consideration while
calculating the Ageing.
 The Customer Ready Date is the date on which the customer expects to release
the Trailer
 A COMMAND BUTTON to clear the input text on the form
 A COMMAND BUTTON to update the database information
Remarks
3.

13.2.27 New Request Page

Page Id: Page Name: ROT.asp
Style Sheet: Hms.css Called from: Customer Home Page

111
Screenshot

112
Functionality
.
This Page is for filling up New Request form by customer and so hereby display the
following controls.
A. Request Order Headers
➘ A LABEL to display Request No.
➘ A LABEL to display Request Date
➘ A LABEL to display Order No.
➘ A LABEL to display Order Date
B. Two Checkboxes to select the Job Type Required (Delivery or Collection or
both).
a. The Checkbox corresponding to Delivery will show the Delivery
Button when clicked.
b. The Checkbox corresponding to Delivery will show the Collection
Button when clicked.
C. Controlling Visibility of (Delivery or Collection) Sections
a. A Button to show the Delivery Section and hide Collection Section
while clicked.
b. A Button to show the Collection Section and hide Delivery Section
while clicked.
D. Delivery Section
a. Subsection Controlling Buttons
i. A Button to show and fill up Service Details and hide other
subsections.
➘ Service Details
o A TEXTBOX to insert Delivery Required Date in
(dd/mm/yyyy) format
• If this checkbox is clicked A calendar will be
shown to insert the date on click, which will be
hidden on click outside the calendar and the
above checkbox.
o A TEXTBOX to insert Delivery Required Time in
(hh:mm) format
o A SELECTION BOX to select From Premise
o A SELECTION BOX to select To Premise
o A CHECKBOX to select Delivery Offload
Required
o A CHECKBOX to select Delivery Waiting
Required
o A TEXTBOX for inserting Delivery Waiting
Time
• The above will be initially hidden. It is visible
whenever the CHECKBOX corresponding to
Delivery Waiting Required is checked.
o A CHECKBOX to select Diversion Required.
o A SELECTION BOX to insert Diversion 2nd
Premise
• The above will be initially hidden. It is visible

113
 o A TEXTBOX to insert Diversion 2nd Premise
Waiting Time
• The above will be initially hidden. It is visible
whenever the CHECKBOXES corresponding
to Diversion Required and Diversion 2nd
Premise Waiting Required is checked.
ii. A Button to show and fill up Consignment Details and hide
other subsections.
➘ Consignment Details
o A TEXTBOX to insert Consignment No.
o A SELECTION BOX to select Consignment Type
whether it is Normal, Perishable or Dangerous
o OPTION BUTTONS to select Whether Import or
Export
o A TEXTBOX to insert Consignment Weight in
Tons
o A TEXTBOX to insert Consignment Quantity
o A TEXTBOX to insert Unit Measurement
o A TEXTBOX to insert Consignment Value
o A LABEL to distinguish Consignor Details
subsection.
o A TEXTBOX to insert Consignor Name
o A Scrollable TEXTAREA to insert Consignor
Address1
o A Scrollable TEXTAREA to insert Consignor
Address2
o A TEXTBOX to insert Consignor City
o A TEXTBOX to insert Consignor Country
o A TEXTBOX to insert Consignor Pin code
o A TEXTBOX to insert Consignor Phone No.
o A TEXTBOX to insert Consignor Contact
Person’s Name.
o A LABEL to distinguish Consignee Details
subsection.
o A TEXTBOX to insert Consignee Name
o A Scrollable TEXTAREA to insert Consignee
Address1
o A Scrollable TEXTAREA to insert Consignee
Address2
o A TEXTBOX to insert Consignee City
o A TEXTBOX to insert Consignee Country
o A TEXTBOX to insert Consignee Pin code
o A TEXTBOX to insert Consignee Phone No.
o A TEXTBOX to insert Consignee Contact
Person’s Name.

114
iii. A Button to show and fill up Container Details and hide other
subsections.
➘ Container Details
o A TEXTBOX to insert Container Number
o OPTION BUTTONS to select Whether Container
Size is 20 or 40
o A SELECTION BOX to select Container Type
whether it is Normal or Refrigerated.
o A TEXTBOX to insert Container Owner
o OPTION BUTTONS to select Whether Container
Status will be Laden or Empty.
iv. A Button to show and fill up Voyage & Vessel Details and
hide other subsections.
➘ Voyage & Vessel Details
o A TEXTBOX to insert Voyage Number.
o A TEXTBOX to insert Vessel Expected Date of
Arrival in (dd/mm/yyyy) format.
o A TEXTBOX to insert Vessel Expected Time of
Arrival in (hh:mm) format.
o A TEXTBOX to insert Vessel Name.
o A TEXTBOX to insert Vessel Type.
o A TEXTBOX to insert Vessel Country of Origin.
o A TEXTBOX to insert Shipping Line.

115
E. Collection Section
a. Subsection Controlling Buttons
i. A Button to show and fill up Service Details and hide other
subsections.
➘ Service Details
o A TEXTBOX to insert Delivery Required Date in
(dd/mm/yyyy) format
• If this checkbox is clicked A calendar will be
shown to insert the date on click, which will be
hidden on click outside the calendar and the
above checkbox.
o A TEXTBOX to insert Delivery Required Time in
(hh:mm) format
o A SELECTION BOX to select From Premise
o A SELECTION BOX to select To Premise
o A CHECKBOX to select Delivery Offload
Required
o A CHECKBOX to select Delivery Waiting
Required
o A TEXTBOX for inserting Delivery Waiting
Time
• The above will be initially hidden. It is visible
whenever the CHECKBOX corresponding to
Delivery Waiting Required is checked.
ii. A Button to show and fill up Consignment Details and hide
other subsections.
➘ Consignment Details
o A TEXTBOX to insert Consignment No.
o A SELECTION BOX to select Consignment Type
whether it is Normal, Perishable or Dangerous
o OPTION BUTTONS to select Whether Import or
Export
o A TEXTBOX to insert Consignment Weight in
Tons
o A TEXTBOX to insert Consignment Quantity
o A TEXTBOX to insert Unit Measurement
o A TEXTBOX to insert Consignment Value
o A LABEL to distinguish Consignor Details
subsection.
o A TEXTBOX to insert Consignor Name
o A Scrollable TEXTAREA to insert Consignor
Address1
o A Scrollable TEXTAREA to insert Consignor
Address2
o A TEXTBOX to insert Consignor City
o A TEXTBOX to insert Consignor Country
o A TEXTBOX to insert Consignor Pin code

116
 o A LABEL to distinguish Consignee Details
subsection.
o A TEXTBOX to insert Consignee Name
o A Scrollable TEXTAREA to insert Consignee
Address1
o A Scrollable TEXTAREA to insert Consignee
Address2
o A TEXTBOX to insert Consignee City
o A TEXTBOX to insert Consignee Country
o A TEXTBOX to insert Consignee Pin code
o A TEXTBOX to insert Consignee Phone No.
o A TEXTBOX to insert Consignee Contact
Person’s Name.
iii. A Button to show and fill up Container Details and hide other
subsections.
➘ Container Details
o A TEXTBOX to insert Container Number
o OPTION BUTTONS to select Whether Container
Size is 20 or 40
o A SELECTION BOX to select Container Type
whether it is Normal or Refrigerated.
o A TEXTBOX to insert Container Owner
o OPTION BUTTONS to select Whether Container
Status will be Laden or Empty.
iv. A Button to show and fill up Voyage & Vessel Details and
hide other subsections.
➘ Voyage & Vessel Details
o A TEXTBOX to insert Voyage Number.
o A TEXTBOX to insert Vessel Expected Date of
Arrival in (dd/mm/yyyy) format.
o A TEXTBOX to insert Vessel Expected Time of
Arrival in (hh:mm) format.
o A TEXTBOX to insert Vessel Name.
o A TEXTBOX to insert Vessel Type.
o A TEXTBOX to insert Vessel Country of Origin.
o A TEXTBOX to insert Shipping Line.
F. Form Control
a. A BUTTON to go to the Next Section.
b. A BUTTON to Submit the form on this Level.
c. A BUTTON to Refresh the entire form.
G. A Button to Calculate the estimated cost of the given order.
Remarks

13.2.28 New Order Page

Page Id: Page Name: NewOrder.html
Style Sheet: Hms.css Called from: VROT.html

117
Screenshot
Same as New Request Page. Only the heading is “New Order” in
Place of “New Request”.

118
Functionality
.
This Page is for filling up New Order form for the Request just filled by
customer and so hereby display the following controls.
H. Request Order Headers
➘ A LABEL to display Request No.
➘ A LABEL to display Request Date
➘ A LABEL to display Order No.
➘ A LABEL to display Order Date
I. Two Checkboxes to select the Job Type Required (Delivery or Collection
or both).
a. The Checkbox corresponding to Delivery will show the Delivery
Button when clicked.
b. The Checkbox corresponding to Delivery will show the
Collection Button when clicked.
J. Controlling Visibility of (Delivery or Collection) Sections
a. A Button to show the Delivery Section and hide Collection
Section while clicked.
b. A Button to show the Collection Section and hide Delivery
Section while clicked.
K. Delivery Section
a. Subsection Controlling Buttons
i. A Button to show and fill up Service Details and hide
other subsections.
➘ Service Details
o A TEXTBOX to insert Delivery Required
Date in (dd/mm/yyyy) format
• If this checkbox is clicked A calendar will
be shown to insert the date on click, which
will be hidden on click outside the calendar
and the above checkbox.
o A TEXTBOX to insert Delivery Required
Time in (hh:mm) format
o A SELECTION BOX to select From Premise
o A SELECTION BOX to select To Premise
o A CHECKBOX to select Delivery Offload
Required
o A CHECKBOX to select Delivery Waiting
Required
o A TEXTBOX for inserting Delivery Waiting
Time
• The above will be initially hidden. It is
visible whenever the CHECKBOX
corresponding to Delivery Waiting
Required is checked.
o A CHECKBOX to select Diversion Required.
o A SELECTION BOX to insert Diversion 2nd
Premise

119
 o A TEXTBOX to insert Diversion 2nd Premise
Waiting Time
• The above will be initially hidden. It is
visible whenever the CHECKBOXES
corresponding to Diversion Required and
Diversion 2nd Premise Waiting Required is
checked.
ii. A Button to show and fill up Consignment Details and
hide other subsections.
➘ Consignment Details
o A TEXTBOX to insert Consignment No.
o A SELECTION BOX to select Consignment
Type whether it is Normal, Perishable or
Dangerous
o OPTION BUTTONS to select Whether Import
or Export
o A TEXTBOX to insert Consignment Weight
in Tons
o A TEXTBOX to insert Consignment Quantity
o A TEXTBOX to insert Unit Measurement
o A TEXTBOX to insert Consignment Value
o A LABEL to distinguish Consignor Details
subsection.
o A TEXTBOX to insert Consignor Name
o A Scrollable TEXTAREA to insert Consignor
Address1
o A Scrollable TEXTAREA to insert Consignor
Address2
o A TEXTBOX to insert Consignor City
o A TEXTBOX to insert Consignor Country
o A TEXTBOX to insert Consignor Pin code
o A TEXTBOX to insert Consignor Phone No.
o A TEXTBOX to insert Consignor Contact
Person’s Name.
o A LABEL to distinguish Consignee Details
subsection.
o A TEXTBOX to insert Consignee Name
o A Scrollable TEXTAREA to insert Consignee
Address1
o A Scrollable TEXTAREA to insert Consignee
Address2
o A TEXTBOX to insert Consignee City
o A TEXTBOX to insert Consignee Country
o A TEXTBOX to insert Consignee Pin code
o A TEXTBOX to insert Consignee Phone No.
o A TEXTBOX to insert Consignee Contact
Person’s Name.

120
iii. A Button to show and fill up Container Details and hide
other subsections.
➘ Container Details
o A TEXTBOX to insert Container Number
o OPTION BUTTONS to select Whether
Container Size is 20 or 40
o A SELECTION BOX to select Container Type
whether it is Normal or Refrigerated.
o A TEXTBOX to insert Container Owner
o OPTION BUTTONS to select Whether
Container Status will be Laden or Empty.
iv. A Button to show and fill up Voyage & Vessel Details
and hide other subsections.
➘ Voyage & Vessel Details
o A TEXTBOX to insert Voyage Number.
o A TEXTBOX to insert Vessel Expected Date
of Arrival in (dd/mm/yyyy) format.
o A TEXTBOX to insert Vessel Expected Time
of Arrival in (hh:mm) format.
o A TEXTBOX to insert Vessel Name.
o A TEXTBOX to insert Vessel Type.
o A TEXTBOX to insert Vessel Country of
Origin.
o A TEXTBOX to insert Shipping Line.

121
L. Collection Section
a. Subsection Controlling Buttons
i. A Button to show and fill up Service Details and hide
other subsections.
➘ Service Details
o A TEXTBOX to insert Delivery Required
Date in (dd/mm/yyyy) format
• If this checkbox is clicked A calendar will
be shown to insert the date on click, which
will be hidden on click outside the calendar
and the above checkbox.
o A TEXTBOX to insert Delivery Required
Time in (hh:mm) format
o A SELECTION BOX to select From Premise
o A SELECTION BOX to select To Premise
o A CHECKBOX to select Delivery Offload
Required
o A CHECKBOX to select Delivery Waiting
Required
o A TEXTBOX for inserting Delivery Waiting
Time
• The above will be initially hidden. It is
visible whenever the CHECKBOX
corresponding to Delivery Waiting
Required is checked.
ii. A Button to show and fill up Consignment Details and
hide other subsections.
➘ Consignment Details
o A TEXTBOX to insert Consignment No.
o A SELECTION BOX to select Consignment
Type whether it is Normal, Perishable or
Dangerous
o OPTION BUTTONS to select Whether Import
or Export
o A TEXTBOX to insert Consignment Weight
in Tons
o A TEXTBOX to insert Consignment Quantity
o A TEXTBOX to insert Unit Measurement
o A TEXTBOX to insert Consignment Value
o A LABEL to distinguish Consignor Details
subsection.
o A TEXTBOX to insert Consignor Name
o A Scrollable TEXTAREA to insert Consignor
Address1
o A Scrollable TEXTAREA to insert Consignor
Address2
o A TEXTBOX to insert Consignor City
o A TEXTBOX to insert Consignor Country
122
 o A LABEL to distinguish Consignee Details
subsection.
o A TEXTBOX to insert Consignee Name
o A Scrollable TEXTAREA to insert Consignee
Address1
o A Scrollable TEXTAREA to insert Consignee
Address2
o A TEXTBOX to insert Consignee City
o A TEXTBOX to insert Consignee Country
o A TEXTBOX to insert Consignee Pin code
o A TEXTBOX to insert Consignee Phone No.
o A TEXTBOX to insert Consignee Contact
Person’s Name.
iii. A Button to show and fill up Container Details and hide
other subsections.
➘ Container Details
o A TEXTBOX to insert Container Number
o OPTION BUTTONS to select Whether
Container Size is 20 or 40
o A SELECTION BOX to select Container Type
whether it is Normal or Refrigerated.
o A TEXTBOX to insert Container Owner
o OPTION BUTTONS to select Whether
Container Status will be Laden or Empty.
iv. A Button to show and fill up Voyage & Vessel Details
and hide other subsections.
➘ Voyage & Vessel Details
o A TEXTBOX to insert Voyage Number.
o A TEXTBOX to insert Vessel Expected Date
of Arrival in (dd/mm/yyyy) format.
o A TEXTBOX to insert Vessel Expected Time
of Arrival in (hh:mm) format.
o A TEXTBOX to insert Vessel Name.
o A TEXTBOX to insert Vessel Type.
o A TEXTBOX to insert Vessel Country of
Origin.
o A TEXTBOX to insert Shipping Line.
M. Form Control
a. A BUTTON to go to the Next Section.
b. A BUTTON to Submit the form on this Level.
c. A BUTTON to Refresh the entire form.
N. A Button to Calculate the estimated cost of the given order.
Remarks

123
13.2.29 Update Request – Request Number Entry Page
Page Id: Page Name: SUROT.html
Style Called from: Customer Home Page
Sheet:
Screenshot

Functionality
 A TEXTBOX to insert the Request Number for which the updating should take place.
 A Button to view the following Section when clicked.
 A Button To open Detailed Update Request Page of the particular order
selected by checking the OPTION BUTTON mentioned below when clicked
 A Button to the open Detailed View Request Page of the particular order
selected by checking the OPTION BUTTON mentioned below when clicked.
 A Table to show to the customer the important fields (Order No.,
Service Type, Job Type, Delivery Required Date, Delivery Required Time, Collection
Required Date, Delivery Required Time) relevant to the Orders corresponding to the
Request Number filled in the above text box and hereby help the customer to select the
orders for updating corresponding to the same Request .
 There is an OPTION BUTTON in the left cell of the cell contained
Order No. Field in each row in the table to select the particular order corresponding to the
same order number for Updating.
Remarks

13.2.30 Update Request –Detailed Page

Page Id: Page Name: UROT.html
Style Sheet: Hms.css Called from: SUROT.html

124
Screenshot

Same as New Request Page. Only the heading is “New Order” in

Place of “New Request”.

125
Functionality
This Page is for filling up New Request form by customer and so hereby display the
following controls.
A. Request Order Headers
➘ A LABEL to display Request No.
➘ A LABEL to display Request Date
➘ A LABEL to display Order No.
➘ A LABEL to display Order Date
B. Two Checkboxes to select the Job Type Required (Delivery or Collection or
both).
a. The Checkbox corresponding to Delivery will show the Delivery
Button when clicked.
b. The Checkbox corresponding to Delivery will show the Collection
Button when clicked.
C. Controlling Visibility of (Delivery or Collection) Sections
a. A Button to show the Delivery Section and hide Collection Section
while clicked.
b. A Button to show the Collection Section and hide Delivery Section
while clicked.
D. Delivery Section
a. Subsection Controlling Buttons
i. A Button to show and fill up Service Details and hide other
subsections.
➘ Service Details
o A TEXTBOX to insert Delivery Required Date in
(dd/mm/yyyy) format
• If this checkbox is clicked A calendar will be
shown to insert the date on click, which will be
hidden on click outside the calendar and the
above checkbox.
o A TEXTBOX to insert Delivery Required Time in
(hh:mm) format
o A SELECTION BOX to select From Premise
o A SELECTION BOX to select To Premise
o A CHECKBOX to select Delivery Offload
Required
o A CHECKBOX to select Delivery Waiting
Required
o A TEXTBOX for inserting Delivery Waiting Time
• The above will be initially hidden. It is visible
whenever the CHECKBOX corresponding to
Delivery Waiting Required is checked.
o A CHECKBOX to select Diversion Required.
o A SELECTION BOX to insert Diversion 2nd
Premise
• The above will be initially hidden. It is visible
whenever the CHECKBOX corresponding to
Diversion Required is checked.

126
 o A TEXTBOX to insert Diversion 2nd Premise
Waiting Time
• The above will be initially hidden. It is visible
whenever the CHECKBOXES corresponding to
Diversion Required and Diversion 2nd Premise
Waiting Required is checked.
ii. A Button to show and fill up Consignment Details and hide
other subsections.
➘ Consignment Details
o A TEXTBOX to insert Consignment No.
o A SELECTION BOX to select Consignment Type
whether it is Normal, Perishable or Dangerous
o OPTION BUTTONS to select Whether Import or
Export
o A TEXTBOX to insert Consignment Weight in
Tons
o A TEXTBOX to insert Consignment Quantity
o A TEXTBOX to insert Unit Measurement
o A TEXTBOX to insert Consignment Value
o A LABEL to distinguish Consignor Details
subsection.
o A TEXTBOX to insert Consignor Name
o A Scrollable TEXTAREA to insert Consignor
Address1
o A Scrollable TEXTAREA to insert Consignor
Address2
o A TEXTBOX to insert Consignor City
o A TEXTBOX to insert Consignor Country
o A TEXTBOX to insert Consignor Pin code
o A TEXTBOX to insert Consignor Phone No.
o A TEXTBOX to insert Consignor Contact
Person’s Name.
o A LABEL to distinguish Consignee Details
subsection.
o A TEXTBOX to insert Consignee Name
o A Scrollable TEXTAREA to insert Consignee
Address1
o A Scrollable TEXTAREA to insert Consignee
Address2
o A TEXTBOX to insert Consignee City
o A TEXTBOX to insert Consignee Country
o A TEXTBOX to insert Consignee Pin code
o A TEXTBOX to insert Consignee Phone No.
o A TEXTBOX to insert Consignee Contact
Person’s Name

127
iii. A Button to show and fill up Container Details and hide other
subsections.
➘ Container Details
o A TEXTBOX to insert Container Number
o OPTION BUTTONS to select Whether Container
Size is 20 or 40
o A SELECTION BOX to select Container Type
whether it is Normal or Refrigerated.
o A TEXTBOX to insert Container Owner
o OPTION BUTTONS to select Whether Container
Status will be Laden or Empty.
iv. A Button to show and fill up Voyage & Vessel Details and
hide other subsections.
➘ Voyage & Vessel Details
o A TEXTBOX to insert Voyage Number.
o A TEXTBOX to insert Vessel Expected Date of
Arrival in (dd/mm/yyyy) format.
o A TEXTBOX to insert Vessel Expected Time of
Arrival in (hh:mm) format.
o A TEXTBOX to insert Vessel Name.
o A TEXTBOX to insert Vessel Type.
o A TEXTBOX to insert Vessel Country of Origin.
o A TEXTBOX to insert Shipping Line.

128
E. Collection Section
a. Subsection Controlling Buttons
i. A Button to show and fill up Service Details and hide other
subsections.
➘ Service Details
o A TEXTBOX to insert Delivery Required Date in
(dd/mm/yyyy) format
• If this checkbox is clicked A calendar will be
shown to insert the date on click, which will be
hidden on click outside the calendar and the
above checkbox.
o A TEXTBOX to insert Delivery Required Time in
(hh:mm) format
o A SELECTION BOX to select From Premise
o A SELECTION BOX to select To Premise
o A CHECKBOX to select Delivery Offload
Required
o A CHECKBOX to select Delivery Waiting
Required
o A TEXTBOX for inserting Delivery Waiting Time
• The above will be initially hidden. It is visible
whenever the CHECKBOX corresponding to
Delivery Waiting Required is checked.
ii. A Button to show and fill up Consignment Details and hide
other subsections.
➘ Consignment Details
o A TEXTBOX to insert Consignment No.
o A SELECTION BOX to select Consignment Type
whether it is Normal, Perishable or Dangerous
o OPTION BUTTONS to select Whether Import or
Export
o A TEXTBOX to insert Consignment Weight in
Tons
o A TEXTBOX to insert Consignment Quantity
o A TEXTBOX to insert Unit Measurement
o A TEXTBOX to insert Consignment Value
o A LABEL to distinguish Consignor Details
subsection.
o A TEXTBOX to insert Consignor Name
o A Scrollable TEXTAREA to insert Consignor
Address1
o A Scrollable TEXTAREA to insert Consignor
Address2
o A TEXTBOX to insert Consignor City
o A TEXTBOX to insert Consignor Country
o A TEXTBOX to insert Consignor Pin code
o A TEXTBOX to insert Consignor Phone No.

129
 o A LABEL to distinguish Consignee Details
subsection.
o A TEXTBOX to insert Consignee Name
o A Scrollable TEXTAREA to insert Consignee
Address1
o A Scrollable TEXTAREA to insert Consignee
Address2
o A TEXTBOX to insert Consignee City
o A TEXTBOX to insert Consignee Country
o A TEXTBOX to insert Consignee Pin code
o A TEXTBOX to insert Consignee Phone No.
o A TEXTBOX to insert Consignee Contact
Person’s Name.
iii. A Button to show and fill up Container Details and hide other
subsections.
➘ Container Details
o A TEXTBOX to insert Container Number
o OPTION BUTTONS to select Whether Container
Size is 20 or 40
o A SELECTION BOX to select Container Type
whether it is Normal or Refrigerated.
o A TEXTBOX to insert Container Owner
o OPTION BUTTONS to select Whether Container
Status will be Laden or Empty.
iv. A Button to show and fill up Voyage & Vessel Details and
hide other subsections.
➘ Voyage & Vessel Details
o A TEXTBOX to insert Voyage Number.
o A TEXTBOX to insert Vessel Expected Date of
Arrival in (dd/mm/yyyy) format.
o A TEXTBOX to insert Vessel Expected Time of
Arrival in (hh:mm) format.
o A TEXTBOX to insert Vessel Name.
o A TEXTBOX to insert Vessel Type.
o A TEXTBOX to insert Vessel Country of Origin.
o A TEXTBOX to insert Shipping Line.
F. Form Control
a. A BUTTON to go to the Next Section.
b. A BUTTON to Submit the form on this Level.
c. A BUTTON to Refresh the entire form.
G. A Button to Calculate the estimated cost of the given order.
Remarks

13.2.31 View Request – Request Number Entry Page

Page Id: Page Name: SVROT.html

130
 Style Called from: Customer Home Page
Sheet:
Screenshot

Functionality
 A TEXTBOX to insert the Request Number for which the orders should be viewed.
 A Button to view the following table when clicked.
 A Table to show to the customer the important fields (Order No.,
Service Type, Job Type, Delivery Required Date, Delivery Required Time, Collection
Required Date, Delivery Required Time) relevant to the Orders corresponding to the
Request Number filled in the above text box and hereby help the customer to select the
orders for updating corresponding to the same Request .
 The Order No. Fields in each row in the table are hyper linked to open
the detail view page of the particular order corresponding to the same order number.
Remarks

13.2.32 View Request – View Next to Filled Up Order

Page Id: Page Name: SVROT.html
Style Called from: Customer Home Page
Sheet:

131
 Screenshot

Functionality
 A Frame for Showing the following Button.
 A Button ADD MORE ORDER to open the New Order Page in a blank
to fill the next Order for the Request just filled window when clicked.
 A Frame to view the Detailed View Request Page in it.
Remarks

13.2.33 View Request – Detailed Page

Page Id: Page Name: VDROT.html
Style Sheet: Hms.css Called from: SVROT.html,VROT.html
Screenshot

132
Functionality.
This Page is for Displaying Request to customer and so hereby display the following
disabled controls.
A. Request Order Headers
➘ A LABEL to display Request No.
➘ A LABEL to display Request Date
➘ A LABEL to display Order No.
➘ A LABEL to display Order Date
B. Two Checkboxes to display the Job Type Required (Delivery or Collection or
both).
a. The Checkbox corresponding to Delivery will show the Delivery
Button when clicked.
b. The Checkbox corresponding to Delivery will show the Collection
Button when clicked.
C. Controlling Visibility of (Delivery or Collection) Sections
a. A Button to show the Delivery Section and hide Collection Section
while clicked.
b. A Button to show the Collection Section and hide Delivery Section
while clicked.
D. Delivery Section
a. Subsection Controlling Buttons
i. A Button to show and fill up Service Details and hide other
subsections.
➘ Service Details
o A TEXTBOX to view Delivery Required Date in
(dd/mm/yyyy) format
o A TEXTBOX to view Delivery Required Time in
(hh:mm) format
o A SELECTION BOX to view the previously
selected From Premise
o A SELECTION BOX to view the previously
selected To Premise
o A CHECKBOX to view the previously selected
Delivery Offload Required
o A CHECKBOX to view the previously selected
Delivery Waiting Required
o A TEXTBOX for viewing Delivery Waiting Time
• The above will be initially hidden. It is visible
whenever the CHECKBOX corresponding to
Delivery Waiting Required is checked.
o A CHECKBOX to view the previously selected
Diversion Required.
o A SELECTION BOX to view Diversion 2nd
Premise
• The above will be initially hidden. It is visible
whenever the CHECKBOX corresponding to
Diversion Required is checked.
o A CHECKBOX to view the previously selected

133
 o A TEXTBOX to view Diversion 2nd Premise
Waiting Time
• The above will be initially hidden. It is visible
whenever the CHECKBOXES corresponding to
Diversion Required and Diversion 2nd Premise
Waiting Required is checked.
➘ Form Control
o A BUTTON to go to the Next Section.
o A BUTTON to Submit the form on this Level.
o A BUTTON to Refresh the entire form.
ii. A Button to show and fill up Consignment Details and hide
other subsections.
➘ Consignment Details
o A TEXTBOX to view Consignment No.
o A SELECTION BOX to view the previously
selected Consignment Type whether it is Normal,
Perishable or Dangerous
o OPTION BUTTONS to view the previously
selected Whether Import or Export
o A TEXTBOX to view Consignment Weight in
Tons
o A TEXTBOX to view Consignment Quantity
o A TEXTBOX to view Unit Measurement
o A TEXTBOX to view Consignment Value
o A LABEL to distinguish Consignor Details
subsection.
o A TEXTBOX to view Consignor Name
o A Scrollable TEXTAREA to view Consignor
Address1
o A Scrollable TEXTAREA to view Consignor
Address2
o A TEXTBOX to view Consignor City
o A TEXTBOX to view Consignor Country
o A TEXTBOX to view Consignor Pin code
o A TEXTBOX to view Consignor Phone No.
o A TEXTBOX to view Consignor Contact Person’s
Name.
o A LABEL to distinguish Consignee Details
subsection.
o A TEXTBOX to view Consignee Name
o A Scrollable TEXTAREA to view Consignee
Address1
o A Scrollable TEXTAREA to view Consignee
Address2
o A TEXTBOX to view Consignee City
o A TEXTBOX to view Consignee Country
o A TEXTBOX to view Consignee Pin code

134
iii. A Button to show and fill up Container Details and hide other
subsections.
➘ Container Details
o A TEXTBOX to view Container Number
o OPTION BUTTONS to view the previously
selected Whether Container Size is 20 or 40
o A SELECTION BOX to view the previously
selected Container Type whether it is Normal or
Refrigerated.
o A TEXTBOX to view Container Owner
o OPTION BUTTONS to view the previously
selected Whether Container Status will be Laden
or Empty.
iv. A Button to show and fill up Voyage & Vessel Details and
hide other subsections.
➘ Voyage & Vessel Details
o A TEXTBOX to view Voyage Number.
o A TEXTBOX to view Vessel Expected Date of
Arrival in (dd/mm/yyyy) format.
o A TEXTBOX to view Vessel Expected Time of
Arrival in (hh:mm) format.
o A TEXTBOX to view Vessel Name.
o A TEXTBOX to view Vessel Type.
o A TEXTBOX to view Vessel Country of Origin.
o A TEXTBOX to view Shipping Line.

135
E. Collection Section
a. Subsection Controlling Buttons
i. A Button to show and fill up Service Details and hide other
subsections.
➘ Service Details
o A TEXTBOX to insert Delivery Required Date in
(dd/mm/yyyy) format
• If this checkbox is clicked A calendar will be
shown to insert the date on click, which will be
hidden on click outside the calendar and the
above checkbox.
o A TEXTBOX to insert Delivery Required Time in
(hh:mm) format
o A SELECTION BOX to view the previously
selected From Premise
o A SELECTION BOX to view the previously
selected To Premise
o A CHECKBOX to view the previously selected
Delivery Offload Required
o A CHECKBOX to view the previously selected
Delivery Waiting Required
o A TEXTBOX for inserting Delivery Waiting Time
• The above will be initially hidden. It is visible
whenever the CHECKBOX corresponding to
Delivery Waiting Required is checked.
ii. A Button to show and fill up Consignment Details and hide
other subsections.
➘ Consignment Details
o A TEXTBOX to insert Consignment No.
o A SELECTION BOX to view the previously
selected Consignment Type whether it is Normal,
Perishable or Dangerous
o OPTION BUTTONS to view the previously
selected Whether Import or Export
o A TEXTBOX to insert Consignment Weight in
Tons
o A TEXTBOX to insert Consignment Quantity
o A TEXTBOX to insert Unit Measurement
o A TEXTBOX to insert Consignment Value
o A LABEL to distinguish Consignor Details
subsection.
o A TEXTBOX to insert Consignor Name
o A Scrollable TEXTAREA to insert Consignor
Address1
o A Scrollable TEXTAREA to insert Consignor
Address2
o A TEXTBOX to insert Consignor City
o A TEXTBOX to insert Consignor Country
136
 o A LABEL to distinguish Consignee Details
subsection.
o A TEXTBOX to insert Consignee Name
o A Scrollable TEXTAREA to insert Consignee
Address1
o A Scrollable TEXTAREA to insert Consignee
Address2
o A TEXTBOX to insert Consignee City
o A TEXTBOX to insert Consignee Country
o A TEXTBOX to insert Consignee Pin code
o A TEXTBOX to insert Consignee Phone No.
o A TEXTBOX to insert Consignee Contact
Person’s Name.
iii. A Button to show and fill up Container Details and hide other
subsections.
➘ Container Details
o A TEXTBOX to insert Container Number
o OPTION BUTTONS to view the previously
selected Whether Container Size is 20 or 40
o A SELECTION BOX to view the previously
selected Container Type whether it is Normal or
Refrigerated.
o A TEXTBOX to insert Container Owner
o OPTION BUTTONS to view the previously
selected Whether Container Status will be Laden
or Empty.
iv. A Button to show and fill up Voyage & Vessel Details and
hide other subsections.
➘ Voyage & Vessel Details
o A TEXTBOX to insert Voyage Number.
o A TEXTBOX to insert Vessel Expected Date of
Arrival in (dd/mm/yyyy) format.
o A TEXTBOX to insert Vessel Expected Time of
Arrival in (hh:mm) format.
o A TEXTBOX to insert Vessel Name.
o A TEXTBOX to insert Vessel Type.
o A TEXTBOX to insert Vessel Country of Origin.
o A TEXTBOX to insert Shipping Line.

Remarks

13.2.34 Cancel ROT

Page Id: Page Name: SCROT.html

Style Called from: Customer Home Page
Sheet:

137
 Screenshot

Functionality
 A TEXTBOX to insert the Request Number for which the cancellation should take place.
 A Button to view the following Section when clicked.
 A Button SELECT ALL, If it is checked, then all the CHECKBOX will
be checked.
 A Button UNCHECK ALL, The all selected order (checkbox) will be
unchecked.
 A Button CANCEL, All the selected order will be deleted.
 A Table to show to the customer the important fields (Order No.,
Service Type, Job Type, Delivery Required Date, Delivery Required Time, Collection
Required Date, Delivery Required Time) relevant to the Orders corresponding to the
Request Number filled in the above text box and hereby help the customer to select the
orders for cancellation corresponding to the same Request.
 There is a CHECBOX in the left cell of the cell contained Order No.
Field in each row in the table to select the particular orders corresponding to the same
order number for cancellation.
 The Order No. field in each row in the table are hyper linked to open the
detail view page of the particular order corresponding to the same order number.
Remarks

13.2.35 Estimated Order Cost Page

Page Id: Page Name: Estimated Order Cost Page

(Customer point of view)
Style Sheet: Called from: ROT.html,NewOrder.html,UROT.ht
ml

138
Screenshot

Functionality
1. This page will be accessible to Customer to know the estimated cost of
an order.
2. This page have the following properties
 Request No, Order No, Order Type, Service Type, Service sub type
will automatically displayed by system.
 Transportation Cost, Diversion Cost, Side loader Cost of delivery job
and Transportation Cost, Staging Cost of collection job which are fill up
in new Order will calculated by system and generated automatically by
System
 Total cost is sum of all the cost and generated by system
 Clicking the button Close, the pop up will close and the control will
transfer to New ROT page.
 If there is a Back To Back CDA ,then a deduction of cost will be
reflected on corresponding second order.

Remarks

139
13.2.36 Detailed CDA
Page Id: 25-00 Page Name: Detailed CDA

Style Sheet: Hms.css Called from: View CDA

Screenshot

140
.
1 This page will display the detailed information for the particular CDA #
clicked in the ViewCDA Screen in tabular form.
The page contains the following labels
 Interim Status
 CDA #
 CDA Status
 Impex Type
 Request #
 Order #
 B2B CDA #
 Side Loader
 Required Date
 Required Time
 Service Type
 Service Sub-Type
 Container #
 Container Size
 ETA Date
 ETA Time
 From Premise
 To Premise
 Delivery Waiting t
 Waiting Time
 Delivery Offload
 Diversion
 Diversion Second Premise
 Diversion Second Premise Waiting Time
 Diversion Second Premise Offload
 Collection Ready Date
 Collection Ready Time
 Locality
 Empty Trailer Collection
 Replan Date LABEL
 Replanned By Customer or Planner.
 Consignment Type

2. The page will have the following controls:

 When REPLAN Button will be clicked, the replan Screen will be opened. The
fields on the Screen are editable .Replan is done when the required date is
changed or CDA failed to be executed on the Require Date.
 UPDATE this button will clicked when the required time gets changed .
 When FORWARD Button is clicked then if the previous operation was update
and we came out of it by clicking back then FORWARD will again bring us back
to the UPDATE Screen keeping the changes intact.Same will happen with the

141
 Remarks

13.2.37 Update CDA

Page Id: 26-00 Page Name: Update CDA

Style Sheet: Hms.css Called from: Detailed CDA

Screenshot

Functionality

142
 a. This page will have the following controls :
 A TEXTBOX for updating ETA Time. This will fetch the last
updated ETA Time and display it in editable mode when the
page is launched. When the ETA Time is edited and the
SAVE BUTTON is pressed, the modified ETA Time will be
updated into the database.
o The ETA Time cannot be less than the current time.
System will raise an error message when this condition
is violated.
 A CHECKBOX for displaying whether Side Loader required.
 A TEXTBOX for displaying Delivery Required Time.
o The Delivery Required Time cannot be less than the
current time. System will raise an error message when
this condition is violated.

 A TEXTBOX for displaying Collection Required Time.

o The Collection Required Time cannot be less than the
current time. System will raise an error message when
this condition is violated.

 A CHECKBOX for displaying whether Offload required.

 A CHECKBOX for displaying whether Diversion required.
 A DROPDOWN for viewing the previously selected
Diversion Second premise which will be enabled if Diversion
is required.
o This dropdown will be populated from the database.
Premises pertaining to the customer concerned will be
displayed.
 A Back button to go to the previous page from which the page
is called. If some changes made in the UpdateCDA Screen and
BACK Button is clicked then control will go back to the
DetailedCDA page. In DetailedCDA Screen if FORWARD
button is clicked then control will go to previous UpdateCDA
Screen keeping the changes intact.
 A SAVE Button to save the changes in database and control
will go to DetailedCDA Screen.
 A RESET Button to reset the values of all the fields with
original values.
 A CANCEL Button to cancel the changes made in Update
CDA Screen and control will go to DetailedCDA Screen.
Update Screen will disappear disregarding the changes made
in Update Screen.

Remarks

143
13.2.38 Replan CDA
Page Id: 27-00 Page Name: Replan CDA

Style Sheet: Hms.css Called from: Detailed CDA

Screenshot

Functionality

144
b. This page will have the following controls :
 A TEXTBOX for displaying repanned date.
o The repanned date cannot be less than the current date.
System will raise an error message when this condition
is violated.

 A TEXTBOX for displaying Repanned time.

o The Repanned Time cannot be less than the current
time. System will raise an error message when this
condition is violated.

 A TEXTBOX for displaying ETA date.

o The ETA date cannot be less than the current date.
System will raise an error message when this condition
is violated.

 A TEXTBOX for displaying ETA time.

o The ETA Time cannot be less than the current time.
System will raise an error message when this condition
is violated.

 A CHECKBOX for displaying whether Side Loader required.

 A CHECKBOX for displaying Delivery Required Time.
o The Delivery Required Time cannot be less than the
current time. System will raise an error message when
this condition is violated.

 A CHECKBOX for displaying Collection Required Time.

o The Collection Required Time cannot be less than the
current time. System will raise an error message when
this condition is violated.

 A CHECKBOX for displaying whether Offload required.

 A CHECKBOX for displaying whether Diversion required.
 A DROPDOWN for viewing the previously selected
Diversion Second premise which will be enabled if Diversion
is requied.
 Two OPTION BUTTON for viewing the previously selected
whether replanned by customer or planner.
 A Back button to go to the previous page from which the page
is called. If some changes made in the Replan Screen and
BACK Button is clicked then control will go back to the
DetailedCDA page. In DetailedCDA Screen if FORWARD
button is clicked then control will go to previous ReplanCDA
Screen keeping the changes intact.
 A SAVE Button to save the changes in database and control
will go to DetailedCDA Screen.
 A RESET Button to reset the values of all the fields with

145
 Remarks

13.2.39 Plan for CDAs

Page Id: 48-00 Page Name: Plan for CDAs
Style Sheet: Called from: Planner’s default home page
Screenshot

146
Functionality:
1. This Page is accessible by the planner and the administrator to make plan for
different CDAs .
2. This page have the following controls.
 A LABEL to display current Date.
 Two TEXTBOX to insert Planning Time in (hh:mm) format
 A SELECTION BOX to select prime mover. The selection will be database
driven.
 The availability of prime mover in different shifts will be displayed in tabular
format, after selecting a particular prime mover. It will show in which shift the
prime mover will be available.
 A SELECTION BOX to select shift1 driver. The selection will be database
driven. Depending upon the shift of selected prime mover the driver should be
chosen.
 A SELECTION BOX to select shift2 driver. The selection will be database
driven. Depending upon the shift of selected prime mover the driver should be
chosen.
 A SELECTION BOX to select shift3 driver. The selection will be database
driven. Depending upon the shift of selected prime mover the driver should be
chosen.

Three different TEXT BOXES are there to represent the colour code for different types
of CDA .
 Floralwhite will be used to represent new CDAs .
 #d0f0ff will be used to represent pending CDAs .
 #ffceff will be used to represent replanned CDAs

The following information will be displayed in tabular format.

 Serial No to represent the sequence.
 CDA No - it is a machine generated number and will be hyperlinked. On
clicking it will display the detailed information about the particular CDA.
 B2B CDA No. – If there is a B2B CDA for the particular current CDA, then
this column contains the corresponding B2B CDA number and this will be
hyperlinked to get the detailed information about that particular CDA.
 Visit No – it is the sequence number in which a prime mover will perform
different CDAs. There will be text box to enter the number and it will be given
by planner.
 Order Type – it represents the type of order. The different types of orders are :
 Direct Delivery.
 Direct Collection.
 Direct Delivery & Direct Collection.
 Direct Collection & Direct Delivery.
 IMPEX Type –
 Export.
 Import.
 Consign Type - it represents the nature of goods the consignment is handling.
According to the types there are different consignment types.

147
  Offload - it will represent whether offload is required or not. It is a Boolean
field.
• ‘Y’ for offload required.
• ‘N’ for offload not required.
 Side Loader –it will represent whether side loader option is required or not. It
is a Boolean field.
• ‘Y’ for side loader option required.
• ‘N’ for side loader option not required.
 Required Date – it is the date specified by the customer, on which the work is to
be done.
 Required Time - it is the time of a particular date specified by the customer,
when he/she wants the service.
 ETA Date – it is expected time of arrival of the vessel.
 ETA Time - it is expected time of arrival of the vessel.
 From - it represents the premise form where the consignment will be carried.
 To - it represents the premise where the consignment is to be carried.
 Diversion –
 Container Size - the type of container.
• 20’.
• 40’.
 Ageing - the number of days delayed from the required date.
 Replan Date - if the customer wants to change the required date of a particular
order after generation of CDA or under any unnecessary circumstance, the date
is changed by the planner. A TEXT BOX is there to do the job. It should be
kept in mind that replanned date should not less than required date.
 Allocate - A CHECK BOX is there to allocate a CDA to a particular prime
mover.
 BUTTON –
• Save Allocation – On clicking this button the allocation of different
attributes for planning a CDA is saved.
• Assign Trailer - On clicking this button Assignment of Trailer to Prime
Mover page will come and the assignment will be done.

Remarks

13.2.40 Assignment of Trailer to Prime Mover

Page Id: 48-00 Page Name: Assignment of Trailer to Prime
Mover
Style Sheet: Called from: Plan for CDAs

148
Screenshot

149
Functionality:

1. This page will be accessible to planner as well as administrator to assign trailers

to a particular prime mover.
2. This page will have the following controls.
3. A LABEL to display current Date.
4. A SELECTION BOX to select prime mover. The selection will be database
driven.
5. The availability of prime mover in different shifts will be displayed in tabular
format, after selecting a particular prime mover. It will show in which shift the
prime mover will be available.
6. A SELECTION BOX to select shift1 driver. The selection will be database
driven. Depending upon the shift of selected prime mover the driver should be
chosen.
7. A SELECTION BOX to select shift2 driver. The selection will be database
driven. Depending upon the shift of selected prime mover the driver should be
chosen.
8. A SELECTION BOX to select shift3 driver. The selection will be database
driven. Depending upon the shift of selected prime mover the driver should be
chosen.
9. Three different TEXT BOXES are there to represent the colour code for
different types of CDA .
10. Floralwhite will be used to represent new CDAs .
11. #d0f0ff will be used to represent pending CDAs .
12. #ffceff will be used to represent replanned CDAs

13. The following information will be displayed in tabular format.

Status:- This is the interim status of the CDAs and categorized as
 Done.
 Not started
 Started
This status of CDAs will be changed dynamically. And this status also
Reflected in detailed CDA page.

14. Container Size.

15. Visit No. This No. comes directly from the calling page. This no. is for
particular CDA This no shows the sequence of execution of the CDAs.

16. Trip No. Trip No shows sequential trip of the Prime Mover in a planning day.
17. Premise. This field keeps track of destination of prime mover in a particular
time.
18. Visit start date. This field keeps track of the date on which the Prime Mover
starts its its visit.
19. Visit start time. This field keeps track of the time at which the Prime Mover
starts its its visit from a particular premise.
20. Start trailer size. This field will be filled up automatically depending on the cda
type
21. Start trailer No. This field will be filled up automatically depending on the cda

150
 25. Remarks

13.2.41 View Status for CDAs

Page Id: 48-00 Page Name: View Status for CDAs
Style Sheet: Called from: Assignment of Trailer to Prime
Mover
Screenshot

Functionality:

1. This page will be accessible to planner to select the Prime Mover, that the
planner wants
to see the status of a particular CDA related to that selected Prime Mover.
2. This page will have the following controls
3. A LABEL to display current Date.
4. Two TEXTBOX to insert Planning Time in (hh:mm) format
5. A SELECTION BOX to select prime mover. The selection will be database
driven.
6. A BUTTON - Mark/View Status will display the page in which the user can
update the interim status of the CDA execution.

Remarks

151
13.2.42 View status of CDAs Assigned To a particular Prime
Mover.
Page Id: 48-00 Page Name: View Status of CDAs Assigned To
Prime Mover PM468
Style Sheet: Called from: Accountant Home Page
Screenshot

152
 Functionality:

1. This page will be accessible to planner.

2. .This page will have the following controls

3. A LABEL to display current Date.

4. Two TEXTBOX to insert Planning Time in (hh:mm) format.
5. The following information will be displayed in tabular format.

♦ Serial No to represent the sequence.

♦ CDA No - it is a machine generated number and will be
hyperlinked. On clicking it will display the detailed
information about the particular CDA.
♦ Visit No – it is the sequence number in which a prime mover will perform different
CDAs. There will be text box to enter the number and planner will give it.
♦ Planned Departure Time – A TEXT BOX to display the planned departure time for
a a particular CDA . This field is not editable. This field directly comes from plan
table
♦ Planned Arrival Time - A TEXT BOX to display the planned Arrival time for a a
particular prime mover after executing a particular CDA. This field is also not
editable. This field directly comes from plan table
♦
♦ Actual Departure Time - A TEXT BOX to enter the Actual departure time for a a
particular CDA . This field is editable..
♦ Actual Arrival Time - A TEXT BOX to enter the the Actual Arrival time for a a
particular CDA . This field is editable..
♦ Execution – the status of execution .
 Done. ( means cda execution is complete and assigned prime mover
arrives at the base .)
 Not started ( means cda execution is not started from the base at all ,
but it is
assigned to a particular prime mover )

 Started ( means cda execution is started from the base but it is not
complete yet .)

Remarks

13.2.43 View Plan for a particular Prime Mover

Page Id: 48-00 Page Name: View Plan for Prime Movers
Style Sheet: Called from: Assignment of Trailer to Prime
Mover PM464

153
 Screenshot

Functionality:

1. This page will be accessible to planner to select the Prime Mover, that the
planner wants
to view the plan for a particular Prime Mover , that means all the CDAs
attached to that
selected Prime Mover.
2. This page will have the following controls

♦ A LABEL to display current Date.

♦ Two TEXTBOX to insert Planning Time in (hh:mm) format
♦ A SELECTION BOX to select prime mover. The selection will be database driven.
♦ A BUTTON – View Plan to view the plan for a selected Prime Mover.

Remarks

13.2.44 View Plan for a particular Prime Mover (Showing Details)

Page Id: 48-00 Page Name: View Plan for Prime Mover PM468
Style Sheet: Called from: View Plan for Prime Movers

154
Screenshot

Functionality:

1. This page will be accessible to planner to assign trailers to a particular

prime mover.
2. This page will have the following controls.
♦ A LABEL to display current Date.
♦ Two TEXTBOX to insert Planning Time in (hh:mm) format
♦ The following information will be displayed in tabular format.
♦ Status – the status of a particular CDA.
♦ Container Size.
♦ Container No.
♦ Driver.
♦ Visit No.
♦ Premise.
♦ Visit start date.
♦ Visit start time.
♦ Start trailer size.
♦ Start trailer No.
♦ End trailer size.
♦ End trailer No.
♦ BUTTON
♦ Back – to return to the view plan page and can select any other Prime Mover.

3. The record set will be broken into several pages ( number of pages will be
calculated
Dynamically ) . links will be given according to dynamic numbers. e.g. let
suppose that there 20 CDAs are assigned to a particular prime mover . Then we may
divide the total records into 10 parts and show them in 10 different pages with 2 cdas at
a time. And current page will be displayed as bold.

155
 Remarks

13.2.45 Update Plan For CDAs

Page Id: 48-00 Page Name: Update Plan For CDAs
Style Sheet: Called from: View Plan for Prime Movers
Screenshot

156
Functionality:
1. This Page is accessible by the planner and the administrator to make plan
for different CDAs .
2. This page have the following controls.
♦ A LABEL to display current Date.
♦ Two TEXTBOX to insert Planning Time in (hh:mm) format
♦ A SELECTION BOX to select prime mover. The selection will be database driven.
When a particular Prime Mover will be selected, the corresponding CDAs that has
been assigned to the particular Prime Mover and will be displayed with a check in
the Allocate column.
♦ The availability of prime mover in different shifts will be displayed in tabular
format, after selecting a particular prime mover. It will show in which shift the
prime mover will be available.
♦ A SELECTION BOX to select shift1 driver. The selection will be database driven.
Depending upon the shift of selected prime mover the driver should be chosen.
♦ A SELECTION BOX to select shift2 driver. The selection will be database driven.
Depending upon the shift of selected prime mover the driver should be chosen.
♦ A SELECTION BOX to select shift3 driver. The selection will be database driven.
Depending upon the shift of selected prime mover the driver should be chosen.
♦ Three different TEXT BOXES are there to represent the colour code for different
types of CDA .
♦ Floralwhite will be used to represent new CDAs .
♦ #d0f0ff will be used to represent pending CDAs .
♦ #ffceff will be used to represent replanned CDAs
♦ The following information will be displayed in tabular format.
♦ Serial No to represent the sequence.
♦ CDA No - it is a machine generated number and will be hyperlinked. On clicking it
will display the detailed information about the particular CDA.
♦ B2B CDA No. – If there is a B2B CDA for the particular current CDA, then this
column contains the corresponding B2B CDA number and this will be hyperlinked
to get the detailed information about that particular CDA.
♦ Visit No – it is the sequence number in which a prime mover will perform different
CDAs. There will be text box to enter the number and it will be given by planner.
♦ Order Type – it represents the type of order. The different types of orders are :
♦ Direct Delivery.
♦ Direct Collection.
♦ Direct Delivery & Direct Collection.
♦ Direct Collection & Direct Delivery.
♦ IMPEX Type –
♦ Export.
♦ Import.
♦ Consign Type - it represents the nature of goods the consignment is handling.
According to the types there are different consignment types.
• Normal.
• Perishable.
• Dangerous.

157
 o Offload - it will represent whether offload is required or not. It is a
Boolean field.
♦ ‘Y’ for offload required.
♦ ‘N’ for offload not required.
o Side Loader –it will represent whether side loader option is required
or not. It is a Boolean field.
♦ ‘Y’ for side loader option required.
♦ ‘N’ for side loader option not required.
o Required Date – it is the date specified by the customer, on which
the work is to be done.
o Required Time - it is the time of a particular date specified by the
customer, when he/she wants the service.
o ETA Date – it is expected time of arrival of the vessel.
o ETA Time - it is expected time of arrival of the vessel.
o From - it represents the premise form where the consignment will
be carried.
o To - it represents the premise where the consignment is to be
carried.
o Diversion –
o Container Size - the type of container.
♦ 20’.
♦ 40’.
o Ageing - the number of days delayed from the required date.
o Replan Date - if the customer wants to change the required date of
a particular order after generation of CDA or under any
unnecessary circumstance, the date is changed by the
planner. A TEXT BOX is there to do the job. It should be
kept in mind that replanned date should not less than
required date.
o Allocate - A CHECK BOX is there to allocate a CDA to a
particular prime mover.
➘ BUTTON –
o Save Allocation – On clicking …………….
o Assign Trailer - On clicking this button Assignment of Trailer to
Prime Mover page will come and the assignment will be
done.
3. When it is needed to update any plan pertaining to a particular Prime Mover, the
Check Box in the Allocate column and Visit No entry should be updated. By
checked or unchecked the Check Box and change the Text Box entry plan can be
updated.

Remarks

158
13.2.46 Cancel Plan for CDAs
Page Id: 48-00 Page Name: Cancel Plan for CDAs
Style Sheet: Called from: Planner’s home page
Screenshot

Functionality:

1.This page will be accessible to planner to cancel plan for a particular Prime
Mover.
2.This page will have the following controls

➘ A LABEL to display current Date.

➘ Two TEXTBOX to insert Planning Time in (hh:mm) format
➘ A SELECTION BOX to select prime mover. The selection will be database
driven. To cancel a plan the corresponding Prime Mover should be selected
and then press the button to perform the job.
➘ A BUTTON - Cancel Plan.
• If any of the CDAs assigned to a Prime Mover has not
been executed then it is possible to cancel the total plan for a
particular Prime Mover. But if started then cancel plan is not
possible. A suitable message should be displayed that the
planner has to go to update plan page.

Remarks

13.2.47 Date Wise Billing Information – Request Page (Customer

Point Of View)
Page Id: 28-00 Page Name: DATE WISE BILLING INFORMATION –
REQUEST PAGE
(CUSTOMER POINT OF VIEW)
Style Sheet: Called from: CUSTOMER HOME PAGE

159
 Screenshot

Functionality:

1. This page will be accessible to Customer as well as administrator to submit

query for getting Date-wise Billing Information of the customer.
2. This page will have the following controls

 A TEXTBOX to enter From Date in (dd-mm-yyyy) format

 A TEXTBOX to enter To Date in (dd-mm-yyyy) format
 A COMBOBOX to select payment status(all,full payment done,part payment
done,No payment done)
 A BUTTON (get invoice) to retrieve Invoice Details from the database. The
system will retrieve Invoices pertaining to the Customer who has
logged on for the Date Range specified. After pressing the button customer
will see the following information in the next page:
• Invoice No.
• Invoice date
• Request No.
• Order No.
• Invoice Value
• Amount Received
• Amount Due
Remarks
3.

13.2.48 Date Wise Billing Information – Response Page

(Customer Point Of View)
Page Id: 29-00 Page Name: DATEWISE BILLING INFORMATION –
RESPONSE PAGE
(CUSTOMER POINT OF VIEW)
Style Sheet: Called from: DATE WISE BILLING INFORMATION –
REQUEST PAGE

160
 Screenshot

Functionality:

 This page will be displayed to Customers in response to customer request for

getting Date wise Invoice information.
 This page will display the following information in a tabular format
• Invoice No.
• Invoice date
• Request No.
• Order No.
• Invoice Value
• Amount Received
• Amount Due
 Here Order No. will be hyperlinked, on clicking the “Order Details For Billing”
Page will be appeared.
 If no data found, then proper msg will be displayed.
Remarks

13.2.49 Order Details For Billing(Customer Point Of View)

Page Id: 30-00 Page Name: ORDER DETAILS FOR BILLING
(CUSTOMER POINT OF VIEW)
Style Sheet: Called from: DATE WISE BILLING INFORMATION –
RESPONSE PAGE

161
 Sreenshot

Functionality:

 This page will be displayed to Customers in response to customer request for

getting Date wise Invoice information and order details for a particular order.
 This page will display the following information in a tabular format
• Request No.
• Order No.
• Required Date
• Execution Date
• B To B Order No.
• Order Date
• Service Type
o Diversion
o Delivery
o Offload
• Rate
Remarks

13.2.50 Order Wise Billing Information – Request Page (Customer

Point Of View)

Page Id: 31-00 Page Name: ORDER WISE BILLING INFORMATION –

REQUEST PAGE
(CUSTOMER POINT OF VIEW)
Style Sheet: Called from: CUSTOMER HOME PAGE

162
 Screenshot

Functionality :
1. This page will be accessible to Customer as well as administrator to submit
query for getting Order wise Billing Information of the customer.
2. This page will have the following controls

 A COMBOBOX to select Request Number. This COMBOBOX will

be populated from the database with Request Numbers
pertaining to the Customer who has logged on.
 A COMBOBOX to select Order Number of the particular
request. This COMBOBOX will be dynamically populated from
the database with Order Numbers pertaining to the Request
Number selected by the Customer.
 A BUTTON (get invoice)to retrieve Invoice Details from the
database. The system will retrieve Invoices pertaining to the
Request Number and the Order Number/s selected.
 After pressing the button customer will see the following
information in the next page.

• Request No.
• Order No.
• Required Date
• Execution Date
• B To B Order No.
• Order Date
• Service Type
o Diversion
o Delivery
o Offload
• Rate

Remarks

13.2.51 Order Wise Billing Information – Response Page

(Customer Point Of View)
Page Id: 32-00 Page Name: ORDER WISE BILLING INFORMATION –
RESPONSE PAGE (CUSTOMER POINT
OF VIEW)
Style Sheet: Called from: ORDERWISE BILLING INFORMATION –

163
 REQUEST PAGE
Screenshot

Functionality:

 This page will be displayed to Customers in response to customer request for

getting Date wise Invoice information and order details for a particular order.
 This page will display the following information in a tabular format
• Request No.
• Order No.
• Required Date
• Execution Date
• B To B Order No.
• Order Date
• Service Type
o Diversion
o Delivery
o Offload
• Rate
 If no data found, then proper msg will be displayed.
Remarks

13.2.52 Customer Wise Billing Information-Request Page

Page Id: 43-00 Page Name: CUSTOMER WISE BILLING
INFORMATION-REQUEST PAGE
(ACCOUNTANT POINT OF VIEW)
Style Sheet: Called from: ACCOUNTANT HOME PAGE

164
Screenshot

Functionality:

1. This page will be accessible to Accountant as well as administrator to

submit query to get the information about orders status customer wise.
2. This page will have the following controls

 A COMBOBOX to select Customer Name to get all order details of the particular
customer within a date range. This COMBOBOX will be dynamically populated from
the database with Customer Name pertaining to the Customer Name selected by the
Accounant.
 A TEXTBOX to enter From Date in (dd-mm-yyyy) format
 A TEXTBOX to enter To Date in (dd-mm-yyyy) format
 A BUTTON (Get Invoice) to retrieve order Details from the database
customerwise.The system will retrieve orders pertaining to the Accounant who has
logged on for the Date Range specified. After pressing the button accounant will
see the following information in the next page:
• Request No.
• Order Date.
• Order No.
• Customer ID
• Customer Name
• Invoice No.
• Invoice Date
• Payment Status
• Amount

Remarks

165
13.2.53 Customer Wise Billing Information-Response Page
Page Id: 44-00 Page Name: CUSTOMER WISE BILLING
INFORMATION-RESPONSE PAGE
(ACCOUNANT POINT OF VIEW)
Style Sheet: Called from: CUSTOMER WISE BILLING
INFORMATION-REQUEST PAGE
Screenshot

Functionality:

1. This page will be displayed to Accountant in response to Accountant’s

request about order details of a particular customer.
2.This page will display the following information in the tabular format.

• Customer ID
• Customer Name
• Request No.
• Order No.
• Order Date.
• Invoice No.
• Invoice Date
• Invoice value
• Amount received
• Amount Due

Remarks

13.2.54 Customer Order Details

Page Id: 45-00 Page Name: CUSTOMER ORDER DETAILS
(ACCOUNANT POINT OF VIEW)
Style Sheet: Called from: CUSTOMER WISE BILLING
INFORMATION-RESPONSE PAGE

166
 Screenshot

Functionality:

1. This page will be displayed to Accountant in response to Accountant’s

request about a particular order details of a particular customer.
2.This page will display the following information in the tabular format.

• Request No.
• Order No.
• Required Date
• Execution Date
• B To B Order No.
• Order Date
• Service Type
o Diversion
o Delivery
o Offload
• Rate
Remarks

13.2.55 Date Wise Billing Information – Request Page

(Accountant Point Of View) – Not Required
Page Id: 46-00 Page Name: DATE WISE BILLING INFORMATION –
REQUEST PAGE (ACCOUNTANT POINT
OF VIEW)
Style Sheet: Called from: Accountant Home Page

167
 Screenshot

Functionality
1.This page will be accessible to Accountant as well as administrator to submit
query for Date-wise Billing Information
2.This page will have the following controls
 A TEXTBOX to enter From Date in (dd-mm-yyyy) format
 A TEXTBOX to enter To Date in (dd-mm-yyyy) format
 A COMBOBOX to select payment status(all,full payment done,part payment
done,No payment done)
 A BUTTON (get invoice) to retrieve Invoice Details from the database. The
system will retrieve Invoices pertaining to the Customer who has logged on for the
Date Range specified. After pressing the button customer will see the following
information in the next page:
• Invoice No.
• Request No.
• Order No.
• Required Date
• Date Of Order Execution
• Invoice Date
• Value of Invoice
• Rate
• Aging
• Nature of Service
• Payment Status
Remarks
4.

13.2.56 Date Wise Billing Information – Response Page

(Accountant Point Of View) – Not Required
Page Id: 47-00 Page Name: DATE WISE BILLING INFORMATION –
RESPONSE PAGE (ACCOUNTANT POINT
OF VIEW)
Style Sheet: Called from: DATE WISE BILLING INFORMATION –
REQUEST PAGE

168
 Screenshot

Functionality:
 This page will be displayed to Accountant in response to accountant’s request
for Date wise Invoice information.
 This page will display the following information in a tabular format
• Invoice No.
• Invoice date
• Request No.
• Order No.
• Invoice Value
• Amount Received
• Amount Due
 Here Order No. will be hyperlinked, on clicking ‘Order Details for Billing’ page
will be appeared.
 If no data found, then proper msg will be displayed.
Remarks

13.2.57 Order Details For Billing(Accountant Point Of View)

Page Id: 30-00 Page Name: ORDER DETAILS FOR BILLING
(ACCOUNTANT POINT OF VIEW)
Style Sheet: Called from: DATE WISE BILLING INFORMATION –
RESPONSE PAGE
Sreenshot

169
 Functionality:

 This page will be displayed to Accountant in response to customer request for

getting Date wise Invoice information and order details for a particular order.
 This page will display the following information in a tabular format
• Request No.
• Order No.
• Required Date
• Execution Date
• B To B Order No.
• Order Date
• Service Type
o Diversion
o Delivery
o Offload
• Rate
Remarks

13.2.58 Order Wise Billing Information – Request Page

(Accountant Point Of View)
Page Id: 49-00 Page Name: ORDER WISE BILLING INFORMATION –
REQUEST PAGE (ACCOUNTANT POINT
OF VIEW)
Style Sheet: Called from: ACCOUNTANT HOME PAGE

170
 Screenshot

Functionality :

1. This page will be accessible to Accountant as well as administrator to submit

query for getting Order wise Billing Information of the customer.
2. This page will have the following controls

 A COMBOBOX to select Request Number. This COMBOBOX will

be populated from the database with Request Numbers
pertaining to the Customer who has logged on.
 A COMBOBOX to select Order Number of the particular
request. This COMBOBOX will be dynamically populated from
the database with Order Numbers pertaining to the Request
Number selected by the Customer.
 A BUTTON (get invoice)to retrieve Invoice Details from the
database. The system will retrieve Invoices pertaining to the
Request Number and the Order Number/s selected.
 After pressing the button customer will see the following
information in the next page.

• Request No.
• Order No.
• Required Date
• Execution Date
• B To B Order No.
• Order Date
• Service Type
o Diversion
o Delivery
o Offload
• Rate

Remarks

13.2.59 Order Wise Billing Information – Response Page

(Accountant Point Of View)
Page Id: 50-00 Page Name: ORDER WISE BILLING INFORMATION –
RESPONSE PAGE (ACCOUNTANT POINT
OF VIEW)

171
 Style Sheet: Called from: ORDER WISE BILLING INFORMATION-
REQUEST
PAGE
Screenshot

Functionality:

 This page will be displayed to Accountant in response to accountant request for

getting Date wise Invoice information and order details for a particular order.
 This page will display the following information in a tabular format
• Request No.
• Order No.
• Required Date
• Execution Date
• B To B Order No.
• Order Date
• Service Type
o Diversion
o Delivery
o Offload
• Rate
 If no data found, then proper msg will be displayed.
Remarks

13.2.60 Payment Status

Page Id: 51-00 Page Name: PAYMENT STATUS (ACCOUNTANT
POINT OF VIEW)

172
13.2.61 Order Details
Page Id: 52-00 Page Name: ORDER DETAILS (ACCOUNTANT POINT
OF VIEW)
Style Sheet: Called from: PAYMENT STATUS
Screenshot
Screenshot

Functionality:

 This page will be displayed to Accountant in response to accountant request for

getting Date wise Invoice information and order details for a particular order.
 This page will display the following information in a tabular format
• Request No.
• Order No.
• Required Date
• Execution Date
• B To B Order No.
• Order Date
• Service Type
o Diversion
o Delivery
o Offload
• Rate
 If no data found, then proper msg will be displayed.
Remarks

173
13.2.62 Payment Details
Page Id: 52-00 Page Name: PAYMENT DETAILS (ACCOUNTANT
POINT OF VIEW)
Style Sheet: Called from: PAYMENT STATUS
Screenshot

174
 Functionality:

 This page will be displayed to Accountant in response to accountant request for

getting payment details for a particular order.
 Invoice No.,Order No.,Request No.,Bill Date,BillValue,Amount Due are displayed
from the database.
 A TEXTBOX to enter Amount Received.
 A TEXTBOX to enter Draft/Cheque No.
 A TEXTBOX to enter Draft/Cheque Date
 A TEXTBOX to enter Valid for (Months)
 A TEXTBOX to enter Drawee Bank
 A TEXTBOX to enter Branch
 A COMBOBOX to select mode of payment (cash,cheque,draft)
 A BUTTON (Submit) to enter the Payment Details to the database.
 A BUTTON (Reset) to reset all the values.
 This page will display the following information in a tabular format
 Payment Details
• Invoice No.
• Request No.
• Order No.
• Bill Date
 Bill Details
• Mode Of Payment
• Bill Value
• Amount Due
• Date Of Receipt
• Amount Received
 Draft/Cheque Details
• Draft/Cheque No.
• Draft/Cheque Date
• Valid For (Months)
• Drawee Bank
• Branch
 If no data found, then proper msg will be displayed.
Remarks

13.2.63 List of Customers

Page Id: 48-00 Page Name: List of Customers
Style Sheet: Called from: Admin Home Page

175
 Screenshot

Functionality:
1. This page will be accessible by the administrator.
2. This page will display the list of customers with the following attributes.
 Customer Code.
 Customer Name.
 Customer Address.
 Customer City.
 Customer Country.
 Customer Phone.
 Customer Contact Person.
 Customer Email.
 Customer Credit Rating.
3. Report Run Date will display the date on which the report is generating.
Remarks

13.2.64 List Of Internal Users

Page Id: 48-00 Page Name: List Of Internal Users
Style Sheet: Called from: Admin Home Page
Screenshot

176
 Functionality:
1. This page will be accessible by the administrator.
2. This page will display the list of internal users (Employee) with the
following attributes.
 Employee Code.
 Employee Name.
 Employee Designation.
 Date Of Joining.
 User Role.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.65 List Of Prime Mover Commissioned

Page Id: 48-00 Page Name: List of Prime Mover Commissioned
Style Sheet: Called from: Admin Home Page
Screenshot

177
 Functionality:

5. This page will be accessible to administrator to submit query to get the list
of Prime Mover commissioned during the specified period.
6. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Prime Mover commissioned during
the specified Date given by Administrator .The information related to
commissioned Prime Mover during that period will come from the database.
After pressing the button administrator will see the following information in
the next page:
• PrimeMover No.
• Date of Commissioning.
• Registration No.
• Model No.
• Engine No.
• Chasis No.
• Manufacturer Name.

Remarks

13.2.66 List Of Prime Mover Commissioned Details

Page Id: 48-00 Page Name: List of Prime Movers Commissioned
Details
Style Sheet: Called from: List of Prime Mover Commissioned
Screenshot

178
 Functionality:
1. This page will be displayed to the administrator.
2. This page will display the following information
• PrimeMover No.
• Date of Commissioning.
• Registration No.
• Model No.
• Engine No.
• Chasis No.
• Manufacturer Name.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.67 List Of Trailer Commissioned

Page Id: 48-00 Page Name: List of Trailer Commissioned
Style Sheet: Called from: Admin Home Page
Screenshot

179
 Functionality:
1. This page will be accessible to administrator to submit query to get the
list of Trailer commissioned during the specified period.
2. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Trailer commissioned during the
specified Date given by Administrator .The information related to
commissioned Trailer during that period will come from the database. After
pressing the button administrator will see the following information in the
next page:
• Trailer No.
• Trailer Size
• Date of Purchase.
• Date of Commissioning.
• Purchase Price
• Side Loader Option
• Manufacturer Name.

Remarks

13.2.68 List Of Trailer Commissioned Details

Page Id: 48-00 Page Name: List of Trailer Commissioned
Details
Style Sheet: Called from: List of Trailer Commissioned
Screenshot

180
 Functionality:

1. This page will be displayed to the administrator.

2. This page will display the following information
• Trailer No.
• Trailer Size
• Date of Purchase.
• Date of Commissioning.
• Purchase Price
• Side Loader Option
• Manufacturer Name.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.69 List Of Scrapped Trailers

Page Id: 48-00 Page Name: List of Scrapped Trailers
Style Sheet: Called from: Admin Home Page
Screenshot

181
 Functionality:
1. This page will be accessible to administrator to submit query to get the
list of Scrapped Trailers during the specified period.
2. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Scrapped Trailers during the
specified period given by Administrator .The information related to scrapped
Trailer during that period will come from the database. After pressing the
button administrator will see the following information in the next page:
• Trailer No.
• Trailer Size
• Date of Purchase.
• Date of Commissioning.
• Purchase Price
• Side Loader Option
• Date of Decommissioning
• Date of Scrap
• Manufacturer Name.

Remarks

13.2.70 List Of Scrapped Trailers Details

Page Id: 48-00 Page Name: List of Scrapped Trailers Details
Style Sheet: Called from: List of Scrapped Trailers
Screenshot

182
 Functionality:
1. This page will be displayed to the administrator.
2. This page will display the following information
• Trailer No.
• Trailer Size
• Date of Purchase.
• Date of Commissioning.
• Purchase Price
• Side Loader Option
• Date of Decommissioning
• Date of Scrap
• Manufacturer Name.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.71 List Of Scrapped PMs

Page Id: 48-00 Page Name: List of Scrapped PMs
Style Sheet: Called from: Admin Home Page
Screenshot

183
 Functionality:
1. This page will be accessible to administrator to submit query to get the
list of Scrapped PMs during the specified period.
2. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Scrapped PMs during the specified
period given by Administrator .The information related to scrapped PM
during that period will come from the database. After pressing the button
administrator will see the following information in the next page:
• Date of Purchase.
• Date of Commissioning.
• Registration No.
• Model No.
• Engine No.
• Chasis No.
• Date of Decommissioning
• Date of Scrap
• Scrap Value

Remarks

13.2.72 List Of Scrapped Prime Mover Details

Page Id: 48-00 Page Name: List of Scrapped Prime Movers
Details
Style Sheet: Called from: List of Scrapped PMs
Screenshot

184
 Functionality:
1. This page will be displayed to the administrator.
2. This page will display the following information
• Date of Purchase.
• Date of Commissioning.
• Registration No.
• Model No.
• Engine No.
• Chasis No.
• Date of Decommissioning
• Date of Scrap
• Scrap Value
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.73 Location Wise Customer List

Page Id: 48-00 Page Name: Location Wise Customer List
Style Sheet: Called from: Planner Home Page
Screenshot

185
 Functionality:

1. This page will be accessible to Planner to submit the query to get the
list of Customer depending upon the selection of the locations by
Planner.
2. This page will have the following controls

 A LISTBOX having multiple selection property to choose more than one

location.
 A BUTTON (get list) to retrieve the list of Customer from database with the
following information. After pressing the button administrator will see the
following information in the next page:
• Location Name.
o Customer Name.
o Customer Billing Address.
o Customer Person.
o Customer Premises.

Remarks

13.2.74 Location Wise Customer List Details

Page Id: 48-00 Page Name: Location Wise Customer List Details
Style Sheet: Called from: Location Wise Customer List
Screenshot

186
 Functionality:
1. This page will be displayed to the administrator.
2. This page will display the following information
• Location Name.
o Customer Name.
o Customer Billing Address.
o Customer Person.
o Customer Premises.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.75 List Of Break Down Prime Mover

Page Id: 48-00 Page Name: List Of Break Down Prime Mover
Style Sheet: Called from: Planner Home Page
Screenshot

187
 Functionality:
1. This page will be accessible to Planner to submit query to get the list of
Breakdown Prime Mover during the specified period.
2. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Breakdown
Prime Mover during the specified period given by Planner .The
information related to Breakdown Prime Mover during that period
will come from the database. After pressing the button
administrator will see the following information in the next page:
• Prime Mover No.
• Registration No.
• Model No.
• Date of Break Down.
• Cause of Break Down.
• Driver Name.
• Maintenance Station.

Remarks

13.2.76 List Of Break Down Prime Mover Details

Page Id: 48-00 Page Name: List Of Break Down Prime
Mover Details
Style Sheet: Called from: List Of Break Down Prime
Mover
Screenshot

188
 Functionality:
1. This page will be displayed to the administrator.
2. This page will display the following information
• Prime Mover No.
• Registration No.
• Model No.
• Date of Break Down.
• Cause of Break Down.
• Driver Name.
• Maintenance Station.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.77 Prime Mover Maintenance

Page Id: 48-00 Page Name: Prime Mover Maintenance
Style Sheet: Called from: Planner Home Page
Screenshot

189
 Functionality:
1. This page will be accessible to Planner to submit query to get the list of
Prime Mover that have gone under maintenance during the specified
period.
2. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Prime Mover
that have gone under maintenance during the specified period
given by Planner .The information related to Prime Mover
maintenance during that period will come from the database.
After pressing the button administrator will see the following
information in the next page:
• Prime Mover No.
• Registration No.
• Model No.
• From Date.
• To Date.
• Cause Of Maintenance.
• Maintenance Station.

Remarks

13.2.78 Prime Mover Maintenance Details

Page Id: 48-00 Page Name: Prime Mover Maintenance Details
Style Sheet: Called from: Prime Mover Maintenance
Screenshot

190
 Functionality:
1. This page will be displayed to the administrator.
2. This page will display the following information
• Prime Mover No.
• Registration No.
• Model No.
• From Date.
• To Date.
• Cause Of Maintenance.
• Maintenance Station.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.79 List Of Executed CDAs

Page Id: 48-00 Page Name: List of Executed CDA
Style Sheet: Called from: Planner Home Page
Screenshot

191
 Functionality:
1. This page will be accessible to Planner to submit query to get the list of
Executed CDA during the specified period.
2. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Executed CDA
during the specified period given by Planner .The information
related to Executed CDA during that period will come from the
database. After pressing the button administrator will see the
following information in the next page:
• CDA No.
• Request No.
• Order No.
• Impex Type.
• Required Date.
• Execution Date.
• Customer Name.
• From Premise.
• To Premise.
• PM_No.
• Driver Name.

Remarks

13.2.80 List Of Executed CDA Details

Page Id: 48-00 Page Name: List of Executed CDA Details
Style Sheet: Called from: List of Executed CDA
Screenshot

192
 Functionality:
1. This page will be displayed to the administrator.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Impex Type.
• Required Date.
• Execution Date.
• Customer Name.
• From Premise.
• To Premise.
• PM_No.
• Driver Name.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.81 List Of Replanned CDA

Page Id: 48-00 Page Name: List of Replanned CDA
Style Sheet: Called from: Planner Home Page
Screenshot

193
 Functionality:
1. This page will be accessible to Planner to submit query to get the list of
Replanned CDA during the specified period.
2. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Replanned
CDA during the specified period given by Planner .The
information related to Replanned CDA during that period will
come from the database. After pressing the button planner will
see the following information in the next page:
• CDA No.
• Request No.
• Order No.
• Impex Type.
• Required Date.
• Replanned Date.
• Execution Date.
• Customer Code.
• Customer Name.
• From Premise.
• To Premise.

Remarks

13.2.82 List Of Replanned CDA Details

Page Id: 48-00 Page Name: List of Replanned CDA Details
Style Sheet: Called from: List of Replanned CDA
Screenshot

194
 Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Impex Type.
• Required Date.
• Replanned Date.
• Execution Date.
• Customer Code.
• Customer Name.
• From Premise.
• To Premise.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.83 List Of Cancelled Orders

Page Id: 48-00 Page Name: List of Cancelled Orders
Style Sheet: Called from: Planner Home Page
Screenshot

195
 Functionality:
1. This page will be accessible to Planner to submit query to get the list of
Cancelled Order depending upon the selection of customer during the
specified period.
2. This page will have the following controls

 A SELECTIONBOX having multiple selection property to

select more than one customer to see the cancelled order of
those customers.
 A TEXTBOX to enter From Date.
 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Cancelled
Orders during the specified period of those specified customer
given by Planner .The information related to Cancelled Order
during that period will come from the database. After pressing
the button planner will see the following information in the next
page:
• Request No.
• Order No.
• Order Date.
• Customer Name.
• Cancellation Date.
• Cause of Cancellation.

Remarks

13.2.84 List Of Cancelled Orders Details

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders
Screenshot

196
 Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• Request No.
• Order No.
• Order Date.
• Customer Name.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.85 List Of Pending CDA

Page Id: 48-00 Page Name: List of Pending CDA
Style Sheet: Called from: Planner Home Page
Screenshot

Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Impex Type.
• Required Date.
• Ageing.
• Customer Name.
• From Premise.
• To Premise.
3. Report Run Date will display the date on which the report is generating.

Remarks

197
13.2.86 List Of Cancelled Orders
Page Id: 48-00 Page Name: List of Cancelled Orders
Style Sheet: Called from: Customer Home Page
Screenshot

Functionality:
1. This page will be accessible to Customer to submit query to get the list
of Cancelled Order during the specified period.
2. This page will have the following controls

 A TEXTBOX to enter From Date.

 A TEXTBOX to enter To Date.
 A BUTTON (get list) to retrieve the list of Cancelled
Orders during the specified period Customer .The information
related to Cancelled Order during that period will come from the
database. After pressing the button Customer will see the
following information in the next page:
• Request No.
• Order No.
• Order Date.
• Cancellation Date.
• Cause of Cancellation.

Remarks

13.2.87 List Of Cancelled Orders Details

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders

198
Screenshot

Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

Remarks

199
13.2.88 List Of Request
Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders
Screenshot

Functionality:
1. This page will be accessible to Customer to submit the query to get the list
of Request status submitted by that particular customer.
2. This page will have the following controls

 A LISTBOX having multiple selection property to choose more than one

Request.
 A BUTTON (get list) to retrieve the list of Request Status from database with
the following information. For a particular Request there may be several
Orders.After pressing the button customer will see the following information
in the next page:
• Request Date.
• Request No.
o Order No.
o Required Date.
o Order status.
o Execution Date.

Remarks

13.2.89 Request Status Details

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders

200
 Screenshot

Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.90 Payment Status Request

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders

201
 Screenshot

Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.91 Payment Status Details

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders
Screenshot

202
 Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.92 Account Invoice Payment Status

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders
Screenshot

Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.93 Invoice Payment Deatils

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders

203
 Screenshot

Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

Remarks

13.2.94 Generated Invoice Status

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders
Screenshot

Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

204
 Remarks

13.2.95 Generated Invoice Details

Page Id: 48-00 Page Name: List of Cancelled Orders Details
Style Sheet: Called from: List of Cancelled Orders
Screenshot

Functionality:
1. This page will be displayed to the Planner.
2. This page will display the following information
• CDA No.
• Request No.
• Order No.
• Cancellation Date.
• Cause of Cancellation.
3. Report Run Date will display the date on which the report is generating.

Remarks

205
13.3 Database Design

This section provides an insight into the database tables used by the Haulage
Management System.

13.3.1 User Master

Table Name User Master
Table This table contains the Master information of the
Description Users
Fields
Field Name Data Si Field Description
Type ze Level
Constr
aints
UID Varchar 20 Primary
User-ID of the Internal User
2 Key
Password Varchar 10 Password of the UID
2
User_Type Varchar 15 Admin/Planner/Acct/Customer
2
Validations & Table Level Constraints
Constraint Description
Name
UID UID is a primary key and holds unique records.
Password Password should be minimum 8 characters and
maximum 10 characters

13.3.2 Employee Master

Table Name Employee Master
Table This table contains the Master information of the
Description Internal Users
Fields
Field Name Data Si Field Description
Type ze Level
Constrai
nts
Emp_Code Varchar 10 Primary Employee Code
2 Key
Emp_Name Varchar 30 Employee Name
2
Emp_Desig Varchar 20 Employee Designation
2
UID Varchar 20 Foreign UID
2 Key

206
Validations & Table Level Constraints
Constraint Description
Name
Emp_Code Emp_Code is the Primary Key in the Employee Master
Table.
UID UID is the Foreign Key in the Employee Master Table
and corresponds to the primary key
UID in the User Master Table.

13.3.3 Role Master

Table Name Role Master
Table This table contains Master information of the Roles with
Description their IDs.
Fields
Field Name Data Si Field Description
Type ze Level
Constr
aints
Role_Id Varchar 10 PrimaryThis is the Role-id of the User
2 Key
Role_Name Varchar 15 This is the Role name of
2 Users.
Validations & Table Level Constraints
Constraint Description
Name
Role_ID Role_ID is the Primary Key in the Role Master Table.

13.3.4 User Role Map

Table User_Role_Map
Name
Table This table contains the information of the Users and
Descripti their respective roles.
on
Fields
Field Data Si Field Description
Name Type ze Level
Constra
ints
UID Varcha 20 Foreign This is the UID of the user.
r2 key
Role_Id Varcha 10 Foreign This is the Role-Id of the
r2 key user.
Validations & Table Level Constraints
Constrain Description
t Name

207
UID This is the foreign key referring only the employees in
the user master table
Role_Id This is the foreign key referred from the Role master
table

13.3.5 Functionality Master

Table Functionality Master
Name
Table This table contains the information of the pages .
Descriptio
n
Fields
Field Data Si Field Description
Name Type ze Level
Constra
ints
Page_Id Varcha 10 Primary This is ID of the page.
r2 Key
Page_Name Varcha 20 This is the name of the page.
r2
Validations & Table Level Constraints
Constraint Description
Name
Page_ID This is the Primary Key .

13.3.6 Functionality Role Map

Table Functionality_Role_Map
Name
Table This table contains the information of the Role and their
Descriptio functionalities .
n
Fields
Field Data Si Field Description
Name Type ze Level
Constra
ints
Page_Id Varcha 10 Foreign This is ID of the page.
r2 Key
Role_Id Varcha 10 Foreign This is Role-Id.
r2 Key
Validations & Table Level Constraints
Constraint Description
Name

208
Page-Id This is a foreign key.
This field references the Page-Id field of the Functionality
Master table.
Role-Id This is a foreign key.
This field references the Role-Id field of the Role Master
table.

13.3.7 Customer Master

Table Name Customer Master
Table This table contains master information of
Description customers.
Fields
# Field Name Data Siz Field Description
Type e Level
Constra
ints
1 Cust_Code Varchar2 10 Primary Code of customer
key
2 Cust_Name Varchar2 30 Name of the
Customer
3 UID Varchar2 20 Foreign UID of the
Key Customer
4 Cust_Address1 Varchar2 50 Address of
Customer
5 Cust_Address2 Varchar2 50 Address of
Customer
(optional)
6 C_City Varchar2 25 City of Customer
7 C_Country Varchar2 25 Country of
Customer
8 C_Fax Number 15 Fax Number of the
Customer
9 C_Email Varchar2 20 E-Mail of the
Customer
10 C_Phone Number 15 Phone Number of
Customer
11 C_Contact _Person Varchar2 30 Contact Person’s
name
of Customer.
12 C_Priority Number 2 Priority Of the
Customer
13 Credit_Limit Number 10 Credit limit of the
Customer

209
14 Credit_Rating Number 1 Credit Rating will
be between 0-9.
Poorest – 0
Best - 9
Validations & Table Level Constraints
Constraint Description
Name
Cust_Code Cust_Code is Primary key in Customer table and will
hold unique records.
UID UID is a foreign key.
It references the UID field of the User Master table.

13.3.8 Prime Mover Master

Table Name Prime-Mover Master

Table This table contains master information of Prime-Movers.
Description
Fields
# Field Name Data Siz Field Description
Type e Level
Constr
aints
01 PM_No Varcha 10 Primary PrimeMover Number
r2 key
02 Regn_No Varcha 10 Unique Prime Mover
r2 Registration Number
03 Regn_Year Numb 4 Year of registration of
er Prime Mover
04 Manufacturer Varcha 30 Manufacturer’s Name
r2 of Prime Mover
05 Model Varcha 6 Model number of
r2 vehicle
06 Engine_No Varcha 10 Unique Engine Number of Prime
r2 Mover
07 Chassis_No Varcha 10 Unique Chassis Number of Prime
r2 Mover
08 Price Numb 10, Price of purchase of
er 2 Prime Mover
09 DOP Date Purchase date of of Prime
Mover
10 Km_Travel_DOP Numb 5 Kilometers traveled at
er Purchase Date
11 DOC Date Date of
Commissioning of
Prime Mover

210
12 Km_Travel_DOC Numb 5 Kilometers traveled at Date
er of Commissioning
13 Decommissioned Varcha 3 Whether PrimeMover
r2 has been
decommissioned or
not
14 DOD Date Date of
Decommissioning of
Prime Mover
15 Km_Travel_DOD Numb 5 Kilometers traveled at Date
er of Decommissioning
16 Scrapped Varcha 3 Whether PrimeMover
r2 has been scrapped or
not
17 DOS Date Date of Scrap of Prime
Mover
18 Scrap_Val Numb 10, Scrap Value Of Prime
er 2 Mover
19 Weight Numb 6,2 Gross Weight Of Prime
er Mover
Validations & Table Level Constraints
Constraint Description
Name
PM_PK PM_PK is a Primary Key constraint in Prime Mover Master
Table that corresponds to PM_No field and will hold
unique records.
Regn_No Unique field in PrimeMover Master table.
Engine_No Unique field in PrimeMover Master table.
Chassis_No Unique field in PrimeMover Master table.

13.3.9 Trailer Master

Table Name Trailer Master
Table This table contains master information of Trailers.
Description
Fields
# Field Name Data Siz Field Description
Type e Level
Constr
aints
1. T_No Varchar 10 Primary Trailer Number
2 Key
2. T_Size Number 2 Size of Trailer
3. Manufacturer Varchar 30 Name of Manufacturer
2
4. Price Number 10,2 Purchase Price of Trailer
5. DOP Date Date of Purchase of Trailer

211
6. DOC Date Date of Commissioning of
Trailer
7. Decommissioned Varcha 3 Whether Trailer has been
r2 decommissioned or not
8. DOD Date Date of Decommissioning
of Trailer
9. Scrapped Varcha 3 Whether Trailer has been
r2 scrapped or not
10. DOS Date Date of Scrap of Trailer
11. Scrap_Val Numb 10, Scrap Value of Trailer
er 2
12. Weight Numb 6,2 Weight of Trailer in tonnes
er
13. Side_Loader Boolea 1 Whether Side-Loader is
n present or absent in trailer.
Validations & Table Level Constraints
Constraint Description
Name
Trailer_PK Trailer_PK is a Primary Key constraint in Trailer Master
Table that corresponds to T_No field and will hold unique
records.

13.3.10 Location Master

Table Location Master
Name
Table This table contains master information of
Description Locations.
Fields
# Field Name Data Siz Field Description
Type e Level
Constra
ints
1. Loc_Code Varchar 10 Primary Location Code
2 Key

212
2. Loc_Name Varchar 20 Location Name
2
3. Standard_Time Date Standard Time of
Location.
4. Latitude_Deg Numb 3 Degree of Latitude
er of Location
5. Latitude_Min Numb 2 Minutes of Latitude
er of Location
6. Latitude_Sec Numb 2 Seconds of Latitude
er of Location
7. Latitude_Dir Varch 1 Direction of Latitude
ar2 (N/S)
Longitude_Deg Numb 3 Degree of Longitude
8. er of Location
Longitude_Min Numb 2 Minutes of
9. er Longitude of
Location
10. Longitude_Sec Numb 2 Seconds of
er Longitude of
Location
11. Longitude_Dir Varch 1 Direction of
ar2 Longitude (E/W)
12. Local_X_Coord Numb 3 Local X Coordinate
er of Location
13. Local_Y_Coord Numb 3 Local Y Coordinate
er of Location
14. Local_Out Boolea 1 Denotes Local trip
n for TRUE and
Outstation trip for
FALSE
Validations & Table Level Constraints
Constraint Description
Name
Loc_PK Loc_PK is a Primary Key constraint in Location
Master Table that corresponds to Loc_Code field
and will hold unique records.

13.3.11 Port Master

Table Name Port Master

213
Table This table contains master information of Ports.
Description
Fields
# Field Name Data Siz Field Description
Type e Level
Constr
aints
1. Port_Code Varchar2 10 Primary Port Code
Key
2. Port_Name Varchar2 20 Name of Port
3. Port_Address1 Varchar2 50 Address of Port
4. Port_Address2 Varchar2 50 Address of Port
(optional)
5. Port_City Varchar2 25 City where Port is
located
6. Port_Country Varchar2 25 Country where Port is
located
7. Loc_Code Varchar2 10 Foreign Location Code Of Port
Key
8. Im_Open_Dang Date Import Opening Time
for Dangerous Cargo
9. Im_Open_Normal Date Import Opening Time for
Normal Cargo
10. Im_Open_Refrig Date Import Opening Time for
Refrigerated Cargo
11. Im_Close_Dang Date Import Closing Time for
Dangerous Cargo
12. Im_Close_Normal Date Import Closing Time for
Normal Cargo
13. Im_Close_Refrig Date Import Closing Time for
Refrigerated Cargo
14. Ex_Open_Dang Date Export Opening Time for
Dangerous Cargo
15. Ex_Open_Normal Date Export Opening Time for
Normal Cargo
16. Ex_Open_Refrig Date Export Opening Time
forRefrigerated Cargo
17. Ex_Close_Dang Date Export Closing Time for
Dangerous Cargo
18. Ex_Close_Normal Date Export Closing Time for
Normal Cargo
19. Ex_Close_Refrig Date Export Closing Time for
Refrigerated Cargo
20. Ex_Shut_Time Date Export Shut Time
Validations & Table Level Constraints
Constraint Description
Name

214
Port_PK Port_Code and Loc_Code fields together form the primary
key constraint and will be unique together.
Port_Lcode_F A Foreign Key constraint in Port Master Table ,where
K Loc_Code in Port table corresponds to Primary key
Loc_Code in Location Master table.

13.3.12 Driver Master

Table Name Driver Master
Table This table contains master information of Drivers.
Description
Fields
# Field Name Data Siz Field Description
Type e Level
Constr
aints
1. D_Code Varchar 10 Primary Code of Driver
2 Key
2. D_Name Varchar 30 Name of Driver
2
3. D_Age Number 2 Age of Driver
4. D_ Address1 Varchar 50 Address of Driver
2
5. D_ Address2 Varchar 50 Address of
2 Driver(optional)
6. D_City Varchar 25 City of Driver
2
7. D_Country Varchar 25 Country of Driver
2
8. D_Phone Numb 15 Phone no. of Driver
er
9. D_ Mobile_No Numb 12 Mobile no. of Driver
er
10. D_Passportno Varcha 10 Passport Number of
r2 Driver.
11. Join_Date Date Date of joining of
driver.
12. License_No Numb 15 LicenseNumber held
er by Driver
13. License_Validity_Dat Date License Validity Date
e of Driver
14. Accident_Rec Varcha 10 Accident Record of
r2 Driver
(Good/Bad/Best/Avera
ge)
15. Basic_Wage Numb 8,2 Basic Wages Of
er Driver

215
Validations & Table Level Constraints
Constraint Description
Name
Driver_PK A Primary Key constraint in Driver MasterTable that
corresponds to D_Code and will hold unique records for a
driver.

13.3.13 Premises Master

Table Name Premises Master
Table This table contains master information of Premises.
Description
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. Premises_Code Varchar2 10 Primary Premises Code
Key
2. Premise_Name Varchar2 20 Unique Name of Premises
3. P_Address1 Varchar2 50 Address of Premises
4. P_Address2 Varchar2 50 Address of Premises
(optional)
5. P_City Varchar2 25 City where Premises
is located
6. P_Country Varchar2 25 Country where
Premises is located
7. Loc_Code Varchar2 10 Foreign Location Code Of
Key Premises
8. Cust_Code Varchar2 10 Foreign Customer Code,if
Key Premises is a customer
premise.
9. Premise_Type Varchar2 1 Type Of Premise –
C,I,D,B
10. No_Shifts Number 1 Number of Shifts.
11. Shift1_Open_Time Date First Shift Opening Time
12. Shift1_Close_Time Date First Shift Closing Time
13. Shift2_Open_Time Date Second Shift Opening
Time
14. Shift2_Close_Time Date Second Shift Closing
Time
15. Shift3_Open_Time Date Third Shift Opening
Time
16. Shift3_Close_Time Date Third Shift Closing Time
17. Load_Time Varchar 10 Loading Time
2

216
18. Unload_Time Varchar 10 Unloading Time
2
19. Coupling_Time Varchar 10 Coupling Time
2
20. Decoupling_Time Varchar 10 Decoupling Time
2
Validations & Table Level Constraints
Constraint Description
Name
Premises_PK Premises_PK is a Primary Key constraint in Premises
Master Table and will hold unique records.
Ploc_FK A Foreign Key constraint in Premises Master Table ,where
Loc_Code in Premises table corresponds to Primary key
Loc_Code in Location Master table.
PCust_FK A Foreign Key constraint in Premises Master Table ,where
Cust_Code in Premises table corresponds to Primary key
Cust_Code in Customer Master table.

13.3.14 Service Rate Master

Table Name Service Rate Master
Table This table contains master information of
Description Service Rates.
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. Service_Code Varchar2 10 Primary Service Rate Code
Key
2. Service_Type Varchar2 100 Service Type
3. Service_Rate Number 8,2 Rate Of Service
4. UOM Varchar2 20 Unit of Measurement
Validations & Table Level Constraints
Constraint Description
Name
Serv_PK Serv_PK is a Primary Key constraint in Service Rate
Master Table and will hold unique records.

13.3.15 Parameter Master

Table Name Parameter Master
Table This table contains master information of Parameter.
Description
Fields

217
# Field Name Data Siz Field Description
Type e Level
Constrain
ts
1. Parameter_Code Varchar 10 Primary This is the code of
2 Key the parameter.
2. Parameter_Name Varchar 20 This is the name of
2 the parameter.
3. Value1 Varchar 10 Value of parameter
2
4. Value2 Varchar 10 Value of
2 parameter,if
parameter has more
than 1
value(Optional).
5. UOM Varchar 20 This is the Unit Of
2 Measurement.
Validations & Table Level Constraints
Constraint Description
Name
Param_PK Param_PK is the primary key in the Parameter Master Table
that corresponds to Parameter_Code field and will hold
unique records.

13.3.16 Distance Master

Table Name Distance Master
Table This table contains information about
Description distances between two
locations.
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. From_Prem Varchar2 10 Primary Location from which
Key distance is taken.
2. To_Prem Varchar2 10 Primary Location to which
Key distance is taken.
3. Distance Number 10,2 Distance between the
two locations.
4. Time Date Time taken to travel
between two
locations.
Validations & Table Level Constraints
Constraint Description
Name

218
Dist_PK Both From and To fields together will form the
Primary Key constraint in Distance Master Table and
will be unique.

13.3.17 Trailer Location

Table Trailer Location
Name
Table This table contains the present location of the
Description trailers along with the trailer number.
Fields
# Field Name Data Siz Field Description
Type e Level
Constra
ints
1. T_No Varchar2 10 Foreign Trailer Number
Key
2. Loc_Code Varchar2 10 Foreign Location Code
Key
Validations & Table Level Constraints
Constraint Description
Name
T_No Trailer number is the foreign key referred from
trailer master table.
Loc_Code Location code is the foreign key referred from
location master table.

13.3.18 Request Details

Table Name Request Details
Table This table contains detailed information about Request For
Description Transportation.
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. Request_No Varchar2 10 Primary Request Number
Key
2. Request_Date Date Request Date
3. Request_Status Varchar2 15 Status Of Request
4. Cust_Code Varchar2 10 Foreign Customer Code
Key
Validations & Table Level Constraints
Constraint Description
Name
Request_No Request_No is a Primary Key constraint in Request Table
and will hold unique records.

219
Cust_Code Cust_Code is a Foreign Key constraint in Request Table
and corresponds to Primary key Cust_Code in Customer
Master table.

13.3.19 Order Details

Table Name Order Details
Table This table contains detailed information about Orders.
Description
Fields
# Field Data Siz Field Level Description
Name Type e Constraints
1 Order_No Varchar 10 Primary Kay Order No. Unique for this
2 Table
2. Request_No Varchar 10 Foreign Key Foreign Key to Request
2 Details.
3. Order_Type Boolean Order Type (Simple or
Compound)
4. Order_Date Date 10 Date of Order
5. Order_Status Varchar 12 Status of Order(Executed
2 ,Not
Executed,Pending,Cancelled)
6 Cancellation Date Stores Date of Cancellation
Date
7 Cancel_Caus Varchar 50 Stores the reason of
e 2 cancellation
Validations & Table Level Constraints

Constrain Description
t Name
Ct_Reques Request_No is a Primary Key constraint in Request Table and will hold
t_No unique records.
Ct_Contain Container_No is a Foreign Key constraint in Request Table and corresponds
er_No to Primary key Container_No in Container Master table.
Consignm Consignment Type contain what type we used that is
ent Type (normal,perishable,dangerous)

Foreign Vessel_Code is a Foreign Key constraint in Request Table and corresponds to

key Primary key Vessel_No in Vessel Master table.
Foreign Consign_No is a Foreign Key constraint in Request Table and corresponds to
key Primary key Voyage_No in Voyage Master table.
Foreign Voyage_No is a Foreign Key constraint in Request Table and corresponds to
key Primary key Voyage_No in Voyage Master table.

13.3.20 Service Details

Table Name
Table
Description

220
Fields
# Field Name Data Siz Field Level Description
Type e Constraints
1. Service Type Varchar 24 Primary Key This will be
2 basically containing
two types of services
collection or/and
delivery.
2. Order No. Varchar 10 Primary Key, References Order
2 Foreign Key Details.
3 Request_No Varchar 10 Primary Key, References Request
2 Foreign Key Details.
4. Vessel_Code Varchar 10 Foreign References Vessel
2 Key Details.
5. Voyage_No Varchar 10 Foreign References Voyage
2 key Details.
6. Container_No Varchar 10 Foreign References Container
2 key Details.
7. Consign_No Varchar 10 Foreign References
2 key Consignment
Details..
8. FromPrmId Varchar 10 Foreign Key From Premise Code,
2 references Prmise
Master.
9. Reqd_Date Date Service Required
Date
10. Reqd_Time Date Service Required
Time
11. ToPrmId Varchar 10 Foreign Key To Premise Code,
2 references Prmise
Master.
12. Offload Boolean Whether Delivery
offload required
13 Side_Ldr Boolean Side Loader required
14. Del_Wait Boolean Whether Delivery
waiting required
15. Del_Wait_Time Date Delivery waiting time
16. Diver_Reqd Boolean Whether Diversion
required
17. Diver_2ndPrem Varchar 10 Foreign Diversion 2nd Premise
_Id 2 key Code, references
Prmise Master.
18. Div2_Wait Boolean Whjether Delivery
waiting required
19. Div2_Wait_Tim Date Diversion 2nd Premise
e waiting time
20. Staging Boolean Staging required

221
21 B_To_B Boolean Back to back cda is
accepted by customer
or not.
22. Locality Varchar 10 It will denote whether
2 the CDA is local or
outstation.
Validations & Table Level Constraints

Constrain Description
t Name
Request_N Request_No is a Primary Key constraint in Request Table and will
o hold unique records.
Container_Container_No is a Foreign Key constraint in Request Table and
No corresponds to Primary key Container_No in Container Master
table.
Consignme Consignment Type contain what type we used that is
nt Type (normal,perishable,dangerous)

Foreign Vessel_Code is a Foreign Key constraint in Request Table and

key corresponds to Primary key Vessel_No in Vessel Master table.
Foreign Consign_No is a Foreign Key constraint in Request Table and
key corresponds to Primary key Voyage_No in Voyage Master table.
Foreign Voyage_No is a Foreign Key constraint in Request Table and
key corresponds to Primary key Voyage_No in Voyage Master table.

13.3.21 Consignment Details

Table Name Consignment
Table This table contains Detailed Information of
Description Consignments.
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. Consign_No Varchar2 10 Primary Consignment
Key Number
Container_No Varchar2 10 Foreign References
Key Container Details
3. Consign_Type Varchar2 10 Not Null Consignment
Type
4. Impex_type Varchar2 6 Not Null Whether
Consignment is
Export or Import

222
 5. Consign_Wt Number 10 Consignment
Weight in Tons
6. Consign_Qty Number 10 Consignment
Quantity
7. UOM Varchar2 20 Consignment
Unit Of
Measurement
supplied by the
customer
8. Consign_Value Number 10,2 Consignment
Value
9. Consignor_Name Varchar2 30 Not Null Consignor Name
10 Consignor_Address1 Varchar2 50 Not Null Consignor
. Address1
11 Consignor_Address2 Varchar2 50 Consignor
. Address2
12 Consignor_City Varchar2 25 Not Null Consignor City
.
13 Consignor_Country Varchar2 25 Not Null Consignor
. Country
14 Consignor_Pin Varchar2 10 Not Null Consignor Pin
. Code
15 Consignor_Ph_No Varchar2 20 Consignor
. Phone
Number
16 Consignor_Contact Varchar2 30 Consignor
. _Person Contact Person
Name
17 Consignee_Name Varchar2 30 Not Null Consignee Name
18 Consignee_Address1 Varchar2 50 Not Null Consignee
. Address1
19 Consignee_Address2 Varchar2 50 Consignee
. Address2
20 Consignee_City Varchar2 25 Not Null Consignee City
.
21 Consignee_Country Varchar2 25 Not Null Consignee
. Country
22 Consignee_Pin Varchar2 10 Not Null Consignor Pin
. Code
23 Consignee_Ph_No Varchar2 20 Consignee Phone
. Number
24 Consignee_Contact Varchar2 30 Consignee
. _Person Contact Person
25. Voyage_No Varchar2Foreign
10 References
Key Voyage Details
Validations & Table Level Constraints

223
Constraint Description
Name
Consign_No Consign_No is a Primary Key constraint in
Consignment Table and will hold unique records.
Container_No Container_No is a Foreign Key constraint in Consignment
Table and corresponds to Primary key Container_No in
Container table.
Con_Vessel_C Con_Vessel_Code is a Foreign Key constraint in
ode Consignment Table and corresponds to Primary
key Vessel_Code in Vessel r table.
Con_Voyage_ Con_Voyage_No is a Foreign Key constraint in Consignment
No Table and corresponds to Primary key Voyage_No in Voyage
table.

13.3.22 Container Details

Table Name Container Details
Table This table contains details of Containers.
Description
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. Container_No Varchar2 10 Primary Container Number
Key
2. Container_Size Number 2 Container Size (20 or 40)
3. Container_Type Varchar2 15
5. Container_Owner Varchar2 30 Container Owner
8. Container_Status Varchar2 5 Container Status
(Laden/Empty)
Validations & Table Level Constraints

Constraint Description
Name
Primary key Container_No is a Primary Key constraint in Container
MasterTable and will hold unique records.

13.3.23 Voyage Details

Table Voyage
Name
Table This table contains detailed information of Voyage.
Description
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts

224
1. Voyage_No Varchar2 10 Primary Voyage Number
Key
2 Vessel_No. Varchar2 10 Foreign Vessel No.
Key
3. ETA_Date Date Vessel Expected
Date of Arrival
4. ETA_Time Date Vessel Expected
Time of Arrival
5. Port_Code Varchar2 10 Foreign Port Code
Key
Validations & Table Level Constraints
Constraint Description
Name
Voyage_No Voyage_No is a Primary Key constraint in Voyage
Table and will hold unique records.
Port_Code Port_Code is a Foreign Key constraint in Voyage
Table and corresponds to Primary key Port_Code in
Port Master table.

13.3.24 Vessel Details

Table Name Vessel
Table This table contains detailed information of Vessels.
Description
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. Vessel_Code Varchar2 10 Primary Vessel Code number
Key
2. Vessel_Type Varchar2 9 Type Of Vessel
3. Origin_Country Varchar2 25 Country Of Origin
4. Shipping_Line Varchar2 30 Shipping Line
Validations & Table Level Constraints
Constraint Description
Name
Vessel_Code Vessel_Code is a Primary Key constraint in Vessel Table
and will hold unique records.

225
13.3.25 CDA

Table Name CDA

Table This table contains master information about
Description Collection and Delivery Advice.
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. CDA_No Varchar 10 Primary CDA Number -
2 Key Unique for a
CDA
2 Interim_Status Varchar 12 Whether the
2 CDA has Not
started,
Started or
Done
3 CDA Status Varchar 10 This will show the
2 current status of
the CDA, i.e
whether it is
Pending,
Replanned or
New
4. Request_No Varchar 10 The Request
2 Number
pertaining to the
Request from
which the CDA is
generated.
5. Order_No Varchar 10 The Order
2 Number
pertaining to the
Order from which
the CDA is
generated.
6 Impex_Type Varchar 7 Whether Import
2 or Export
7. Reqd_Date Date Required Date
8. Reqd_Time Time Required Time
10 Service_Sub-Type Varchar 8 This contains
2 basically ten types
of services we are
providing to the
customer.

226
 11 Container_No Varchar 10 Container
2 Number – The
Container number
of the container to
be collected, if
any
12 Container_Size Number 6 Container Size -
. The Container
size of the
container to be
collected. If no
container is to be
collected, the
Container Size is
zero.
13 BtoB_CDA_No Varcha 10 Back-To-Back
. r2 CDA Number –
CDA Number of
the Back-To-Back
CDA associated
with the current
CDA
14 ETA_Date Date ETA Date
.
15 ETA_Time Time ETA Time
.
16 From_Premise Varchar 30 From Premise
. 2 Name
17 To_Premise Varchar 30 To Premise Name
. 2
18 Replanned By Varchar 30 Whether
. 2 replanned by
Customer or
Planner
19 Side_Loader Boolean Side Loader
. Option
20 Del_Waiting_Time Delivery Waiting
. Time
21 Offload Boolean Delivery Offload
.
22 Diversion Boolean Whether
. Diversion
Required
23 Diversion_Sec_Premise Varchar 30 Diversion Second
. 2 Premise Name
24 Div_SecPremiseWait_Ti Varchar 30 Diversion Second
. me 2 Premise Waiting
Time

227
 25 Div_SecPremise_Offloa Boolean Whether
. d Diversion Second
Premise Offload
26 Coll_Ready_Date Date Collection Ready
. Date
27 Coll_Ready_Time Time Collection Ready
. Time
28 Locality Varchar 10 Local or
2 Outstation
29 Empty_Trailer_Coll_Dat Empty Trailer
. e Collection Date
30 Replan_Date Replan Date
31 Consignment Type Varchar 10 This will contain
2 the type of goods
i.e whether
Dangerous
,Normal or
perishable
Validations & Table Level Constraints

Constraint Description
Name

13.3.26 Plan Audit

Table Name Plan Audit
Table
Description
Fields
Field Name Data Si Field Level Description
Type ze Constraints
Plan_ID Varchar 10 Identification for a
2 particular plan.
User_ID Varchar 20 The unique code to
2 identify a particular
planner.
Mode_op Varchar 10 The type of
2 operation planner is
doing. It may be
Insert / Update /
Delete.
Op_Dt Date The date when
planner is making
the plan.

228
From_Tm Date At what time
planner is starting
planning pertaining
to a particular date.
To_Tm Date End time of
planning pertaining
to a particular date.
Validations & Table Level Constraints
Constraint Description
Name

13.3.27 Plan
Table Name Plan
Table
Description
Fields
Field Name Data Si Field Level Description
Type ze Constraints
Plan_Id Varchar 10 PK,Foreign Key Unique
2 identification for a
particular plan.
PM_No Varchar 10 Foreign Key Prime Mover
2 number that will
execute a particular
plan.
Request_No Varchar2 10 Foreign Key The Request Number
pertaining to the Request
from which the CDA is
generated.
Order_No Varchar2 10 Foreign Key The Order Number
pertaining to the Order
from which the CDA is
generated.
CDA_No Varchar2 10 Foreign Key CDA Number - Unique
for a CDA
B2B_CDA_No Varchar2 Back-To-Back CDA
Number – CDA Number
of the Back-To-Back
CDA associated with the
current CDA
Tailer_No Varchar 10 Foreign Key Trailer No.
2

229
Driver_name Varchar 30 FK Name of the driver
2 pertaining to a
particular Prime
Mover .
Visit_no Varchar 10 The sequence /
2 order in which a
Prime Mover will
perform a particular
Plan.
Replan_date Date Postponed date on
which a particular
CDA will be
performed.
Container_siz Varchar 5 Size of container.
e 2
From_premis Varchar 30
e 2
To_premise Varchar 30
2
Reqd_Date Date Required Date
Reqd_Time Time Required Time
Validations & Table Level Constraints
Constraint Description
Name
Plan_Id Plan_Id is a Primary Key constraint in Plan Audit Trail
Table and will hold unique records.
PM_No PM_No is a Primary Key constraint in Prime Mover
master Table and will hold unique records.
Request_No Request_No is a Primary Key constraint in Request Details
Table and will hold unique records.
Order_No Order_No is a Primary Key constraint in Order Table and
will hold unique records.
CDA_No CDA_No is a Primary Key constraint in CDA Table and will
hold unique records.

13.3.28 Plan_ PM
Table Name Plan_PM
Table
Description
Fields
Field Name Data Si Field Level Description
Type ze Constraints
Plan_ID Varchar 10 Primary Key Unique
2 identification for a
particular plan.

230
PMNo Varchar 10 The unique code to
2 identify a particular
prime-mover.
Plan_dt Date The date when
planner is making
the plan.
Validations & Table Level Constraints
Constraint Description
Name
Plan_ID Plan_ID is a Foreign Key constraint in Plan Audit Trail
Table and will hold unique records.

13.3.29 PM_Availability
Table PM_Availability
Name
Table This table describes the availability of primemover
Description for different shifts
Fields
Field Name Data Si
Field Level Description
Type ze
Constraints
PMNumber Varchar 10 Identification for a
2 particular plan.
Shift1 Varchar 5 Availability of a
2 particular prime-
mover for shift1
Shift2 Varchar 5 Availability of a
2 particular prime-
mover for shift2
Shift3 Varchar 5 Availability of a
2 particular prime-
mover for
Reason Varchar 50 Reason for
2 unavailability of a
particular
primemover
Validations & Table Level Constraints
Constraint Description
Name

231
13.3.30 Plan_Table_Audit
Table Plan_Table_Audit
Name
Table
Description
Fields
Field Name Data Si Field Level Description
Type ze Constraints
Plan_ID Varchar 10 Identification for a
2 particular plan.
Request_No Varchar 10 Gives request no.
2 of a particular
request.
Order_No Varchar 10 Gives order no. of
2 a particular
request
CDA_No Varchar 10 Gives cda no. of a
2 particular order
Driver Varchar 30 Driver allocated
2 for a plan
Visit_No Varchar 10 Sequence of
2 CDA’s to be
executed in a
plan
Int_Stat Varchar 15 Gives the interim
2 status of a
particular CDA-
Sarted,Not
started,Done
Cont_No Varchar 10 Container no. of
2 the particular
CDA which is
currently planned
Cont_Sz Number 2 Container size for
the particular
CDA which is
currently planned
Time date Operational Time
Mode_op Varchar 10 Delete,Update
2
Validations & Table Level Constraints
Constraint Description
Name

232
13.3.31 Logged_Planner
Table Name Logged_Planner
Table
Description
Fields
Field Name Data Si Field Level Description
Type ze Constraints
Usr Varchar 20 Describes which
2 planner logged into
the system at
current time
Session_From Date Starting time of the
current logging
planner
Session_To Date End time of the
current logging
planner
Validations & Table Level Constraints
Constraint Description
Name
Plan_ID Plan_ID is a Foreign Key constraint in Plan Audit Trail
Table and will hold unique records.

13.3.32 Driver_Shift
Table Driver_Shift
Name
Table This table describes the availability of driver for
Description different shifts
Fields
Field Name Data Si
Field Level Description
Type ze
Constraints
D_Code Varchar 10 Identification for a
2 particular plan.
Shift Number 1 Availability of a
particular driver
for a particular
shift
Validations & Table Level Constraints
Constraint Description
Name

233
13.3.33 Bill Details
Table Bill_Details
Name
Table This table contains detailed information about
Descriptio billing.
n
Fields
# Field Name Data Siz Field Description
Type e Level
Constr
aints
1. Inv_No Varchar2 10 Primary Invoice
Key number,unique for an
invoice
2. Varchar 10 Foreign Request number
2 Key
3. OrdID Varchar 10 Foreign Order number
2 Key
4. Bill_Date Date Date of Bill
Execution
5. Bill_Value Number (10, Total Bill amount
2)
Validations & Table Level Constraints
Constraint Description
Name
Invoice_No Invoice_No is a Primary Key constraint in Bill Details
table and will hold unique records.
Request_No Request_bo is a Foreign Key constraint in Bill Details
table and is referenced to the Request_No in Order
Details table in which it is a primary key with
Order_No.
Order_No Order_No is a Foreign Key constraint in Bill Details
table and is referenced to the Order_No in Order
Details table in which it is a primary key with
Request_No.

13.3.34 Payment History

Table Name Payment_History
Table This table contains detailed information about payments
Description for billing.
Fields

234
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. Invoice_No Varchar2 10 Foreign Invoice number
Key
2. Amount_Received Number (10,2 Amount Received for a
) bill
3. Amount_Due Number (10,2 Amount Due for a bill
)
4. Date_of_Receipt Date Date of amount received
5. Mode_of_Payment Varchar2 10 Mode of
payment(cheque,cash,dra
ft)
Validations & Table Level Constraints
Constraint Description
Name
Invoice_No Invoice_No is a Foreign Key constraint in Payment History
table and is referenced to the Invoice_No in Bill Details
table in which it is a primary key.

13.3.35 Draft/Cheque Details

Table Draft/Cheque Details
Name
Table This table contains detailed information about
Description draft/cheque
Fields
# Field Name Data Siz Field Description
Type e Level
Constrai
nts
1. Invoice_No Varchar2 10 Foreign Invoice number
Key
2. Draft/Cheque_N Varchar 10 Draft/Cheque
o 2 number
3. Draft/Cheque Date Date Draft/Cheque Date
4. Validity Number (10,2 Validation of cheque
) for specific months
5. Drawee Bank Varchar2 30 Name of the Drawee
Bank
6. Branch Varchar2 20 Name of the branch
of the bank
Validations & Table Level Constraints

235
Constraint Description
Name
Invoice_No Invoice_No is a Foreign Key constraint in Payment
History table and is referenced to the Invoice_No in
Bill Details table in which it is a primary key..

13.3.36 Bill_Dummy
Table Bill_Dummy
Name
Table This table contains dummy temporary information
Description about bill
Fields
# Field Name Data Size Field Description
Type Level
Constra
ints
1. Req_No Varchar2 10 Foreign Request number
Key
2. Ord_No Varchar 10 Foreign Order number
2 Key
3. No_of_cda Number 8 Number of CDAs in
an order
Validations & Table Level Constraints
Constraint Description
Name
Req_No Req_No is a Foreign Key constraint in Bill_Dummy
table and is referenced to the Req_No in
order_details table in which it is a primary key.
Ord_No Ord_No is a Foreign Key constraint in Bill_Dummy
table and is referenced to the Ord_No in
order_details table in which it is a primary key.

236
14 Methodology To Be Used For Testing
14.1 SYSTEM TESTING
 Introduction.
 Module Testing.
 Integration Testing.
 Domain Testing.

14.2 INTRODUCTION:

System testing is one of the vital states and it must be performed for
success of a system. The purpose of the testing is to consider all likely
variations to which the system will be subjected and then push the system
to its limits.

14.3 MODULE TESTING:

In module testing all the modules are tested for syntax and logical errors.
All the modules are tested separately with some sample data; initially it
faces some problems, which are later corrected. The module testing is also
known as unit testing. After module testing the system is tested as a whole
i.e. all the modules are tested together- this is known as integration testing.

14.4 INTREGRATION TESTING:

It implies, the testing of integrated unit tested modules. The testing is done
just after the finished of unit testing, actually here we test as a whole of the
modules. This testing can be down in the following two approaches as
follow:
1). Top down Approach.
2). Bottom up Approach.
Here in this project we apply the Top down approach for the integration
testing and we face so error at first time, then we remove all that error and
we get satisfactory result.

14.5 DOMAIN TESTING:

During domain testing, we test the domain specific values. It is very
important testing for the identification of the domain values, here we check
all the values and we get some error like in the DDO Code, remarks etc.

237
And we remove all that domain specific error and we get the satisfactory
result.

14.6 Test Report

Project is undergoing ,and now we are in Coding Phase. So Testing is still not be done.

238
15 List of Abbreviations
S. No. Term/Abbreviation Description
1. CDA Collection and Delivery Advice
2. ROT Request On Transportation
3. PM Prime Mover
4. FFA Freight Forwarding Agent
5. DOP Date Of Purchase
6. DOC Date Of Commissioned
7. DOD Date Of Decommissioned
8. DOS Date Of Scrap
9. ETA Expected Time of Arrival
10. ETD Expected Time of Departure
11. CP Customer Premise
12. DD Direct Delivery
13. DC Direct Collection
14. B2B Back to Back

239
16 References

16.1 Bibliography

The following books help us to complete this project.

A. Beginning Active Server Pages 3.0
I. David Buser
II. John Kauffman
III. Juan T. Llibre
IV. Brian Francis
V. David Sussman
VI. Chris Ullman
VII. Jon Duckett
♦ SPD & WROX Publication
B. Beginning Active Server Pages 3.0
I. Alex Homer
II. David Sussman
III. Brian Francis
IV. Dino Esposito
V. Andrea Chiarelli
VI. Simon Robinson
VII. Richard Anderson
VIII. George Reilly
IX. Craig Mc. Queen
X. Chris Blexrud
XI. Dean Sonderegger
XII. Dan Denault
XIII. John Sochenken
XIV. Bill Kropog
XV. Mathew Gibbs
♦ WROX Publication
C. Internet & World Wide Web – How To Program
XVI. H. M. Deitel
Deitel & Associates, Inc.
XVII. P. J. Deitel
Deitel & Associates, Inc.
XVIII. T. R. Nieto
Deitel & Associates, Inc.
♦ Pearson Education Asia
D. Platinum Edition – Using HTML 4,XML,JavaTM 1.2 (QUE Series)
XIX. Eric Ladd
XX. Jim O’Donnell
♦ Eastern Econmy Edition & Prentice Hall India
E. SQL,PL/SQL - The Programming Language of Oracle (2nd Revised
Edition)
I. Ivan Bayross
♦ WROX Publication

240
F. Mastering Visual Basic 6.0
♦ BPB Publication
G. Mastering JavaScript
♦ BPB Publication

H. ORACLE 8i – Advanced PL/SQL Programming of Oracle Press

♦ TATA McGraw-HILL
I. Learn HTML in 21 days
♦ BPB Publication

241