Industrial Automation

“ SANKALAN ”Gathering things together …

Rishabh EnterprisesRishabh Enterprises Sanwer Road,Indore ( M.P. )Sanwer Road,Indore ( M.P. )

for

by :

Kiran Prasad

Kushagra Goyal

Sushil Kumar Singh

MCA IIIrd

semester

04/12/23 "SANKALAN" -Gathering Things Together...

2

Universe of DatabaseRishabh Enterprises:

Having benchmark record in industrial maintenance of:

Heavy industrial motors and

Metal sheet cutting blades.

It is situated at

Agarbatti Complex,

Sanwer Road,

Indore.


3

Rishabh EnterprisesThree main Divisions:

Shah Electricals

Deals with Repairing and Rewinding of old worn-out Motors

Sharp Edge

Deals with Grinding and Sharpening of metal sheet cutting blades

Industrial Visit

Deals with visits to various Industries on the basis of the Request made


4

Rishabh Enterprises

Goals:Timely and successful job completion.

The job completed must be done of good – quality.

Proper administration of business firms.

And total cooperation among all divisions of the organization.

Complete customer satisfaction.

Critical Success Factors:Maintain healthier customer relationship.

Good financial management


5

Rishabh Enterprises

Current System:

No any computerized System

All the jobs are done manually on papers

A Customer comes and submits his Request.

Request

To Purchase or Repair a Motor

For the repair of electrical panel or a starter

To grind or manufacture an industrial Blade,

For an industrial visit.

A job card sheet is filled manually and kept into the


6

Rishabh Enterprises

Current System:Further Processing

A Motor Request to Shah Electricals

Blade Request to Sharp Edge

Industrial Visit Request to the Industrial Visit Division.

spare parts are supplied by purchase division.

Purchase division

old or new motors

Blade manufacturing materials

No record is maintained for the purchases


7

Rishabh Enterprises

Current System:Respective employee tells about the work done

the details about the spare parts used

Final Estimate/ Challan/ Bill is issued at the time of delivery.

Bill is generated manually by the respective employee

particular is delivered to the respective Customer

Manual maintenance of record of Bills issued


8

Rishabh Enterprises

Limitations of Current System:No proper maintenance of information in any parts of the organization.

Manual searching of the previous records stored of each motor.

Problem in recovering the debts on customers as no record is maintained of each customer.

Hard to maintain all records for long duration.

No data of the motors they have in their storehouse,

Exact dimensions of blades are to be kept while remanufacturing the blades, which are not there.


9

Rishabh Enterprises

Limitations of Current System:No records of previous industrial visits

No record is maintained for the Suppliers who supply the spare parts to the organization.

No distinct maintenance of cash book, challan book and bill book for the Customer Transaction.

None of the worker timings are recorded.

Realizing the actual financial loss or profit in every fiscal year is very much difficult.


10

Rishabh Enterprises

Proposed System: Record of all the Customers

Payments of Bills by Customers

Generation of

i. Estimate

ii. Challan

iii. Bill

Record of Login and Logout time of each Employee on daily basis


11

Rishabh Enterprises

Proposed System: Records of all kinds of Motors

Searching of any specific configuration of Motor

Dimensions of all the Blades ordered by particular Customers

Records of all the Industrial Visits made

Records of the whole Stock available and to be purchased

Record of all the Suppliers, payments to be made to them


12

Aim of “SANKALAN”

“To design and develop a fully automated system for the Rishabh Enterprises and thereby learning the concepts of Database Management System.”


13

Objectives of “SANKALAN”

To learn the concepts of Database Management System.

To perform a thorough analysis of working of the whole organization.

To study the problem with the current scenario through fact finding techniques.

To suggest all possible solutions through IT and select the most appropriate solution as project.


14

Objectives of “SANKALAN”

To follow SDLC to develop the system. To develop an appropriate Enterprise Data Model

(EDM) for the system and identify its entities. To develop conceptual, logical and physical model for

the system. To develop Graphical User Interface (GUI) as per

convenience of the user. To implement the physical model, being tested as per

the standards. To document our efforts and analysis in a proper

comprehensible manner.


15

Goals of “SANKALAN”

To make a responsive, easy to operate, fast and

efficient retrieval of information as per the user

requirements.

To provide all material like reports, reminders etc.

that might serve as a helping hand to the users.

To provide adequate information about the customer

transaction etc.

To provide ease in the maintenance of records of

various configurations of motors arriving to the

organization.


16

Goals of “SANKALAN”

To make a database that is consistent, reliable and secure.

To provide correct, complete, ongoing information.

To develop a well-organized information storage system.

To make good documentation so as to facilitate possible future enhancements.


17

Current Scenario

Main dealing of the Rishabh Enterprises is with

CUSTOMER. A CUSTOMER comes to the Organization

at the Reception DIVISION and submits his REQUEST.

A REQUEST may be to Purchase or Repair a MOTOR;

it may be for the repair of electrical panel or a starter. A

REQUEST may be to grind or manufacture an industrial

BLADE, or it may be for an INDUSTRIAL VISIT.

A JOB CARD sheet is prepared manually for

the REQUEST. Requested particular is sent to the

respective DIVISION for the further processing.


18

Current Scenario

A MOTOR REQUEST is sent to Shah Electricals,

BLADE REQUEST to Sharp Edge and an INDUSTRIAL

VISIT REQUEST is sent to the Industrial Visit Division.

While processing the REQUEST if a MOTOR needs

some Spare Parts then these are supplied by purchase

DIVISION. Purchase DIVISION is also responsible for

purchasing of old or new MOTOR and BLADE

manufacturing materials.

On the basis of the job done final Estimate/ Challan/

BILL is issued at the time of delivery.


19

Entity Identification

Customer Division Employee Bill Request Motor Blade Industrial Visit Stock Supplier


20

Enterprise Data Model

Receives

Supplied by

Requires Requires

Forwarded toForwarded to

Prepared by

Pays through

Worked by

Comes to

CUSTOMER

DIVISION

EMPLOYEE

BILL

REQUEST

MOTOR BLADE

STOCK

SUPPLIER


21

Transaction Requirements

System must provide password to the user for their

identification.

User must be able to input and search details about

Customers, their Request.

User must be able to input and retrieve details about

Motor, Blade and any kind of Industrial Visit.

User must be able to view availability of any spare

part and to enter new purchases.

System must provide timely Reminders to the user

about due amount to the Customers & Suppliers and

about expiry date of particulars etc.


22

Input/Output Requirements

Input Requirements:

Details of the employees working in the organization

Details of the customers making request to the

organization

Details of the motor, coming for repairing

Dimensions of the blades, coming for grinding need

to be recorded

Details of the job need to be done during a visit to an

industry.

Records of the old purchased motors need to be

maintained.


23

Input/Output Requirements

Output Requirements: Details of the job done on a particular motor came for

the repair.

Details of the job done on a particular blade came for

the grinding purposes.

Details of the job done by the employee on an

industrial visit.

Record of all the industries visited by the

organization.

Determine schedule for industrial visits.

Generation of challan.

Generation of bills.


24

System Development MethodologySystem development Life Cycle (SDLC):

Project Identification and

selection.

Project Initiation & planning.

Analysis

Logical Design

Physical Design

Implementation

Maintenance


25

Time Scheduling Gantt chartStage of

Development6-14 July

14-21 July

21July-

20Aug

20-30 Aug

1-30 Sep

1-30 Oct

1-15 Nov

15-20 Nov

Project Identification & Selection

*Initiation &

Planning *Analysis

* *

Conceptual Design *

Logical Design *Physical Design & Coding

*Testing &

Implementation

-

Demonstration -


26

Project Identification & Selection

Centre for Advance Technology (CAT)

Rajshahi Palace

Amaltas Hotel

Life Care (C& F)

Rajpal Honda

Mehta Motors

Harsh Honda

Sony World

Veermani Enterprises


27

Initiation & Planning

“Sankalan”Gathering Things Together…

An opportunity to gather data scattered all over the

“Rishabh Enterprises”.

No any computerized system at all.

All the work being done on papers only.

A great opportunity to analyze a Huge Database

and to Design a Database Management System.


28

Analysis Phase

Scheduled a series of meetings with Client 3 meetings with Dheeraj Bhai Shah (The Owner).

6 meetings with Rishabh Shah & various

Employees of the Rishabh Enterprises.

Lots of phone calls to authorized persons.


29

Analysis Phase

Questions asked: Complete organizational Structure

Goals

Existing systems

Problem Areas

What he wants ?

Detailed working Each & Every Section

Business Rules

policies


30

Design PhaseThree steps in Design Phase

Conceptual DesignEnhanced ER Diagram

Logical DesignRelational Data Model

Physical DesignData types & Storage Specification


31

Design Phase

Conceptual Design

Entity Identification

Listing attributes for all the Entities

Relationship Identification

Identification of Weak and Associative Entities

Removal of many to many Relationships

Super type/Subtype classification

Final EER Schema


32

Design Phase Conceptual Design

List of all the Entities Identified from Analyzed Scenario:CUSTOMER CUST_TRANSBILL DIVISIONREQUEST

INDUSTRY_REQMTR_JOB_CARD BLD_JOB_CARDMOTOR BLADEDEMAND STOCKSUPPLIER_STOCK SUPPLIERSUPPLIER_PAYMENT SUPPLIER_BILLWORK_DETAIL EMPLOYEEWAGED_EMP SALARIED_EMPPHONE_DIR TAX_RATEUSER_ACCOUNT


33


Relationship Identification between Entities:

MOTOR poses DEMAND.

“While processing MOTOR, it may pose some

DEMAND for some parts to be purchased. DEMAND

records different Part_Id for each Request_Id, also it

keeps track of Quantity Used and Unit Price of the

part being used.”MOTOR DEMANDposes

A MOTOR may pose DEMAND for zero, one or many

part.

A DEMAND for part can be posed by one and only one

MOTOR.


34


Relationship Identification between Entities:

MOTOR DEMANDposes

D1.

D2.

D3.

D4.

D5.

M1.

M2.

M3.

MOTOR poses DEMAND

A MOTOR may pose DEMAND for one or many part.

A DEMAND for part can be posed by one and only one MOTOR.


35


Identification of Weak & Associative

Entities:

Two Weak Entities identified

DEMAND

SUPPLIER_STOCK

Cured by assigning identifier attribute from owner

Entities.

One Associative Entity (initially)

WORK_DETAIL


36


Super type/Subtype Classification:

Two Super type/Subtype Relations Identified

1.) REQUEST is divided into three subtypes

MTR_JOB_CARD

BLD_JOB_CARD

INDUSTRY_REQUEST

“M” “I” “B”

REQUEST

d

MTR_JOB_CARD INDUSTRY_REQ BLD_JOB_CARD


37


Super type/Subtype Classification:

Two Super type/Subtype Relations Identified

2.) EMPLOYEE is divided into two Subtypes:

WAGED_EMP

SALARIED_EMP

“W” “S”

EMPLOYEE

WAGED_EMP SALARIED_EMP

d


38

S_BILL

MOTOR

BILLDIVISION

REQUEST

CUST_TRANS

SUPPLIER_PAYMENT

STOCK

SUPPLIER_STOCK

DEMAND

MTR_JOB_CARD BLD_JOB_CARD INDUSTRY_REQ WORK_DETAIL

BLADE

WAGED_EMP

CUSTOMER

EMPLOYEE

SUPPLIER

SALARIED_EMP

c

payed_by

relates_to

comes_to

generates

requires

receives

maintains

sent_to

sent_to

poses

poses

maintained_by

supplied_by

receives

c

fulfilled_by

performed_by

Final

EER

Schema


39

Design Phase

Logical Design: Conversion from Entity to Relation

Entity Relation

Attributes Columns

Entity Instances Rows

Relationship Association Foreign Key-Primary

Key Normalization

1st Normal Form

2nd Normal Form

3rd Normal Form


40

Design Phase Logical Design

Conversion from Entity to Relation:

CUSTOMER

Cust_Id Cust_Name Industry_Name Cust_Add Cust_City Cust_State Bal_Due

CUSTOMERCust_Id

Cust_Name

Industry_Name

Cust_Add

Cust_StateCust_City

Bal_Due


41

Design Phase Logical Design Primary key-Foreign key association

between Relations:CUSTOMER


CUST_TRANS

Trans_Id Trans_Amt Cust_Id Bill_Id Trans_Date

BILL

Bill_Id Bill_Date Estemate_Status Delevery_Date Challan_Date Request_Id

Parts_Charges Labour_charges Tax Total_Amt

INDUSTRY_REQ

Request_Id Cust_Id Visitors_Name Request_Desc Desc_Of_Job_Done

REQUEST

Request_Id Cust_Id Particulars Entry_Date Exp_Serv_Date


42

Design Phase Logical Design

Normalization:

First Normal Form:

No multivalued Attribute detected in any of the

Relations

Second Normal Form:

No partial Functional Dependency detected

Third Normal Form:

No Transitive Dependency at all

CUSTOMER



43

Design Phase

Physical Design:

Designing Fields:

Type of data (storage type) used to represent

values of concerned

field.

Data integrity controls built into the

database.

Choosing Data Types:

Minimize storage space

Represent all possible values

Improve data integrity

Support all data manipulations


44

Design Phase Physical Design

Relation: CUSTOMER

Primary Key: Cust_Id

ATTRIBUTE DESCRIPTION DOMAIN VALUES

Cust_Id Customer Id String Not Null

Cust_Name Customer Name String Not Null

Industry_NameName of the concerned

Industry

String Null

Cust_Add Customer Address String Not Null

Cust_City Customer City String Not Null

Cust_State Customer State String Null

Bal_DueBalance Due to

Customer

Number Not Null


45


Choosing Database (Back-End Tool):

SQL Server 2000:

Internet Integration

Scalability and Availability

Enterprise-Level Database Features

Ease of installation, deployment, and use

Data warehousing


46


Choosing Front-End Tool:

Visual Basic Dot Net (VB.Net):

Simple

Object-Oriented

Multithreaded

Robust

Distributed

Dynamic:

Event-Driven


47

Implementation, Coding & Testing

CUSTOMER Table:CREATE TABLE [dbo].[Customer] (

[Cust_ID] [varchar] (10) NOT NULL ,[Cust_Name] [varchar] (40) NULL ,[Industry_Name] [varchar] (40) NULL ,[Cust_Address] [varchar] (80) NOT NULL ,[Cust_City] [varchar] (15) NOT NULL ,[Cust_Pin] [varchar] (6) NULL ,[Cust_State] [varchar] (15) NOT NULL ,[Bal_Due] [decimal](18, 0) NOT NULL ) ;

INSERT INTO Supplier(Supplier_Id, Supplier_Name, Supplier_Add, Supplier_City, Supplier_State) VALUES (@Supplier_Id, @Supplier_Name, @Supplier_Add, @Supplier_City, @Supplier_State);


48

Conclusion

Problem Areas:

Searching of UoD

System Analysis

Selection of DBMS

Representation of various Business Functions into

Codes

Designing of Test Cases

Scarcity of Human Resources


49

Conclusion

Lesson Learned: Experience to convenience the unknown client

(Searching Phase) Live project experience Team working Time management Improve technical knowledge How to follow Database approach. Backup and recovery management. Write what you do, do what you write. Approach of problem solving.


50

The Working Log

Project Leader:Kushagra Goyal

System Analysis:Sushil Kumar SinghKushagra Goyal

Database Design:Kiran PrasadSushil Kumar Singh

Programmer:Kiran PrasadKushagra Goyal

Testing & Documentation:The Complete Team


51

Education

Industrial Automation