TRANSPORT MANAGEMENT SYSTEM

Transport Management System

Contents
1. Introduction:............................................................................................................................................3
2. Problems and proposed solutions:...........................................................................................................4
2.1 Proposed Solutions:...............................................................................................................................5
3. Project planning:......................................................................................................................................6
3.1 System Development Life Cycle (SDLC).......................................................................................6
3.1.1 Planning Phase:.............................................................................................................................6
3.1.2 Analysis Phase:.............................................................................................................................7
3.1.3 Design Phase:................................................................................................................................8
3.1.4 Implementation Phase:.................................................................................................................9
3.1.5 Maintenance Phase:......................................................................................................................9
4.0 Feasibility Study:.................................................................................................................................10
4.4.1 Technical Feasibility...................................................................................................................10
4.4.2 Economical Feasibility................................................................................................................10
4.4.3 Operational Feasibility...............................................................................................................11
4.4.4 Behavioural Feasibility...............................................................................................................11
5. Requirement Definition:........................................................................................................................12
6. Design Diagram (Use Case):.................................................................................................................14
6.1 Use Case Diagram:........................................................................................................................14
6.3 Context diagram:...........................................................................................................................15
6.4 DFD:...............................................................................................................................................15
6.5 Use Case Description:....................................................................................................................17
7. Database:...............................................................................................................................................19
8. Implementation:.....................................................................................................................................31
8.1. Hardware Requirement.......................................................................................................................31
8.2. Software Requirement........................................................................................................................32
9. References:............................................................................................................................................33

Page 2 of 33
 Transport Management System

1. Introduction:

A transport system can be conceptualized as the set of relationships

between nodes, networks, and demand. These relationships involve locations spatially
expressing this demand, flows between them, and infrastructures designed to handle and link
these flows. All the components of a transport system are designed to facilitate the movements of
passengers, freight, and information, either as separate or joint components.

 Demand. A derived function for the mobility of people, freight, and information for a
variety of socioeconomic activities.
 Nodes. Where movements are originating, ending, and transiting (intermediacy), entry or
exit points in a transport system. They vary according to the geographical scale being
considered ranging from local nodes (such as a subway station) to global nodes (such as
port or airport terminals).
 Networks. Composed of a set of linkages expressing the connectivity between places and
the capacity to handle passenger or cargo volumes.
 Locations. Nodes where demand is expressed as an origin, destination, or point of transit.
The level of spatial accumulation of socioeconomic activities (production and
consumption) jointly defines demand and where this demand is taking place.
 Flows. The amount of traffic over a network, which is composed of nodes and linkages.
This is jointly a function of the demand and the capacity of the linkages to support them.
 Infrastructures. The conveyances such as roads and terminals expressing the physical
reality of a network and are designed to handle demand with specific volume and
frequency characteristics. Facilities enabling access to a network are jointly characterized
by their centrality and the linkages that radiate from them.

Research and Assumption:

The basic assumption of the model is that the transportation cost on a given route is directly
proportional to the number of units transported. The "unit of transportation" will differ based on
the "commodity" transported i.e. a truck load may be a better unit than single product units.
Research plays a critical—and growing— role in the national transportation debate.
Transportation research is vital for improving mobility, building better roads, providing safer
conditions for drivers and pedestrians, and increasing the service life of bridges. For example,
issues of funding and finance dominate the discussion of surface transportation in the United
States. Two national commissions have addressed the topic, and the U.S. Government
Accountability Office recently added transportation financing to the list of high-risk areas for
oversight by Congress. The ongoing dialogue and debate at the federal, state, and local levels
point to the need for robust transportation research programs and for compelling ways to
communicate the value of that research for solving transportation system problems.
Communicating the value of transportation research can be difficult. Although most people
conceptually grasp the value of research and its results, they do not make the direct connection to

Page 3 of 33
 Transport Management System

the need for research funding—particularly for innovations or new technologies that may take
years to develop.

2. Problems and proposed solutions:

 Inability of modification of data.:- as the data is stored in the registers due to which
modification of the data becomes very complex or we can say that inability of modification of
data.

 Not user friendly.:- as data is stored in the register which makes existing system non
user friendly i.e data becomes complex. Hence its not a user friendly.

 Security issues.:- in existing system as the data is stored in the register which can be
easily accessible by anyone. Anyone can open up the register and can access the data.

 Lots of paperwork. :- in existing system all the data is stored in the register due to
which so many documents get piled up i.e lots of paperwork get collected.

 Manual operator control.:- this can be operated by any of the person easily.

 Time consuming.:-its really time consuming as to search the record you have to search
each and every document.

 More chances of errors.:- all the record is documented manually which increases more
chances of errors.

 Chances of data loss:-in this as all the data is collected in registers due to which chances
of data loss can take place.

 Due to manual work existing system is very time consuming and there is always a
chance of error so that it is not much reliable.

 This system has been developed to be simple and user friendly.

 Hence, even a non-technical user can use the system effectively and without any
difficulty.  It is upgradeable. Hence further enhancement to the system is possible.

 The system can generate the necessary report.

Page 4 of 33
 Transport Management System

 The system maintains speed and accuracy with eye-catching GUI.

 It takes care of database security by restricting unauthorized access to the system.

Currently there is not system available for handling the Transport Management System.
Manual data is updating into ledger and files. So searching any information is not easy task and
everybody has to put more effort to get the appropriate data. More man powers required to
handle the multiple kind of process and same time if customers have any query so it will be
resolved based on the manual intervation along with delay in time. Manual followup require
during the complete process and no plan to develop the new finding to upgrade the process.

2.1 Proposed Solutions:

In this we overcome the limitations of existing system.

 System should be window based, user friendly, and efficient.

 System security must be implemented by preventing unauthorized access to it.

 Appropriate master table mast be present to record relevant data.

 Security feature must exist in the system.

 All the calculations are done automatically and thus no chances of errors

 This system has been developed to be simple and user friendly.

 Hence, even a non-technical user can use the system effectively and without any difficulty.

 It is upgradeable. Hence further enhancement to the system is possible.

 The system can generate the necessary report.

 The system maintains speed and accuracy with eye-catching GUI.

 It take care of database security by restricting unauthorized access to the system

Page 5 of 33
 Transport Management System

3. Project planning:

3.1 System Development Life Cycle (SDLC)

Project should be functioning and working properly as per expectation, there must be
some checklist to make the project success. To develop a project, there should be some standard
which can be maintain for every projects. System development life cycle (SDLC) is a very
popular method which used in maximum project to make the success. In this process, multiple
process will execute in sequence as Planning, Analysis, Design, Development, Testing,
Implementation and Maintenance as per the below snapshot.

Apply the SDLC methodologies to save the cost and time. It will increase the efficiency.

3.1.1 Planning Phase:

Planning stage is the initiation stage of SDLC which is the process to start the work, this
phase is to identify the feasibility study and map with the existing project along with
identification of the Risks. If risks are identified in beginning, then project will not be failed
in any case. Project Charter needs to prepare in the phase which have the objective and main
requirements of the projects. It also contains the project manager name along with the

Page 6 of 33
 Transport Management System

stakeholders and approved by the sponsor. So, the output of this phase will be become the
input of the next phase. The more information and documents on the project goals, the more
outputs can be achieved such as, the management plan structure, emphasis on plan quality,
the overall project plan for the schedule and scope and finally the predictable results.

The planning phase in our proposed system is achieved by the selected team’s members to
get the details from the higher management and HR stakeholders. Now all the team members
will work on Transport domain to understand the functionality so it will be beneficial for making
the initiation document for further phases.

3.1.2 Analysis Phase:

When Planning stage is successfully completed and approved by the sponsor and other
stakeholders then next stage will be initiated to match the requirement, this phase is also an
important part of SDLC. SO, this stage will be performed to understand the system requirement
and match with the exiting product or project, so final goal is to accomplish the goal on time. So,
document should be prepared clearly, and output of this phase is SRS (Software Requirement
Specification) which contains the all requirement and expectation from the project. It contains all
the hardware and software specification for development and deployment environment. So,
remove all uncertainty of this phase so it will become the milestone for the next phase. Multiple
methods are available to get all kind of the requirement as interviews, face to face discussion,
query sheet, , document review and observations through our stakeholders.

Page 7 of 33
 Transport Management System

3.1.3 Design Phase:

Once the requirements are finalized in the above phase, then needs to convert the
requirement (SRS) into design documents. In this phase all kind of designs along with
documentation. So, needs to create the context diagram, multiple level of DFD, ER Diagram and
GRD diagram. It will have the complete information of the architecture on which it has to
develop. This phase is having all in technical aspect of the requirement and cover each in the
design documents. Design documents should be very clear and vast so no gap on requirement.
The best part of this phase is that data base is designing along with data dictionary and
normalization technique. So, once DB is ready then it will be the input of the next phase to
develop the screen/code based on the database structure.

Page 8 of 33
 Transport Management System

3.1.4 Implementation Phase:

This phase is not the implementation phase but it should be development along with
testing phase. So based on the requirement, we need to design the screen and interface which will
save/extract the data from DB in the last phase. development need to complete to make the
deliverable for UAT/Implementation/ deployment. During the development, testing process is
parallel as testing and creating the multiple kind of the testing documents. This is the phase we
execute the multiple kind of test case to get rid of any error and mismatch with the requirements.
Once deliverables are ready to deploy at client location for UAT or LIVE then the task of this
phase is completed, and we have multiple documents for evidence purpose. Everything should be
baselined the TFS.

3.1.5 Maintenance Phase:

Once product/exe is deployed on the client environment then the project will come under
support or maintenance. In this phase, Client will provide the signoff after UAT done and LIVE
deployment done. The signoff meaning is that the product is fulfilling all the requirement which
are available in the SRS document. So, after Signoff, support will be provided free of cost for
some times as per the agreement between client and vendor. During this time, if any error occurs
on live environment, then developer has to fix based on the SLA, if there is any new changes

Page 9 of 33
 Transport Management System

then it will not come under support mode. After agreed points, client will provide the AMC for
further support of the developed project.

4.0 Feasibility Study:

Feasibility study is nothing but the way to work on the environment which can fulfill
the requirement of the client. If client is asking some requirement and it is not possible
to provide then should say NO to client along with the valid reason. Client will
understand and provide some refined requirement which can be developed and
delivered. So, 1st understand the complete scope of the project and work on the
feasibility report on the small requirements. Feasibility report should contains the PO
cost and time also, if the project is not developed during the time and money then we
should say it is not feasible. It should include the benefits also.
The below are some points which need to consider during the process:

1. Problem Statement:

A clear statement which provides the information of any problem. Problem statement
is very useful, but it should have some kind of evidence also.
2. Finding and Recommendations:
Always create a list of all recommendation and findings, it may be small or big. It
will provide the clear picture to each stakeholder.

4.4.1 Technical Feasibility

If discuss on technical feasibility, then always discuss on hardware and software side.
Checklist should be prepared based on the compatibility in multiple aspect and
combination of software and hardware. Even think about the support during warranty
period and after that also. License and expiry date (out of support) software should not
be used, if used then no support found in the market and will struck later on. necessary
steps have been considered to make it technically feasible.

4.4.2 Economical Feasibility

Cost is the important part of any system feasibility. Cost means not only hardware and
software, but it should consider the manpower also. The analysis of Economic should
be very frequently to identify the feasibility in term money and resources. It is called
cost/benefit analysis and it is mostly used to check the process of feasibility, Feasibility
should consider the profit also, it should not be on that theory that no profit not loss.

Page 10 of 33
 Transport Management System

If developing the new product/software 1 st time then should be consider it for

reusability, if product can re-use then it will provide the more benefits to the
organisation so in this case 1st iteration can go in loss also because scope is there to gain
later on. The below points consider for Economic feasibility:
i. Should be full system validation and investigation.
ii. Software and hardware cost should be latest one with inclusive of all taxes.
iii. Make the common practice which can be used to reduce the cost on every
steps.
iv. Adhere the project scope 100%, if any new changes are there then re-calculating
the cost.

The below point will be proposed point to make system economically feasible.
i. Time factor should be less. The system requires very less time factors.
ii. System performance should be at par, if one invest to make the system fast in
term of performance then investment should be executed. This will save
the cost of time and man powers.
iii. Interface should be user friendly so less effort required for demo, training
and actual working.
iv. Multiple parameters should be captured for making the reports and other
story for decision making which can be used in future.
4.4.3 Operational Feasibility

GUI and interface should be designed for less effort or less click on the screen. It will
save the time of actual work hours. This kind of application is easy to operate along
with it is called user friendly screen/product. Main menu and other feasible GUI which
can provide the complete information of the software and user can easily move to
another module from one module.

4.4.4 Behavioural Feasibility

In the normal life, it is expected that behavioural should be as per expectation. It means
if any estimation is happening then it should be on the actual cost (no false addition of
any task or spend), If any estimate done by any vendor and client is having some gap of
estimation then client will ask the question, if vendor is not able to provide the
Page 11 of 33
 Transport Management System

satisfactory answer then both parties will loose the trust to each other. So, any type of
the relation between one party to other party should have the behavioural feasibility.
Demo and support should provide as per the agreement before project gets started.

5. Requirement Definition:

5.1 Functional Requirements:

Functional requirements mean the expectation of client. It is a process to understand the
business logic of Transport Management System and each process in Transport industry. So it
can be defined like that what is the input of the process, processing and output of the process.
The output of the 1st process will become the input of next process. Functional requirements will
be useful to understand the estimation of project in terms of Money and time. Functional
requirement is also useful to provide the support to developer during the development.

Functional requirements for Transport Management System:

- Payment processing and invoice availability along with the pending amount on each customer.

- Should capture the attendance of each person who belongs to the Transport Management
System.

- Customer should have the access to track the class along with the registration for any Truck.

- Admin should have the permission to add the master data.

- System should provide the option to capture the feedback from customer.

- System should provide the option to generate the multiple reports along with dashboard.

5.2 Non-Functional Requirements:

Non-functional requirements specify criteria that can be used to judge the operation of a
system, rather than specific behaviors. Non-functional requirements define how a system is
supposed to be. These are the features that don’t do anything but are important characteristics of
the system. For example, design, user interface, user experience, compatibility, etc.

Security - is the degree of resistance to, or protection from, harm. It applies to any vulnerable
and valuable asset, such as a person, dwelling, community, nation, or organization.

Page 12 of 33
 Transport Management System

Reliability - the ability of a system or component to perform its required functions under stated
conditions for a specified period.

Availability - Availability of a system is typically measured as a factor of its reliability - as

reliability increases, so does availability. Availability of a system may also be increased by the
strategy on focusing on increasing testability & maintainability and not on reliability. Improving
maintainability is generally easier than reliability. Maintainability estimates (Repair rates) are
also generally more accurate. However, because the uncertainties in the reliability estimates are
in most cases very large, it is likely to dominate the availability (prediction uncertainty) problem,
even while maintainability levels are very high.

Maintainability - is defined as the probability of performing a successful repair action within a

given time. In other words, maintain ability measures the ease and speed with which a system
can be restored to operational status after a failure occurs.

Portability - the ability of a computer program to be ported from one system to another in
computer science.

Page 13 of 33
 Transport Management System

6. Design Diagram (Use Case):

6.1 Use Case Diagram:

As per the use case diagram, there are main 4 entities as below
1. Admin – Super user of system and can check/add/delete any thing in the system. So in
other word, he is having the complete permision to provide the permision to any user.
2. Manager – Manager is the part of the system who controls the process and other
impediments.
3. User – Based on the permission, user has the permission to check the status of each
process, registration and location of the Truck also.
4. Server – It is used to save the data as well as the deployment the application.
5.

Page 14 of 33
 Transport Management System

6.3 Context diagram:

6.4 DFD:

Page 15 of 33
Transport Management System

Page 16 of 33
 Transport Management System

Given the data flow diagram for the multiple processed into the system. It denotes the process,
validation, input and output of each process.
Validation is used to validate the system functionalities based on the accepting the correct value
along with business rules validation.

6.5 Use Case Description:

Transport Management Software is a must in modern-day logistics and supply chain
management. TMS can help the supplier develop a proactive approach to managing the flow of
goods from origin to consumption. It enables them to reduce freight transportation cost, identify
freight capacity quickly, and offers transparency into various activities. It can connect to industry
databases to allow the business to stakeholders to make data-driven decisions.
However, choosing the right software is an intimidating task. While going through the selection
process, you need to consider specific points. The software should integrate data and analytics
features to support enhanced reporting capabilities and integrate them easily into your business
infrastructure. Moreover, it should enable you to align your services to the general trade policies
and compliance. The right software will provide you with better trade opportunities by
optimizing the transport budget, manage costs, invoices, and track the fleets in real-time. TMS
solution provides you with better visibility into the entire logistics transport operations.
A TMS software can bring in multiple benefits in the supply chain process and enable you to
generate maximum rate on investments. Here are five use cases of TMS in logistics operations.
Optimize Route Efficiency
Page 17 of 33
 Transport Management System

A TMS solution gives you better visibility into the route for transporting the goods and services.
It helps you consider real-time traffic conditions, equipment availability, personnel for
loading/unloading, and more to facilitate on-time delivery and adhere to the SLA for enhanced
customer experience. The route optimization capability of the software enables you to determine
the most cost-efficient route.
Inventory Reductions
A TMS facilitates an inventory reduction strategy which helps to improve inventory turnover. It
uses accurate inventory forecast models that take the seasonality and trends into consideration to
keep fluctuations in check while reordering stock. It helps to ensure replenishment strategy is
aligned to market demand variances.
Improved Cash Flow
A transportation management software will help your business to minimize shipment costs
significantly. Freight payment, auditing, and consolidation services help business personnel
define each logistical route’s financial aspect. It helps to decrease direct variable costs by
consolidating shipments and improving freight terms to make the transport operations more user
oriented.
Integrated Planning and Execution
A TMS solution can integrate seamlessly with the existing system you have in place for supply
chain optimization. It can work together with other management systems for warehouse,
customer relationship, purchasing and order cycle, and supplier relationship for better route
planning and load optimization.
Improve Customer Experience
A TMS solution enables you to make data-driven decisions to manage end-to-end shipments. It
helps you to save locomotive costs between multiple locations and control the movement of
goods efficiently. It enables you to consolidate all customer orders to find the best carrier at a
cost-effective price. Improved efficiencies in your transport management will speed operations
and deliveries to help you satisfy time-sensitive customers.
To Conclude:
A TMS solution will help you to move freight from origin to destination efficiently and reliably.
It uses process enforcement, analytics, and optimization to enable businesses to save money,
drive growth and revenue, and provide better customer service.

Page 18 of 33
 Transport Management System

7. Database:

Database design is the process of producing a detailed data model of a database. This logical data model
contains all the needed logical and physical design choices and physical storage parameters needed to
generate a design in a data definition language, which can then be used to create a database. A fully
attributed data model contains detailed attributes for each entity. The term database design can be
used to describe many different parts of the design of an overall database system. Principally, and most
correctly, it can be thought of as the logical design of the base data structures used to store the data. In
the relational model these are the tables and view. In an object database the entities and relationships
map directly to object classes and named relationships. However, the term database design could also
be used to apply to the overall process of designing, not just the base data structures, but also the forms
and queries used as part of the overall database application within the database management system.

 Determine the relationships between the different data elements.

 Superimpose a logical structure upon the data on the basis of these relationships.

Below tables will be created to keep the data for Transport Management Center.

1. Bill Table

Page 19 of 33
 Transport Management System

2. Branch table

3. Consignee details table

4. Consigner Details Table

Page 20 of 33
 Transport Management System

5. Crossing challan Table

Page 21 of 33
 Transport Management System

6. DDCC table

7. Deal table

Page 22 of 33
 Transport Management System

8. Docket no. table

Page 23 of 33
Transport Management System

Page 24 of 33
 Transport Management System

9. Lorry hire cum challan Details table

Page 25 of 33
 Transport Management System

10. lorry hire cum challan table

Page 26 of 33
Transport Management System

Page 27 of 33
Transport Management System

Page 28 of 33
 Transport Management System

11. MRC table

Page 29 of 33
 Transport Management System

12. Party table

13. Registration table

Page 30 of 33
 Transport Management System

14. State Table

15. Station table

16. TNC Table

8. Implementation:

Once UAT is successfully finished and Client is ready for the implementation then
Implementation team must install the software as per project requirement on the client machine.
Need to install the .NET framework and SQL Server on client machine to implement the
developed project.

8.1. Hardware Requirement

Page 31 of 33
 Transport Management System

Hardware configuration for executing the project. Every project is having some minimum
requirement to run the application on the machine/pc. So based on the Architecture, hardware
should be selected as per the future requirement as data is increasing everyday o performance
should be decreased. So, Hardware selection is very important to implement the Project.
Client-Side Hardware Requirement:

Intel Core 5 Processor

RAM: 4 GB
HDD: 512 GB
Monitor as per requirement.
Keyboards
Printer

8.2. Software Requirement

Software Requirement is defined here to install on Client machine as per the project requirement.
Operating System : Windows 10
Database (Back End) : Microsoft SQL Server 2018
Front-end : Visual Studio NET, C#, HTML, CSS, jQuery

Page 32 of 33
 Transport Management System

IMPLEMENTATION

After the UAT testing done, implementation phase is initiated. This phase is very crucial in the
SDLC. So now developed system will be implemented into operations. So, it is now coming out
from Testing and now actual users are going to use. During implementation, if any issue occurs
then it needs to resolve on the priority with SLA. During the implementation, User manual and
training to the actual users are mandatory.
After implementation, needs to keep the eye on the data, whether data is inserted/updated correct
or there are any discrepancies in data. If found any issue the needs to correct data. But before that
we must insert all master data with pre-requisite of the project.
User should know the very process of changing the master data as well as. We can divide
Implementation in multiple phases as below,
1. Fresh Implementation – Client did not use any system till now and getting the new
system to get rid of Manual system.
2. Project replacement Implementation – Client is using the same system from other vendor
and getting the new system in place of the previous system.
3. New Release of same Project Implementation – Client is using the same system with
same vendor and getting the newly updated exe based on his/her new requirement for
business related. In this case needs to copy only the deliverables.

9. References:

Websites Referred
 http://en.wikipedia.org/wiki/ASP.NET
 www.aspsnippets.com
 http://www.c-sharpcorner.coms
 http://www.w3schools.com/aspnet/
Books referred.
 Beginning ASP.NET 4.5.1 and Professional ASP.NET MVC 5
 Getting Started with ASP.NET 4.5 Web Forms and Visual Studio 2013
 Mastering Visual C# .NET

Page 33 of 33