A IR BRAKE PARTS MAINTENANCE AND INVENTORY. I NDEX Introduction Company Profile About Existing System Need for the New System Software Tools Used Entity

AIR BRAKE PARTS MAINTENANCE AND

INVENTORY

INDEX Introduction Company Profile About Existing System Need for the New System Software Tools Used Entity Relationship Diagram Data Flow Diagram Data Dictionary Screen Layouts Proposed Enhancement Conclusion Acknowledgment

INTRODUCTION

PROJECT DESCRIPTION

Project Title: Air Brake Parts Maintenance and Inventory

System Facilities: Maintain Inventory. In system employee can easily check warranty period. Standard Inquiry Customize inquiry

System is divided into various modules: Appointment Selling Warranty Maintenance / service inventory invoice

Continue on next page…

Module A - Appointment First of all customer came into office and they order for repairing the parts which parts have fault

and then disscuss the manager for its maintenance warranty and any other expenditure.

Module B - Selling

It sell the all parts of air brake which parts is not repairable. (eg.slack adjuster)

Module C- Warranty: If customer came into his warranty period of any parts then they repair the free of charge and if

warranty period is over then customer pay the charge of their parts.(eg.slack adjuster)

Module D - Maintenance/service: Customer give the parts for repairing/services then we repair their parts and inform to customer for

their damage of parts and their maintance if customer aggry their charges then we repair their parts.

Module E- Inventory

• We can manage the stock of different parts of air brakes and if stock of any parts is not available then we purchase the part for our main branch.

Module F – Invoice

• We can generate the bill and we include the charge of service, maintenance and laboring.

ABOUT EXISTINGSYSTEM

The current system is totally manually, all data is stored on paper, by a master. There is no computerization.

Current System is time consuming.

There are separate books for Order, Invoice, payment, customers detail.

In customer book they write customer name, address, phone no and other details.

master keep track of employee work and write it into employee work book.

ABOUT EXISTING SYSTEM

NEED FOR THENEW SYSTEM

To reduce: Time to do any transaction Man power

To solves following problem: Data Redundancy Improve security

To do Effectively and efficiently task: Maintain inventory and other information. Manually bill calculation. Order process. Inquiry response for customer to appointment.

NEED FOR THE NEW SYSTEM

SOFTWARE TOOLSUSED

Front End Visual Studio 2005

Back End SQL Express

Documentation Tools Microsoft Word 2007 Microsoft PowerPoint 2007

SOFTWARE TOOLS USED

DATA FLOW DIAGRAM

AIR BRAKE PARTS

MAINTANANCE&

INVENTORY

ADMIN CUSTOMER

EMPLOYEE WAREHOUSE

Confirm login

Appointment time

Service Order

Invoice

Warranty Status

Managethe Stock

Confirm stock

Confirm service

Expense(Charge)

Confirm part detail

Customer Reports

Service detail

Receive part detail

0

Request for login

Customer,Service, Payment, Part info

Show Report

SUPPLIER

Order part

Sent part

Payment

Customer detail

Payment

Invoice

E - R DIAGRAM

SERVICES

INVOICE

PARTS

CUSTOMERAPPOINTMENT

SUPPLIER

WARRANTY

EMPLOYEE

ADMIN

User_id PasswordA_id

Date/Time

C_idC_id

Ph_no

City

Email_IdName

Add.

PAY

E_id E_name

Add.Salary

Stock_recrd

Part_idI_id

S_name

S_add.

S_id

S_city

PriceP_Id

Name Size

Part_id

Warranty PeriodWarranty_id

S_id

Cus_id

Part_id

Cus_id

Cash

I_id

TAKE

MANAGE

ASSIGNWORK

HAS

USE SUPPLY

MANAGE

HAS

1

M

1

1 1

1

M

M

M

1

1

1

1

1

1

1

M

1

WAREHOUSE

0 LEVEL DIAGRAM DFD

LOGIN

APPOINTMENT

WARRANTYCHECK

2.0

6.0

1.0

4.0

3.0

SERVICE

PURCHASE

LOGIN

APPOINTMENT

WARRANTY

SERVICE

PURCHASE

EMPLOYEE

ADMIN

CUSTOMER

SUPPLIER

Store Information

Conformation Info.

Store Information

Conformation Info.

Store Information

Conformation Info.

Service damage partRepair part

Store Information

Conformation Info.

Store Information

Conformation Info.

Request To Login

Confirm login

Customer Detail

Conform Appo.

Conform Warranty

Check Warranty

Give damage part

Repair part

Send part

Order part

Login process

Appointment Process

Warranty Process

Service detail

Purchase detail

PAYMENT PAYMENTStore Information

Conformation Info.

Sent bill

Payment

5.0

SELLING

SELLING

INVOICE

Store InformationConformation Info.

Get detail

Update detail

Order part

Send part

Sent bill

Payment

7.0

DATA DICTIONARY

TABLE NAME: LOGIN

FIELD NAME DATATYPE SIZE CONSTRAINTS DESCRIPTION

User_id Nvarchar 50 Primary key Id of user

Password Nvarchar 10 Not Null Password of user

TABLE NAME: APPOINTMENT


Appointment_id

Nvarchar 18 Primary key Id of appointment

Customer_id Nvarchar 10 Foreign Key Id of customer

Part_name Nvarchar 50 Not Null It is a store of part name

Date Date Not Null To store date

TABLE NAME: CUSTOMER_DETAIL

FILEDS NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Customer_id Nvarchar 10 Primary Key Id of customer

Customer_name Nvarchar 50 Not Null Name of customer

Customer_address

Nvarchar 50 Not Null Address of customer

Customer_city Nvarchar 50 Not Null City of customer

Pincode Numeric 6 Not Null Area of code

E-mail Nvarchar 50 Not null E-mail of customer

Contact_no Numeric 10 Not Null Contact no of customer

TABLE NAME:

FILEDS NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Emp_id Nvarchar 10 Primary key It is a id of Employee

Emp_name Nvarchar 50 Not Null It is a name of Employee

Emp_address Nvarchar 50 Not Null It is an address of Employee

Emp_contact Numeric 18 Not Null It is contact no of Employee

Salary Money Not Null Salary of Employee

EMPLOYEE_DETAIL

TABLE NAME:


Inventory_id Nvarchar 50 Primary Key Id of inventory

Part_id Nvarchar 50 Foreign Key It is store part_id

Stock_Record Numeric 18 Not Null It is record of stock

INVENTORY

FILEDS NAME DATA TYPE

SIZE CONSTRAINTS DESCRIPTION

Order_Id Nvarchar 50 Primary Key Id of order

Part_Id Nvarchar 50 Foreign Key It store part_id

Quantity Numeric 18 Not Null Quantity of part

TABLE NAME: ORDER_DETAIL

TABLE NAME:

FILEDS NAME DATA TYPE

SIZE CONSTRAINTS DESCRIPTION

Supplier_id Nvarchar 10 Primary key It is a id of Supplier

Supplier_name Nvarchar 50 Not Null It is a name of Supplier

Supplier_address

Nvarchar 50 Not Null It is an address of Supplier

Supplier_contact

Numeric 18 Not Null It is contact no of Supplier

Supplier_city Nvarchar 50 Not Null City of Supplier

SUPPLIER MASTER

TABLE NAME:


Selling_id Nvarchar 50 Primary Key It is id of selling

Customer_id Nvarchar 50 Foreign key It stores the Customer data

Part_id Nvarchar 50 Foreign Key To store the reference

Selling date Date Not Null To store Selling date

SELLING MASTER

TABLE NAME:

FILEDS NAME

DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Purchase_id Nvarchar 10 Primary Key Id of purchase product

Supplier_id Nvarchar 10 Foreign Key Id of supplier



PURCHASE

TABLE NAME:


Part_id Nvarchar 50 Primary key To store the reference


Part_ price numeric 18 Not Null It is a store of part price

Warranty_period

Nvarchar 10 Not Null It stores the warranty period

PART

TABLE NAME:


Service_id Nvarchar 18 Primary Key id of service

customer_id Nvarchar 50 Foreign Key Id of customer


Vehicle_type Nvarchar 50 Not Null Types of vehicle

SERVICE

TABLE NAME:


Payment_id Nvarchar 18 Primary Key id of Payment

Supplier_id Nvarchar 50 Foreign Key Id of Supplier


Payment_date

Nvarchar 50 Not Null To store the reference

Amount Numeric 18 Not Null Total Amount

PAYMENT_DETAIL

TABLE NAME:

FIELDS NAME

DATATYPE SIZE CONSTRAINTS DESCRIPTION

Invoice_id Nvarchar 50 Primary Key Id of invoice

customer_id Nvarchar 50 Foreign Key Id of customer


Cash Money Not Null To collect the cash


INVOICE

SCREEN LAYOUT

REPORT LAYOUTS

PROPOSEDENHANCEMENT

PROPOSED ENHANCEMENT

In future for billing system the bill is automatically generated. It is possible that in future some other developers can modify this project

because we had done this project in such way that easy to modify. The system is flexible that you can generate more report as required.

CONCLUSION

CONCLUSION

The system developed by us is very efficient, effective, easy and user friendly.

System is a very stable and has a lot of features like: Fast to access Easy for modify and add into database Highly sophisticated

System manages the security. Only authorize employee/administrator can use the system who is having correct user name and password.

System show graphical report. Easy navigation from one record to another. Validations are provided everywhere to reduce the data entry error. Appropriate message if displayed for every transaction performed. Thus, the project has been concluded keeping all the needs and requirements

of system.

THANK YOU

Documents

A IR BRAKE PARTS MAINTENANCE AND INVENTORY. I NDEX Introduction Company Profile About Existing System Need for the New System Software Tools Used Entity