Vehicle Management System

  • June 2020
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Vehicle Management System as PDF for free.

More details

  • Words: 10,157
  • Pages: 87
VEHICLE MANAGEMENT SYSTEM BACHLOR IN COMPUTER APPLICATIONS(BCA) Project Report

Submitted By Mr. Atul , ENROLMENT NO:-021633537 COURSE CODE:-CS-76 STUDY CNETER CODE:-0741(p),Vikas Puri. REGIONAL CENTER CODE:-07,TUGLAKABAD. NEW DELHI- 110046

INDIRA GANDHI NATIONAL OPEN UNIVERSITY(IGNOU)

In Partial Fulfillment of the requirements for the aware of the degree of BACHLOR IN COMPUTER APPLICATION

Page: 3

CERTIFICATE

This is to certify that Mr. Atul final year B.C.A. student of (IGNOU), STUDY CENTER (VIKAS PURI ,0741P), did a project on web based solution for VEHICLE MANAGEMENT SYSTEM for the Internet Business solution group of Falcon Marine Exports Limited, BBSR.The project was successfully completed during his study from – JUN to SEP

During this period we found his conduct to be excellent, adaptive, hard working and adhering to the norms of our organization

Mr Hiranmay Dash Project Guide

Page: 4

VIVA-VOCE EXAMINATION

The viva-voce examination of this project work, submitted by Mr.Atul bearing E- No.021633537 was held on

EXTERNAL EXAMINER

INTERNAL EXAMINER

Page: 5

ACKNOWLEDGEMENT First and foremost I thank the almighty for his shower of blessings and for giving me the courage and enthusiasm and perseverance to handle this project work It is my duty to thank my parents for their rich source of inspiration and advice. I also wish to thank my guide Mr.Kijol Agrawall for their kind suggestions and cooperation during the complete duration of the project. I sincerely thank my Technical Lead. Mr.HIRANMAY DASH who assigned me this project and with whose help this project was completely successfully.

Page: 6

Page: 7

Page: 8

Contents About Falcon Motors................................................................................................................................12 Project Overview.......................................................................................................................................13 The Benefits..........................................................................................................................................13 Project Scope.............................................................................................................................................14 Solution Architecture...............................................................................................................................14 Technology Used.......................................................................................................................................15 Development Environment.................................................................................................................15 Deployment Environment...................................................................................................................15 Requirement Details ................................................................................................................................15 Vehicle Management Module.............................................................................................................15 Vehicle Master Info Maintenance......................................................................................................15 Unit Allocation...................................................................................................................................16 Scheduled Activities .........................................................................................................................16 Change status.....................................................................................................................................16 Alter Registrations.............................................................................................................................16 Fuel Management...............................................................................................................................16 Driver Management...........................................................................................................................16 TYRE Management Module...............................................................................................................17 Tyre Master Maintenance..................................................................................................................17 Tyre Movements................................................................................................................................17 Tyre Purchases...................................................................................................................................17 Scrap Tyres........................................................................................................................................18 Caps & Retreads................................................................................................................................18 Punctures............................................................................................................................................18 Workshop Module...............................................................................................................................18 Logged Symptoms.............................................................................................................................19 Create Job card...................................................................................................................................19 Page: 9

Cancel Job card..................................................................................................................................20 Edit of job card...................................................................................................................................20 Trip Planning Module........................................................................................................................20 Initial Agreements..............................................................................................................................20 Final Agreements..............................................................................................................................21 Accessories Items.............................................................................................................................21 Trip Module..........................................................................................................................................21 Departure............................................................................................................................................22 Arrival................................................................................................................................................22 Accidents & Incidents Module............................................................................................................22 Insurance, License & Permits............................................................................................................23 Incidents.............................................................................................................................................23 Accidents............................................................................................................................................23 Report Module ....................................................................................................................................23 Trip Planning Reports........................................................................................................................24 Trip Reports.......................................................................................................................................24 Insurance & Incident .........................................................................................................................25 High Level Design....................................................................................................................................25 Dataflow Diagrams...........................................................25 Vehicle Management Module............................................................................................................25 Job card Creation.....................................................................................................................................27 ...............................................................................................................28 Logical Schema Design.........................................................28 Vehicle Management Module............................................................................................................29 Accidents & Incidents Module...................................................................31 Table: Edit_Job_Card.........................................................................................................................37 Detail Design.............................................................................................................................................38

Page: 10

Page: 11

About Falcon Motors Falcon Motors is one of the premiere transport service company in India. Falcon Motors is a full fledge Transport Services Company with a host of other local offices all over the India. It is committed to excellence to provide services and support to satisfy the customer needs. It is a market-tested leader in delivery services, offering an easy full-fledged delivery of transport services globally. Serving as a strategic advisor and trusted delivery to his clients, it also delivers solutions that are tailored to meet the customer needs through our major product channels. Falcon Motors is the ideal solution for the majority of client time-sensitive deliveries to virtually, whether full or multiple piece delivery. Every day at Falcon Motors, delivers national shipments within with in different states of India. It offers a variety of transport services to meet the different type of customer requirements like to provide the services for Dept Stores and warehouses. Electronic tracking and confirmation of delivery is available on-line through the Internet within minutes of delivery. Services are made to suite individuals' needs. Falcon offers a full fledged of transport services such as:    

  

Delivering different ranges of product from all parts of geographic locations 24x7 support and services Managed by highly experience team to handle any type of circumstances Well equipped modern amenities to handle easy and proper loading and unloading Covers insurance to each trip of delivery Timely delivery, reliability and security Inter –network among different branches with state-of –art technology

Page: 12

Project Overview The Vehicle Management System (VMS ) is the Proactive management science of using and maintaining a fleet of vehicles in such a fashion that whilst spending the minimum amount of money , a Vehicle manager is able to offer his/her users maximum flexibility , availability and reliability. VMS has been developed in conjunction with the Transport Industry in an effort to provide a total web-based solution for Maintenance, Operational and Administrative Controls in any vehicle situation. The competitive nature of our transport world today requires that we manage all aspects of the transport business. The VMS includes customers resources, the vehicles that play an integral part in delivering your products and services to the customer. VMS’S - incredibly focused philosophy:  To provide clients with strategic solutions that offer competitive advantages - resulting in quick paybacks, improvements in long-term costs and excellent customer service.  Specifically: 1. Reductions in total local & global vehicle operating costs 2. Improvements in local & international data control and flexibility 3. Improvements in overall transportation savings The Benefits It is widely accepted by VMS that available feature changes the playing field by providing numerous benefits. The science of Vehicle Management has been forever changed by these benefits : 



Improved Customer Service: more accurate prediction of arrival times, faster pickups and deliveries (dispatch closest vehicle by having real time information), reduce operator tardiness (information makes managing this a reality), Resolve Billing Disputes (recorded arrival and departure times) Efficient Logistics Management: assist lost drivers, eliminate employee downtime, Dispatch at a glance (view part or the entire Vehicle), knowledge will create confidence and reduce stress and assures better management decisions (route evaluation, attract and retrain the best employees, efficient scheduling)

Page: 13



Profitability: serve more customers in less time, save on gas and slow Vehicle wear and tear, reduce unnecessary overtime, minimize unauthorized use of company vehicles, fewer resources to do equal or more work Project Scope

VMS is web-based solution, to fulfill the Falcon Motors requirements. VMS is integrated web-based solution comprises of following modules:       

Vehicle Management Tyre Management Workshop Trip Planning Trip Incidents and Accidents Reports

Detail phases of the engagement:  Requirement gathering and Finalisation of User Requirements  High Level Design  Detail Design  Construction  Unit Testing  Integration Testing  System Testing Solution Architecture Client Tier

Presentation Tier

Browser

Webserver

Database

MS Internet Explorer

Weblogic Server

Oracle 8i

Windows 2000/ME

Windows NT

Database Tier

Windows NT

Page: 14

Technology Used Development Environment 1. Operating System 2. Database 3. Webserver 4. Presentation 5. Client 6. Tools used

Windows NT/2000,Windows ME, 9x Oracle 8i Tomcat/Java Webserver/ iPlanet Webserver/ Weblogic Webserver HTML, Java, JavaScript & JSP MS Internet Explorer, Netscape Navigator Front Page 2000,EditPlus, Toad & Platinum ERWin Deployment Environment

1. 2. 3. 4. 5.

Operating System Database Webserver Presentation Client

Windows NT/2000,Windows ME Oracle 8i Weblogic Webserver HTML, Java, JavaScript & JSP MS Internet Explorer Requirement Details

A modular approach has been followed to provide for the necessary flexibility to use only the modules related to the user's specific environment. Vehicle Management Module Vehicle management module forms the core of the Vehicle Management System. This module provides all relevant information pertaining to the vehicle such as vehicle description, scheduled activities, licensing details and other statistical data. Functionalities: Vehicle Master Info Maintenance Vehicle master keeps basic information of a vehicle. Vehicle Master has that information of vehicle, which are dynamic, and change with every trip of the vehicle .New vehicle addition, edition/deletion of existing vehicles. Queries income

Page: 15

details and cost details (fixed /operational/maintenance cost) attached with a vehicle. Unit Allocation This facility allows the user to allocate Exchange Units to vehicles or placing them back to stores. Scheduled Activities This is for planning planned services, licenses, insurance, permits etc. The user has to specify the last dates and/or odometer readings for these services last provided to ensure that user is timely warned for due activities as period/ distance between two instances of same service is also captured.

Change status This facility allows one to change the status of a vehicle within any of the userdefined status. Alter Registrations This facility allows the user to alter the registration number of a vehicle. This is especially useful where a vehicle has been re-registered due to number plate changes. All costs incurred on the old vehicle are automatically carried over to the new registration number. Fuel Management On receipt of fuel, invoicing facility is provides and user is allowed to print a fuel receipt note. Fuel cannot receive more than the maximum capacity of the tank. At the time receipt of fuel the system will prompt the level of existing fuel. Driver Management This module keeps record of all drivers involved in the business.     

Master maintenance for new and old personnel Attendance management Time card input Leaves & Sick leaves Skill & Training need

Page: 16

TYRE Management Module This module provides for a comprehensive tyre management system catering for tyre identification, wheel positions, expected km life, purchase details. Full tracking per tyre and/or wheel position is provided to enable a detailed analysis of tracked km's, positioning and removal reasons, dates positioned and removed, etc. The system caters for new and retread tyres and each retread life is monitored separately for comparative reasons. Repair costs, casing residuals and amortisation costs enable accurate costing on each individual tyre, as well as costs per vehicle. Full scrapping analysis and repair history is kept to enable management accurate decision making in choosing the correct tyre for the operation.

Functionalities: Tyre Master Maintenance This function allows the user edit old or adds new tyres. ”Pop-up” screens are provided wherever possible to help the user select from listed values. Entries in some critical fields are essential and fixed fields are made non-editable. Editing, deletion and query of an existing tyre is provided on the basis of unique identity number. Tyre Movements This function allows the user to move a tyre from / to a store, vehicle or as a spare on a vehicle. When selecting a vehicle the user has to enter the position and date the tyre has been fitted. Tyre Purchases This facility allows the user to purchase in bulk from a specific supplier. Once the tyres are received the user has to enter for each tyre an identity number, make , type etc. On entry of new tyres , cross checks are done with invoice balance. The user has option of returning goods to the supplier if they have been incorrectly supplied. Then all tyres in the invoice are listed with identity number, make, type and amount. Against each identity number details entered can be seen. The total amount is summed under a head called subtotal. On this subtotal discount % is mentioned and the discount amount shown. Over this delivery charges are added Page: 17

along with tax amount to arrive at total amount. On confirmation a goods received note can be generated and printed. Scrap Tyres This function allows the user to scrap a specific tyre. Caps & Retreads This function allows the user to select and forward tyres to retreaders for retreading / recapping. Once the retreader has completed the job , goods are received back into the stock . This involves following functions: • •

Ship Tyres Receive Tyres

Punctures This function allows the user to enter any costs on the tyre pertaining to a puncture. The user selects a tyre and the account number of the supplier to whom the tyre has been sent for repair. A reference, date, amount charged as well as the current tread depth are entered. Workshop Module The Workshop Module is fully integrated with the Main Module avoiding duplication of entries. Job cards are printed as instruction of work to be carried out. Detailed Performa job cards for different services are created to specify the tasks to be performed, parts to be replaced/repaired as well as standard times for each type of service. As soon as the job card is closed, the details are automatically transferred to the Main Module to update the vehicle detail. This module helps to maintain the details of the vehicle symptoms, the actions taken to rectify them (spares used, labour worked on it and other maintenances undertaken). It also gives the picture of total costs incurred on the vehicle and also on spares, labour and other maintenances. So the user can take the proper decision whether to incur extra expenses on vehicle or not. It also maintains the information in which workshop a particular vehicle has been maintained and the labours worked on it.

Page: 18

Features: • • • • •

• • • •

User of the vehicle can directly report the faults with his experience on a scale of 0 to 9, 9 being the severest. One job card for one vehicle can cater to one or multiple faults existing against the vehicle. A profile exists for rectifying each symptom, which can be called and edited as per the case. Handles scheduled and unscheduled maintenance jobs. Provides information about maintenance labours and spares costs incurred on each vehicle.

Functionalities: Logging symptoms Create job card Cancel job card Edit of job card

Logged Symptoms The user can log scheduled and unscheduled symptoms against a vehicle. User may choose to take action against all symptoms or a few of symptoms logged while creating a job card. He is able to choose the symptom from a user defined list .He can accept the default severity factor and repair cost and time or may override those details according to his own experience or depending upon the vehicles present condition. It gives the details of estimated cost, time and actual cost, time for each symptom in a graphical form. The user can take actions to reduce the cost in future works. He can also cancel the job card when he feels the symptom has been logged unnecessarily. Create Job card The heart of the module lies in creating job card. User creates job card for a vehicle for which symptoms are logged. It checks whether symptoms are logged against a vehicle or not and allows the user to add new symptoms. User may opt to take action against all or few of the logged symptoms. Logged symptoms will be included in the job card when the user creates profiles for that symptom. He estimates spares and their quantity, labours and working hours required and other maintenances required. The user estimates the scheduled out time. It will be checked whether the vehicle is booked in the period in between in and scheduled out timings and the user will be warned if it is booked and allows him to take action accordingly. It will give the details of that vehicle’s maximum maintenances cost and the expenses incurred against that vehicle. So the user can decide to Page: 19

incur further expenses on that vehicle. It also gives the complete details of the vehicle whether job card is being created due to accident or abuse and in and out odometer reading etc. Cancel Job card The user is given the chance to cancel a job card if he feels it is unnecessarily. But however he/she is not allowed to do so once he issues spares, labours to that vehicle. Edit of job card When the vehicle profiles are all attended then the user can close that job card. It gives all Details such as the actual completion date, out odometer reading etc. User gets all the information of the costs incurred on spares, labors and other maintenances. He can also get the picture of how much the vehicle is lagging in time for the delivery. User can compare scheduled out and actual out time and take actions in future endeavors for the time lagging. Trip Planning Module From the functional point of view this module plays very important role as this module controls all sorts vehicle bookings, utilisation contract printing and debtors related reports. It’s one of the advantages is the ability to generate departmental as well as inter company billing. Functionalities: As the name suggests the rental agreement is to give vehicles on rent which is performed through various steps such as:  

Initial Agreements Final Agreements

Initial Agreements Before issuing the agreement it looks for the detailed debtor’s information including postal address, telephone no etc. Allows to enter the date and time out as well as the planned date and time back which also looks for the condition of the vehicles before the delivery to the customer Once the vehicle is not available or there is a conflicting booking then it shows the existing booking along with the option of either canceling or continuing it. All varieties of charging is allowed including: 

Quoted rates incorporating time sheets Page: 20

     

Time Sheets Rates may include/exclude kilometers charge Flat quoted rate Rates may include driver/operator charges Hourly/Weekly/Daily/Monthly rates Rates may allow additional/free kilometers

While estimating charge period of contract depending on the parameters entered it will calculate the chargeable hours , days , weeks , months etc. including whether chargeable for Saturdays /Sundays/Holidays . Final Agreements  See the list of outstanding contracts and select desired contract.  Allow user to change/confirm dates and times in and out which also includes the adding/changing to the collection/delivery details and the remark fields .  It can also calculate the chargeable no. of hours , days , weeks ,months while taking into considerations for Holidays , Sundays and Saturdays if the need arise .  Calculate the discount , tax , and insurance as well as time sheet input .  While calculating Kilometers it takes into consideration the following fact that, “x” no. of kms to be free; next “y” no. of kms to be charged @1 ; “z” no. of kms to be charged @2 ; remaining no. of kms to be charged @3 .  Also it takes care of any new labour charges or any operator.  Allow unlimited different user definable sundry charges, which include delivery, and special charges.  Takes care of Vehicle Damage Insurance (VDI), excess charges and permits. Accessories Items User-defined sundry charges are allowed where ever applicable which may be either hourly, daily, weekly, monthly or flat basis which include if any discountable charge to be listed along with whether it is standard rated, zero rated or exempt from tax. Trip Module Vehicle trip data is recorded in this module and database details of customers and products delivered are captured in this module. Page: 21

Trip Completion and Invoicing can be done through this module. Each Invoice is allocated to a specific vehicle, driver on basis of each trip. Delivery and trip reports are provided as well as detailed analysis regarding cost ratios per trip, per day, per hour, per unit delivered, c/ton-km, etc. Vehicle utilization in terms of time and capacity is also reported on. Trip costing is a crucial element of Vehicle management excels in this area with its very powerful reporting features. The system caters for both kilometers as well as hourly-based vehicles and reports have been designed accordingly. This module tracks all the trips and loads for each vehicle & generates invoice against the customer. Further same invoice can be printed & rise to the debtor for payment. Functionalities: Departure A client or trip profile containing basic information regarding the chargeable trip is entered into the system as a “template” so as to reduce typing at the stage of operation. In addition this profile is used as a record of rates and details standardized. The client order is entered into the system using either the specific trip scheduling that is suitable for amendment to meet the requirements of this particular load and trip. Various orders and loads are grouped into “routes” A number of loads are scheduled and allocated to a particular vehicle and driver to be collected and delivered at specific times and dates. Consignment notes and trip sheet schedules are printed out. Arrival When “Proof of Delivery” (POD) is received, the order is amended to cater for differences in times, tonnage etc. It is then invoiced to the client. Accidents & Incidents Module These module facilities users to maintain the insurance claim maintenance, incidents management and accident management with associate activities related to accidents. Page: 22

Functionalities: Insurance, License & Permits This facility allows the user to enter/update any insurance for a specific vehicle. All costs and dates are recorded against the vehicle as sundry item costs. claims (claimable and non-claimable) as well as "incident" reports relating to driver control, are recorded for disciplinary or merit purposes. Incidents The user requires to keep detailed information about all incidents. So use has the provision to enter new incidents, and edit or delete or query existing ones. Accidents These applications contain most of the information required in the standard insurance and police reports. This sub-module enables the user to add, edit or enquire about any accidents that have occurred. The system stores detailed information such as driver, vehicle, third party information, weather conditions etc. Report Module Report module is fully integrated to the Vehicle Main Module, where most of the global Vehicle Management reporting takes place. Functionalities: Vehicle Reports         

Listing of all vehicle with its attributes Kilometer Report - traveled kilometers/hours and lost kilometers/hour. Running Cost Report Operating Cost Report Vehicle Replacement Report - Based on Replacement Index Availability Report for Vehicles Utilization Report Fuel Receipt Report Meter Reading Report

Page: 23

Tyre Reports       

Listing of Tyres Depth of Tread Analysis Report Tyre Movement Report Scrapped Tyre Report Puncture Report Tyre Location Report Expense Analysis Report

Driver Reports    

Name, Address and contact details List Driver List Productivity Report Availability Report

Workshop Reports: Reports are generated to list job cards, symptoms etc. to facilitate the user with quick overall idea. 







Vehicles Symptoms: It gives a picture of the symptoms logged against each vehicle and estimated cost incurred on individual symptom and also total cost incurred on that vehicle. It also gives the status of the action being taken on the symptom. Job card Listings: It gives the list of all job cards and the status of the job card and reason of the job card etc. Spares shortage Report: It gives the on hand quantity of spares and used and required quantities of spares by the vehicles. So the user can predict the requirement of spares beforehand and can take to procure them. Vehicles exceeding given maintenance cost limit: The user can get the list of vehicles whose Maintenance cost has been exceeded that the amount given by the user.

Trip Planning Reports  Initial & Final Agreement Report  Timesheet Report  Order Report  List Initial Agreements Trip Reports

Page: 24

Following reports are generated for client, route, vehicle and driver.  Trip Sheets  Load Registers  Proof of Deliveries  Fuel consumption  Invoice  Trip-wise expenditure  Periodic Expenditure Insurance & Incident Due Date Reports - License due/ Insurance due/ Permits due/ Warranties due  Accidents reports 



Incidents reports High Level Design Dataflow Diagrams

Vehicle Management Module

START SELECT WORKSHOP LOGG SYMPTOMS OF VEHICLE EXPECTED REPAIR COST APPROXIMATED TIME OF RELEASE ACTUAL REPAIR COST

NO

IS USER AGREE TO CREATE JOB CARD?

YES Page: 25

CREATE JOB CARD LOGIN SYMPTOMS APPROXIMATED OUT TIME INSURED MAINTENANCE INITIAL METER READING INITIAL FUEL LEAVEL

IS USER AGREE TO TAKE ACTION ON EACH LOGG SYMPTOMS?

YES SYMPTOM NAME SPAIRS SYMPTOM ID QUANTITY OF SPAIRS NO OF LABOURS WORKING HOUR OYHER MAINTENANCE

Page: 26

SYMPTOM ID VEHICLE REGISTRATION NUMBER SPAIR COST LABOR COST OTHER MAINTENANCE COST TOTAL COST

Workshop

VEHICLE REGISTRATION NUMBER ACTUAL COMPLITION DATE OUT MEATER READING OUT FUEL LEAVEL COST INSURED ON SPAIRS COST INSURED ON LABOURS COST INSURED ON OTHERMAINTENANCE

*Workshop_ID Workshop_Type *VM_ Regd_No **Entry_Id IN_Date Status App_Date_Of_Release

information

Logging Symptoms *Entry_ID Symptom_List Expected_Repair_Cost App_Date_Of_Release **Vehicle Regd_No

Job card Creation Action on symptoms *Vehicle Regd_No Login symptoms Max. maintenance cost Estimated out time Expenses incurred against vehicle In meter reading In fuel level

*Symptom name Spares Spare quantity No of labors Working hour Other maintenance Vehicle Regd_No Edit job card *Vehicle Regd_No Completion date Out meter reading Out fuel level Insured on labors Insured on spare Final bill Payment by user

Page: 27

Logical Schema Design All the modules including user security logical data structure is as follows:

Page: 28

Vehicle Management Module Table Name: Vehicle_Master Description: To keep track vehicle master data. Index file :Vehicle_Master_Indx0 (VM_regd_no) Sl No 1. 2. 3. 4. 5. 6. 7.

Column Name

Type

Width Key

VM_Regd_No VM_Name VM_Color VM_Model VM_Chesish_No VM_Engine_No VM_Fuel _type

Char 15 Varchar2 20 Varchar2 10 Varchar2 15 Varchar2 15 Varchar2 15 Varchar2 10

8. 9. 10 . 11 . 12 . 13 . 14 . 15 . 16 . 17 . 18 . 19 . 20 .

VM_Company_Add VM_Km/Liter VM_OwnerName

Varchar2 Varchar2 Varchar2

30 10 25

PK

Description Trip departure number Vehicle name Vehicle color Vehicle model Vehicle Chassis number Vehicle engine number Which types of fuel the vehicle uses Company address How Many kilometer per liter Vehicle owner Name

VM_Pur_date

Date

Vehicle purchasing date

VM_Warr_date

Date

Vehicle warrantee date

VM_Permit

Varchar2

20

Vehicle Road permission

VM_A/C_Or_Not

Varchar2

10

Vehicle is a/c or not

VM_Capacity

Varchar2

10

V_Cost

Varchar2

10

VM_ServicingDate

Varchar2

10

VM_Cc_Engine

Varchar2

15

VM_DealerName

Varchar2

20

VM_DealerAddress

Varchar2

30

Page: 29

TABLE NAME DESCRIPTION

TYRE IT TELLS INFORMATION ABOUT DIFFERENT TYPES OF TYRE

Index file :Vehicle_Tyre_Indx0 (VM_regd_no) Sl No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Column Name

Type

Width

VM_Regd_No Fnt_Lft_Tyre_Name Fnt_Lft_Tyre_No Fnt_Rht_Tyre_Name Fnt_Rht_Tyre_No Bck_Lft_Tyre_Name1 Bck_Lft_Tyre_No1 Bck_Lft_Tyre_Name2 Bck_Lft_Tyre_No2 Bck_Rgh_Tyre_Name1 Bck_Rht_Tyre_No1 Bck_Rgh_Tyre_Name2 Bck_Rht_Tyre_No2 Stpn_Tyre_Name Stpn_Tyre_No

Varchar2 Varchar2 Number Varchar2 Number Varchar2 Number Varchar2 Number Varchar2 Number Varchar2 Number Varchar2 Number

15 15 12 15 12 15 12 15 12 15 12 15 12 15 12

Key

Description Vehicle Number given by RTO The name of the front left tyre The number of the front left tyre The name of the front right tyre The number of the front right tyre The name of the back left tyre The number of the back left tyre The name of the back left tyre The number of the back left tyre The name of the back right tyre The number of the back right tyre The name of the back right tyre The number of the back right tyre The name of the step-in tyre The number of the step-in tyre

Page: 30

Accidents & Incidents Module TABLE NAME DESCRIPTION

INCIDENT INFORMATION INFORMATION ABOUT INCIDENTAL CASE OF VEHICLE

Index file: Vehicle_Insurance_Indx0 () Sl No

Column Name

Type

Width

Key

Description

1 VM_Regd_No .

Varchar2

10

Vehicle Registration Number

2 .

VM_Ins_No

Varchar2

10

Vehicle Insurance Number

3 .

Pert_No

Varchar2

10

Vehicle Permit Number

4 .

Trip

Varchar2

10

Vehicle Go to Trip

5 .

Own

Varchar2

10

Vehicle Go to Own

6 .

Drv

Varchar2

10

Vehicle Drive

7 .

Dt_Occ

Date

Date Occurrence

8 .

Tm_Occ

Time

Time Occurrence

9 .

Plc_Occ

Varchar2

10

Place Occurrence

1 0 .

Wh_Rpt

Varchar2

10

Wheather Report

1 1

Visi

Varchar2

10

Visibility Report

Page: 31

Sl No

Column Name

Type

Width

1 2 .

Ins_Clm

Varchar2

10

Insurance Claim Report

1 3 .

Ot_Accr

Varchar2

10

Vehicle Other Accessories Detail

1 4 .

Any Act

Varchar2

10

Vehicle Any Action

TABLE NAME DESCRIPTION

Key

Description

INSURANCE INFORMATION ABOUT INSURANCE TYPE OF VEHICLE

Index file: Vehicle_Insurance_Indx0 () Sl No 1. 2.

Column Name

Type

Width

Key

Description

VM_Regd_No

Varchar2

10

FK

Vehicle Registration Number

VM_Ins_No

Varchar2

10

Vehicle Insurance Number

Page: 32

Sl No 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16.

Column Name

Type

Width

Prt_No Trip

Varchar2 Varchar2

10 10

Vehicle Permit Number Vehicle Go to Trip

Own

Varchar2

10

Vehicle Go to Own

Drv Dt_Occ Tm_Occ Plc_Occ Wht_ Rt Vis_Rt Ins_Clm Ot_Accr Pol_Case Civ/Crim_Case Compen

Varchar2 Date Time Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2 Varchar2

10

Vehicle Drive Date Occurrence Time Occurrence Place Occurrence Wheather Report Visibility Report Insurance Claim Report Vehicle Other Accessories Detail Police Case Civil/Criminal Case Vehicle Compensation

10 10 10 10 10 10 20 20

Key

Description

Table name: Workshop Description: It tells information about the different type of workshop Index file: (Workshop_ID, VM_Regd_No) Sl No

Column Name 1 Workshop_ID .

Data Type

Key

Description

Char (12)

PK

It tells the identification number of the workshop and it also act as a primary key Page: 33

Sl No

Column Name

Data Type

Key

Description

2 Workshop_Type .

Char (8)

3 VM_Regd_No .

Char (12)

PK

4 Entry_ID .

Number (9)

FK

5 In_Date .

Date

6 Status .

Varchar2 (50)

It tells about problems of the vehicle

7 App_Date_Of_Release .

Date

The date in which vehicle release from the workshop

It tells the type of workshop i.e light or heavy It tells the registration number of the vehicle and it is act as a primary key It tells the identification number of the vehicle, given by the workshop when the vehicle enter into the workshop and it is act as a foreign key The date in which the vehicle enter into the workshop

Table name: Log Symptom Description: It tells the information about the problem area of the vehicle Index file:(Entry_ID) Sl No

Column Name

Data Type

Key

Description

1.

Entry_ID

Number (9)

PK

2.

VM_Regd_No

Char (12)

FK

3. 4.

Symptom Expected_Repair_Cost

Varchar2(50) Varchar2(30)

5.

App_Date_Of_Release

Date

It tells the identification number of the vehicle, given by the workshop when the vehicle enter into the workshop and it is act as a foreign key It tells the registration number of the vehicle and it is act as a primary key It tells the problems type It tells the expected cost to repair /replace the above symptoms The date in which vehicle release from the workshop

Page: 34

Table name: Create_ job_Card Description: It tells the information about the creation of job card for the Vehicle Index file: (VM_Regd_No) Sl No

Column Name

Data Type

Key

Description

1 VM_Regd_No .

Char (12)

PK

2 .

Logg_Symp

Varchar2 (50)

FK

It tells the registration number of the vehicle and it is act as a primary key It tells the problems type

3 .

Max_Main

Varchar2 (20)

It tells the maximum cost required for maintenance of the vehicle

4 .

Exp_Inc_Agst_Vehicle

Varchar2 (20)

5 .

Est_Out_Time

Date

It tells the maximum cost incurred against the vehicle for the purpose of maintenance The date in which vehicle may release from the workshop

6 .

Int_mtr_reading

Varchar2 (20)

It tells odometer reading at the time when vehicle in the workshop

7 .

Int_Fuel_Leve

Varchar2 (5)

It tells fuel level at the time when vehicle in the workshop

Page: 35

Table name: Action_On_Each_symptom Description: It tells the information about the action taken against each symptom Index file: (Symptom_Name) Sl No

Column Name

Data Type

1.

VM_Regd_No

Char (12)

2. 3.

Symptom_Name Symptom_ID

Varchar2(20) Char (20)

4.

Date

Date

5.

Affected_Part_No

Char (20)

6.

Spare

7.

Spare_Quantity

8.

NO_Of_Labour

9.

Working_Hour

10.

Other_Maintenance

Varchar2 (50) Varchar2 (60) Varchar2 (40) Varchar2 (10) Varchar2 (30)

Key

PK FK

Description

It tells the registration number of the vehicle and it is act as a primary key It tells the name of the symptom It tells the identification number of the symptom which is given by the workshop Date in which action taken against the symptom It tells the number of that part of vehicle which is affected by the symptom It tells the repair or replace spares of the symptom It tells the quantity of each repair or replace spare It tells the no of labor required to up-to-date the symptom It tells the no of hour required to up-to-date the symptom It tells the information about maintenance which is taken beyond the above maintenance

Page: 36

Table: Maintenance_Cost_Of_Symptom Description: It tells the information about the maintenance cost of the symptoms Index file: (Symptom_ID) Sl No

Column Name

Data Type

Key

Description

1.

Symptom_ID

Char (20)

PK

It tells the identification number of the symptom which is given by the workshop

2.

VM_Regd_No

Char (12)

FK

3.

Spare_Cost

Varchar2(20)

4.

Labor_Cost

Varchar2(20)

5.

Other_Maintenance_Cost Varchar2(20)

6.

Total_Cost

It tells the registration number of the vehicle and it is act as a primary key It tells the cost of the spares which are used to up-to-date the symptom It tells the cost of the labor to upto-date the symptom It tells the cost of other maintenance It tells the final bill to up-to-date the symptom

Varchar2(20)

Table: Edit_Job_Card Description: It tells the information about the vehicle when the vehicle Release from the Workshop Index file: (VM_Regd_No) Sl No

Column Name

Data Type

Key

Description

1.

VM_Regd_No

Char (12)

PK

2.

Comp_Date

Date

3.

Out_Mtr_Reading

Varchar2(20)

4.

Out_Fuel_Level

Varchar2 (5)

5.

Cost_Of_Symptoms

Varchar2(20)

6.

Exp_Inc_Agst_Vehicle

Varchar2(20)

It tells the registration number of the vehicle and it is act as a primary key It tells the date in which the vehicle out from the workshop It tells odometer reading at the time when vehicle out from the workshop It tells fuel level at the time when vehicle out from the workshop It tells the cost expanses to up-todate the symptom It tells the maximum cost incurred against the vehicle for the purpose of maintenance

Page: 37

Sl No

7.

Column Name

Data Type

Final_Bill

Varchar2(20)

Key

Description

It tells the cost the customer have to paid

Detail Design 1. Application Name: Description: Program Name: Program linked Name general function/procedure Tables referred Table updated Trigger used Backend Function/Procedure

Main Manu Main menu screen of the Vehicle Management System. Main.htm

1. hdh 2.

Screen layout – Main menu

Page: 38

Page: 39

Page: 40

Page: 41

Page: 42

Page: 43

Page: 44

Page: 45

Page: 46

Page: 47

Page: 48

Page: 49

Page: 50

Page: 51

Page: 52

Page: 53

Page: 54

Page: 55

Page: 56

Page: 57

Page: 58

Page: 59

Page: 60

HTML CODING <META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="Workshop_information.html" }
Falcon Marine Exports Ltd.
Login Name
Password
   
<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="Workshop_information.html" }

Page: 61

Falcon Marine Exports Ltd.
Login Name
Password
   
<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="Workshop_information.html" }
Falcon Marine Exports Ltd.
Login Name
Password
   


Page: 62

<META http-equiv=Content-Type content="text/html; charset=unicode"> <META content="Microsoft FrontPage 4.0" name=GENERATOR> <script language="javascript"> var a,y,x=1; function fintd() { if(document.getElementById('VEHICLE').value!="") { if(x==1) { x=document.getElementById('VEHICLE').value; a=12-x.length; for(var i=1;i<=a;i++) { x=x+" "; } top.myname.document.getElementById(x).style.background='oldlace'; y=x; } else { x=document.getElementById('VEHICLE').value; a=12-x.length; for(var i=1;i<=a;i++) { x=x+" "; } top.myname.document.getElementById(x).style.background='oldlace'; top.myname.document.getElementById(y).style.background=''; y=x; } } else { alert("ENTER THE VEHICLE REGD NO."); } } function printdoc() { window.print(); }

ABOUT VEHICLE INFORMATION

Select Vehicle Regd No.    



Page: 63

Sl No Vm  Regd No vehicle Name Engine No Company Address Owner Name Purchase Date Dealer Address View/Edit
<iframe src="../jsp/v_master_vehicle1.jsp" frameborder="0" height="250" width="868" border="0" scrolling="yes" name="myname">
_________________________________________________________________________________________ <META http-equiv=Content-Type content="text/html; charset=unicode"> <META content="Microsoft FrontPage 4.0" name=GENERATOR> <script language="javascript"> var a,y,x=1; function fintd() { if(document.getElementById('VEHICLE').value!="") { if(x==1) { x=document.getElementById('VEHICLE').value; a=20-x.length; for(var i=1;i<=a;i++) { x=x+" "; } top.myname.document.getElementById(x).style.background='oldlace';

Page: 64

y=x; } else { x=document.getElementById('VEHICLE').value; a=20-x.length; for(var i=1;i<=a;i++) { x=x+" "; } top.myname.document.getElementById(x).style.background='oldlace'; top.myname.document.getElementById(y).style.background=''; y=x; } } else { alert("ENTER THE VEHICLE REGD NO."); } } function printdoc() { window.print(); }

FUEL MAINTENANCE

Select Vehicle Regd No.    

Sl No Vm Regd No Vehicle Name Fuel Filling Date Fuel Amount Amount Paid Initial Meter Reading   Option


Page: 65

<iframe src="../jsp/V_Fuel_iframe.jsp" frameborder="0" height="250" width="773" border="0" scrolling="yes" name="myname">15656   gggg g

 

 

              &n bsp;           

_________________________________________________________________________________ <META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="v_master_vehicle.html" }

Page: 66

               &nb sp;

            &nb sp;   FUEL MAINTENANCE

             &nb sp;                Vm Regd No
             &nb sp;                Vehicle Type
               &nb sp;              Fuel Filling Date
             &nb sp;                Fuel Amount
             &nb sp;               Amount Paid
             &nb sp;               Initial Meter Reading
             &nb sp;                Vehicle Name
             &nb sp;                         
<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="v_master_vehicle.html" }
 

FUEL MAINTENANCE



Page: 67

Vm Regd No
Vehicle Name
Vehicle Type
Fuel Filling Date
Fuel Amount
Amount Paid
Initial Meter Reading
       
<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="v_master_vehicle.html" }

Page: 68



size=5 face="verdana" >

Vm Regd No
Vehicle Name
Vehicle Type
Fuel Filling Date
Fuel Amount
Amount Paid
Initial Meter Reading
       
<META http-equiv=Content-Type content="text/html; charset=unicode"> <META content="Microsoft FrontPage 4.0" name=GENERATOR> <script language="javascript"> var a,y,x=1; function fintd() { if(document.getElementById('VEHICLE').value!="") { if(x==1) { x=document.getElementById('VEHICLE').value; a=12-x.length; for(var i=1;i<=a;i++) { x=x+" "; }

Page: 69

top.myname.document.getElementById(x).style.background='oldlace'; y=x; } else { x=document.getElementById('VEHICLE').value; a=12-x.length; for(var i=1;i<=a;i++) { x=x+" "; } top.myname.document.getElementById(x).style.background='oldlace'; top.myname.document.getElementById(y).style.background=''; y=x; } } else { alert("ENTER THE VEHICLE REGD NO."); } } function printdoc() { window.print(); }                &nb sp;                               TYRE MASTER MAINTENANCE

                               &nb sp;        Select Tyre No.    



Page: 70

Sl No Vm Regd No    Tyre No   Tyre Name   Vehicle Name Purchase Date   Location   Option
<iframe src="../jsp/V_Tyre_iframe.jsp" frameborder="0" height="200" width="753" border="0" scrolling="yes" name="myname">
<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="v_master_vehicle.html" }

Page: 71

TYRE PUNCTURES
VM Regd No
Tyre Id
Tyre Name
Vehicle Name
Puncture Date
       


<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="v_master_vehicle.html" }

Page: 72

TYRE PUNCTURES
VM Regd No
Tyre Id
Tyre Name
Vehicle Name
Puncture Date
       
<META http-equiv=Content-Type content="text/html; charset=unicode"> <META content="Microsoft FrontPage 4.0" name=GENERATOR> <script language="javascript"> var a,y,x=1; function fintd() { if(document.getElementById('VEHICLE').value!="") { if(x==1) { x=document.getElementById('VEHICLE').value; a=20-x.length; for(var i=1;i<=a;i++) { x=x+" "; } top.myname.document.getElementById(x).style.background='oldlace'; y=x; } else { x=document.getElementById('VEHICLE').value; a=20-x.length; for(var i=1;i<=a;i++) { x=x+" "; } top.myname.document.getElementById(x).style.background='oldlace'; top.myname.document.getElementById(y).style.background=''; y=x; } } else { alert("ENTER THE VEHICLE REGD NO."); } } function printdoc() { window.print(); }

Page: 73


               &nb sp;                               &nb sp;      TYRE PURCHASES

                               &nb sp;         Select Tyre Id.    

Sl No    Tyre Id   Tyre Name Delear Address Purchase Date Amount Paid  Warrenty Period   Option
<iframe src="../jsp/V_tyre_purchase_iframe.jsp" frameborder="0" height="250" width="773" border="0" scrolling="yes" name="myname">


Page: 74

<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="v_master_vehicle.html" }
TYRE PURCHASES
Tyre Id
Tyre Name
Company Address
Delear Address
Purchase Date
Purchase Cash/Cheque
Amount Paid
Warrenty Period
       


Page: 75

<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="v_master_vehicle.html" }
TYRE PURCHASES
Tyre Id
Tyre Name
COMPANY Address
Delear Address
Purchase Date
Purchase Cash/Cheque
Amount Paid
Warrenty Period
       


Page: 76

<META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Motor Vehicle Maintance VEHICLE MASTER page <script language="Javascript"> function display() { location="MANUE.HTML" } function cancel() { alert("Do you want to go the details page") if (alert) location="v_master_vehicle.html" }
TYRE PURCHASES
Tyre Id
Tyre Name
COMPANY Address
Delear Address
Purchase Date
Purchase Cash/Cheque
Amount Paid
Warrenty Period
       


Page: 77

JSP CODING <%@ page language="java" import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <%String userId=request.getParameter("userId"); String Password=request.getParameter("password"); Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); Statement stmt=myConn.createStatement(); ResultSet resultset=stmt.executeQuery("Select * from user_admin where userid='"+userId+"' and passwd='"+Password+"'"); if(resultset.next()) { %> <jsp:forward page="/vms/html/WINFORM.HTML"/> <% } else { %> <jsp:forward page="/vms/loggin.htm"/> <% } stmt.close(); myConn.close(); %> <%@ page import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <% String VM_REGD_NO = request.getParameter("VM_REGD_NO"); String VM_NAME = request.getParameter("VM_NAME"); String VM_COLOR = request.getParameter("VM_COLOR"); String VM_MODEL = request.getParameter("VM_MODEL"); String VM_CHESISH_NO= request.getParameter("VM_CHESISH_NO"); String VM_ENGINE_NO = request.getParameter("VM_ENGINE_NO"); String VM_FUEL_TY = request.getParameter("VM_FUEL_TY"); String VM_COMPANY_ADD = request.getParameter("VM_COMPANY_ADD"); String VM_KMLITER = request.getParameter("VM_KMLITER");

Page: 78

String VM_OWNERNAME= request.getParameter("VM_OWNERNAME"); String VM_PUR_DA= request.getParameter("VM_PUR_DA"); String VM_WARR_D= request.getParameter("VM_WARR_D"); String VM_PERMIT= request.getParameter("VM_PERMIT"); String VM_AC_OR_N= request.getParameter("VM_AC_OR_N"); String VM_CAPACIT= request.getParameter("VM_CAPACIT"); String V_COST= request.getParameter("V_COST"); String VM_SERVICI= request.getParameter("VM_SERVICI"); String VM_CC_ENGINE= request.getParameter("VM_CC_ENGINE"); String VM_DEALERNAME= request.getParameter("VM_DEALERNAME"); String VM_DEALERADDRESS= request.getParameter("VM_DEALERADDRESS"); Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); String template="INSERT INTO VEHICLE_MASTER (VM_REGD_NO,VM_NAME,VM_COLOR,VM_MODEL,"+ "VM_CHESISH_NO,VM_ENGINE_NO,VM_FUEL_TYPE,VM_COMPANY_ADD,VM_KMLITER,VM_OWNERNAME,VM_P UR_DATE,"+ "VM_WARR_DATE,VM_PERMIT,VM_AC_OR_NOT,VM_CAPACITY,V_COST,VM_SERVICINGDATE,VM_CC_ENGINE ,VM_DEALERNAME,"+ "VM_DEALERADDRESS) values(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)"; PreparedStatement pstmt=myConn.prepareStatement(template); pstmt.setString(1,VM_REGD_NO); pstmt.setString(2,VM_NAME); pstmt.setString(3,VM_COLOR); pstmt.setString(4,VM_MODEL); pstmt.setString(5,VM_CHESISH_NO); pstmt.setString(6,VM_ENGINE_NO); pstmt.setString(7,VM_FUEL_TY); pstmt.setString(8,VM_COMPANY_ADD); pstmt.setString(9,VM_KMLITER); pstmt.setString(10,VM_OWNERNAME); pstmt.setString(11,VM_PUR_DA); pstmt.setString(12,VM_WARR_D); pstmt.setString(13,VM_PERMIT); pstmt.setString(14,VM_AC_OR_N); pstmt.setString(15,VM_CAPACIT); pstmt.setString(16,V_COST); pstmt.setString(17,VM_SERVICI); pstmt.setString(18,VM_CC_ENGINE); pstmt.setString(19,VM_DEALERNAME); pstmt.setString(20,VM_DEALERADDRESS); pstmt.executeUpdate(); if(pstmt!=null) pstmt.close(); if(myConn!=null)myConn.close(); %>

Data has been succefully inserted

<%@ page language="java" import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT="">

Page: 79

<% int counter=1; Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); Statement stmt=myConn.createStatement(); ResultSet myresultset=stmt.executeQuery("Select * from vehicle_master"); while(myresultset.next()) { String Vehicle = myresultset.getString("VM_REGD_NO"); %> <% } myresultset.close(); if(stmt!=null)stmt.close(); if(myConn!=null)myConn.close(); %>
<%= counter++%> <%= vehicle%> <%= myresultset.getString("VM_NAME")%> <%= myresultset.getString("VM_ENGINE_NO")%> <%= myresultset.getString("VM_COMPANY_ADD")%> <%= myresultset.getString("VM_OWNERNAME")%> <%= myresultset.getString("VM_PUR_DATE")%> <%= myresultset.getString("VM_DEALERADDRESS")%> " target=parent>View / Edit
<%@ page import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <%

Page: 80

String VM_REGD_NO = request.getParameter("VM_REGD_NO"); String VM_NAME = request.getParameter("VM_NAME"); String VM_TYPE = request.getParameter("VM_TYPE"); String F_DATE = request.getParameter("F_DATE"); String AMOUNT= request.getParameter("AMOUNT"); String PAID = request.getParameter("PAID"); String READING = request.getParameter("READING"); Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); String template="INSERT INTO FUEL (VM_REGD_NO,VM_NAME,VM_TYPE,F_DATE,AMOUNT,PAID,READING) values(?,?,?,?,?,?,?)"; PreparedStatement pstmt=myConn.prepareStatement(template); pstmt.setString(1,VM_REGD_NO); pstmt.setString(2,VM_NAME); pstmt.setString(3,VM_TYPE); pstmt.setString(4,F_DATE); pstmt.setString(5,AMOUNT); pstmt.setString(6,PAID); pstmt.setString(7,READING); pstmt.executeUpdate(); if(pstmt!=null) pstmt.close(); if(myConn!=null)myConn.close(); %>

Data has been succefully inserted

<%@ page language="java" import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <% int counter=1; Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); Statement stmt=myConn.createStatement(); ResultSet myresultset=stmt.executeQuery("Select * from Fuel"); while(myresultset.next()) { %>

String VM_REGD_NO= myresultset.getString("VM_REGD_NO");



Page: 81

<% } myresultset.close(); if(stmt!=null)stmt.close(); if(myConn!=null)myConn.close(); %>
<%= counter++ %> <%=VM_REGD_NO%> <%= myresultset.getString("VM_NAME") %> <%= myresultset.getString("F_DATE") %> <%= myresultset.getString("AMOUNT") %> <%= myresultset.getString("PAID") %> <%= myresultset.getString("READING") %> View/Edit
<%@ page import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <% String VM_REGD_NO = request.getParameter("VM_REGD_NO"); String TYRE_NO = request.getParameter("TYRE_NO"); String TYRE_NAME = request.getParameter("TYRE_NAME"); String VEHICLE_NAME = request.getParameter("VEHICLE_NAME"); String PURSH_DATE= request.getParameter("PURSH_DATE"); String LOCATION = request.getParameter("LOCATION"); Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); String template="INSERT INTO TYRE2_MASTER (VM_REGD_NO,TYRE_NO,TYRE_NAME,VEHICLE_NAME,PURSH_DATE,LOCATION) values(?,?,?,?,?,?)"; PreparedStatement pstmt=myConn.prepareStatement(template); pstmt.setString(1,VM_REGD_NO); pstmt.setString(2,TYRE_NO); pstmt.setString(3,TYRE_NAME); pstmt.setString(4,VEHICLE_NAME); pstmt.setString(5,PURSH_DATE); pstmt.setString(6,LOCATION); pstmt.executeUpdate(); if(pstmt!=null) pstmt.close(); if(myConn!=null)myConn.close(); %>

Data has been succefully inserted



Page: 82

<%@ page import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <% String String String String String

TYRE_ID = request.getParameter("VM_REGD_NO"); TYRE_NAME = request.getParameter("TYRE_ID"); COMPANY_ADDS = request.getParameter("TYRE_NAME"); DELEAR_ADDS = request.getParameter("VEHICLE_NAME"); PURCHASE_DATE= request.getParameter("PUNCTURE_DATE");

Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); String template="INSERT INTO puncture (VM_REGD_NO,TYRE_ID,TYRE_NAME,VEHICLE_NAME,PUNCTURE_DATE) values(?,?,?,?,?)"; PreparedStatement pstmt=myConn.prepareStatement(template); pstmt.setString(1,TYRE_ID); pstmt.setString(2,TYRE_NAME); pstmt.setString(3,COMPANY_ADDS); pstmt.setString(4,DELEAR_ADDS); pstmt.setString(5,PURCHASE_DATE); pstmt.executeUpdate(); if(pstmt!=null) pstmt.close(); if(myConn!=null)myConn.close(); %>

Data has been succefully inserted



<%@ page language="java" import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <% int counter=1; Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); Statement stmt=myConn.createStatement();

Page: 83

ResultSet myresultset=stmt.executeQuery("Select * from tyre2_mASTER"); while(myresultset.next()) { String VM_REGD_NO= myresultset.getString("VM_REGD_NO"); %> <% } myresultset.close(); if(stmt!=null)stmt.close(); if(myConn!=null)myConn.close(); %>
<%= counter++ %> <%=VM_REGD_NO%> <%= myresultset.getString("TYRE_NO") %> <%= myresultset.getString("TYRE_NAME") %> <%= myresultset.getString("VEHICLE_NAME") %> <%= myresultset.getString("PURSH_DATE") %> <%= myresultset.getString("LOCATION") %> View/Edit
------------------------------------------------------------------------------------------------------------------------ <%@ page language="java" import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <% int counter=1; Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); Statement stmt=myConn.createStatement(); ResultSet myresultset=stmt.executeQuery("Select * from purchase");

Page: 84

while(myresultset.next()) { %>

String TYRE_ID= myresultset.getString("TYRE_ID");

<% } myresultset.close(); if(stmt!=null)stmt.close(); if(myConn!=null)myConn.close(); %>
<%= counter++ %> <%=TYRE_ID%> <%= myresultset.getString("TYRE_NAME") %> <%= myresultset.getString("DELEAR_ADDS") %> <%= myresultset.getString("PURCHASE_DATE") %> <%= myresultset.getString("AMOUNT_PAID") %> <%= myresultset.getString("WARRENTY_PERIOD") %> View/Edit
<%@ page language="java" import="java.sql.*" %> <META NAME="GENERATOR" Content="Microsoft FrontPage 4.0"> <TITLE>Moter Vehicle Maintance WORKSHOP INFORMATION VIEW page <script language="Javascript"> function cancel() { alert("Do you want to cancel") if (alert) location="../html/Workshop_information.html"; } <% String vehicle=request.getParameter("VM_REGD_NO"); Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); Statement stmt=myConn.createStatement(); ResultSet myresultset=stmt.executeQuery("Select * from vehicle_master where VM_REGD_NO='"+vehicle+"'");

Page: 85

while(myresultset.next()) { %>



Page: 86

WORKSHOP INFORMATION VIEW

Vehicle Regd No Vehicle Name
Vehicle Color Vehicle Model
Chesish No Engine No
Fuel type Company Address
Km/Liter Owner Name
Purchase date Warranty date
Permit A/C Or Not
Sitting Capacity Vehicle Cost
Servicing Date Cc per Engine
Dealer Name Dealer Address
   
<% } myresultset.close(); if(stmt!=null)stmt.close(); if(myConn!=null)myConn.close(); %> <%@ page language="java" import="java.sql.*" %> <TITLE> New Document <META NAME="Generator" CONTENT="EditPlus"> <META NAME="Author" CONTENT=""> <META NAME="Keywords" CONTENT=""> <META NAME="Description" CONTENT=""> <% int counter=1; Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); Connection myConn=DriverManager.getConnection("jdbc:odbc:vms","vms","vms"); Statement stmt=myConn.createStatement(); ResultSet myresultset=stmt.executeQuery("Select * from purchase"); while(myresultset.next()) { %>

String TYRE_ID= myresultset.getString("TYRE_ID");

Page: 87

<% } myresultset.close(); if(stmt!=null)stmt.close(); if(myConn!=null)myConn.close(); %>
<%= counter++ %> <%=TYRE_ID%> <%= myresultset.getString("TYRE_NAME") %> <%= myresultset.getString("DELEAR_ADDS") %> <%= myresultset.getString("PURCHASE_DATE") %> <%= myresultset.getString("AMOUNT_PAID") %> <%= myresultset.getString("WARRENTY_PERIOD") %> View/Edit


Page: 88

Page: 89

Related Documents