ERP SYSTEM FOR MANUFACTURING

A PROJECT REPORT Submitted by

ANKIT PANCHAL ANKIT R PATEL ANKIT S PATEL

In fulfillment for the award of the degree of

BACHELOR OF ENGINEERING
in Computer Engineering

SVIT, Vasad

Gujarat Technological University, Ahmedabad

December, 2011

Sardar Vallabhbhai Patel Institute of Technology

Computer Department
PROJECT REPORT FOR B.E. 7th SEMESTER

ii

Sardar Vallabhbhai Patel Institute of Technology Computer Department 2011

CERTIFICATE
Date:

This is to certify that the dissertation entitled ERP SYSTEM FOR MANUFACTYRING has been carried out by ANKIT PANCHAL, ANKIT S.PATEL AND ANKIT R.PATEL under my guidance in fulfillment of the degree of Bachelor of Engineering in Computer Engineering (7th Semester) of Gujarat Technological University, Ahmadabad during the academic year 2011-12.

Guide:

Project Guide Mrs. Jayna shah Prof. , CE Department, S.V.I.T., Vasad

Head of Department Prof. B.J. Talati CE Department, S.V.I.T., Vasad

iii

ACKNOWLEDGEMENT
Success comes through team effort, not from an individual. The case in this work is no different. Active involvement of many people made this project a reality and a pleasant experience too. We would take an opportunity to thank them. Firstly we would like to thank our Industry mentor Mr. Tejwani for his active involvement and guidance throughout the time span. Without him it would have been nearly impossible for us to understand what the project demands. The system is huge, not only in term of size, but also in terms of what he wants to put into it Localization and User Experience. It was a big challenge for us, but his guidance cleaned up a lot of confusions. Secondly, we want to thank our Departmental Guide Mrs. Jayna Shah for her guidance through several aspects of the system that only an experience person like her can give. Through her guidance we discovered several new ways of doing the same things, but in a more appropriate and systematic fashion. We thank her deeply. Last but not least we thank our Head of Department, Mrs. Bijal Talati for being there for us whenever we needed any guidance of any sort and helping us not only through the project but throughout our whole journey till present. Ankit Panchal Ankit R.Patel Ankit S.Patel

iv

ABSTRACT
These are the days when Small Businesses are blooming and how. Everyday new businesses surface up. As a startup they have to face their own challenges. But one challenge needs to be addresses upfront managing their business, organization. It consists of not one, two but many things. They need a payroll, Inventory & Customer interface management system to manage all this. And there are several systems out there to solve this too. But the problem is that (1) They are either too costly and/or (2) They are too difficult to use by own. The business owner has no option but to buy the system and then hire some professional to operate it and pay him healthily. But these businesses have to startup at a low budget, this poses a risk. Through this project we aim to target this very vulnerability of these systems. We want to develop and design a new system from scratch that solves the very issues. The two problems pointed out are gracefully solved by developing the system exclusively for the small-medium businesses and developing them with keeping usability in mind. This solves both the problems altogether.

LIST OF TABLES

Table No. Description

Page No.

Table 4.4 Timeline Chart Table 6.3.2 Data Dictionaries for the system

Error! Bookmark not defined. Error! Bookmark not defined.

vi

LIST OF FIGURES

Fig. No. Description Fig. 4.1 Fig. 6.1 Fig. 6.2 Fig. 6.3 Fig. 6.4 Fig. 6.5 Waterfall Model Level 0 DFD Level 1 DFD Level-2 DFD for Payroll System Level-2 DFD for Inventory System Entity Relationship Diagram for the system

Page No. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined.

vii

LIST OF SYMBOLS, ABBREVIATIONS AND NOMENCLATURE

Term Description

Inventory

Inventory is total amount of goods and/materials contained in a store or factory at any given time. Production means creating/manufacturing a commodity in large quantities. An employee contributes labor and expertise to an endeavor of an employer and is usually hired to perform specific duties which are packaged into a job. An item is a good, commodity, or service that is traded or rendered for the purpose of business. An item can be raw material, finished goods, by-products, or service A Bill of Material (BOM) can be referred to as defining the composition for manufacturing/producing an item. Bill of Material signifies the consumption and production relation between the items In a company, payroll is the sum of all financial records of salaries for an employee, wages, bonuses and deductions. An invoice or bill is a commercial document issued by a seller to the buyer, indicating the products, quantities, and agreed prices for products or services the seller has provided the buyer. An invoice indicates the buyer must pay the seller, according to the payment terms. The buyer has a maximum amount of days to pay for these goods and is sometimes offered a discount if paid before the due date.

Production

Employee

Item

Bill of raMaterial or BoM

Payroll

Invoice

viii

Attendance Management

Attendance management is the act of managing attendance or presence in a work setting to minimize loss due to employee downtime. Usability is the ease of use and learnability of a humanmade object An item is a good, commodity, or service that is traded or rendered for the purpose of business. An item can be raw material, finished goods, by-products, or service

Usability

User Interface or UI

Material

Material is anything made of matter, constituted of one or more substances Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is used to develop console and graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact Framework and Microsoft Silverlight Administrator can serve as the title of the general manager or company secretary who reports to a corporate board of directors. A voucher is an accounting document representing an internal intent to make a payment to an external entity, such as a vendor or service provider

Visual Studio

Administration

Voucher

ix

TABLE OF CONTENTS
Acknowledgement Abstract List of Tables List of Figures List of symbols, abbreviations and nomenclature Table of Contents iii v vi vii viii x

Chapter 1. Introduction to the system 1 1.1. Detailed Description of Problem Error! Bookmark not defined. 1.1.1. Manual Payroll System Error! Bookmark not defined. 1.1.2. Manual Inventory & Production ManagementError! Bookmark not defined. 1.1.3. Customer Interface Management Error! Bookmark not defined. 1.2. Objectives of the system Error! Bookmark not defined. 1.3 Limitations of the system 6

1.4

Scope
4 5 5 Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined.

Chapter 2. Brief history of the work Chapter 3. Literature Survey 3.1. ERP Accounting Module 3.1.1. General Ledger 3.1.2. Inventory Management 3.1.3. Project Management 3.1.4. Purchase 3.1.5. Sales and Receivable 3.2. Accounting Functions 3.2.1. Recognizing 3.2.2. Measuring 3.2.3. Recording 3.2.4. Disclosure 3.2.5. Accounting standards 3.2.6. Financial Statements 3.2.7. Fundamental Accounting Model 3.2.8. Transactions 3.2.9. Accounting Process 3.3. Localization

3.3.1. Localization vs. Translation 3.3.2. Language codes 3.3.3. Importance of Localization 3.4. Transliteration 3.4.1. Definition 3.4.2. Implementations Chapter 4. Project Planning 4.1. Software Process Model 4.2. Tools and Technology 4.2.1. Software requirements For Development 4.2.2. Hardware requirement for Development 4.2.3. Software requirement for Implementation 4.2.4. Hardware requirement for Implementation 4.2.5. Overview of ASP.NET 4.3. 4.4. Team Organization Timeline Chart

Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. 8 8 12 Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined.

14 Error! Bookmark not defined. 17 Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. 23 Error! Bookmark not defined. 24 Error! Bookmark not defined. Error! Bookmark not defined. Error! Bookmark not defined. 34

Chapter 5. System Analysis 5.1. Feasibility Study 5.1.1. Technical Feasibility 5.1.2. Economic Feasibility 5.1.3. Schedule Feasibility 5.1.4. Operational Feasibility 5.2. Requirement Specification 5.2.1. Functional Requirements 5.2.2. Non-Functional Requirements Chapter 6. System Design 6.1. Design Methodology 6.2. Data Flow Diagrams 6.3. Database Design 6.3.1. E-R Diagram 6.3.2. Data Dictionary References

xi

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

CHAPTER 1. INTRODUCTION TO THE SYSTEM

1.1DETAIL DESCRIPTION OF PROBLEM

The industry not just requires a business solution, but it is in need of a solution that solves the most basic problems that have been overlooked. There are three straightforward but difficult problems in front of the industry. Each problem is discussed in detail. 1.1.1 Manual Payroll System In this Company Bio-metric machines are used for attendance of employees, but payroll system is done entirely by hand. The problems with a manual system are many. The room for error is high, because all payroll tasks are done manually. This includes calculating time sheets, wages, and taxes. And also include preparing Work-to-Salary, verifying the payroll and recording payroll transactions. Tax errors can easily occur with this system, resulting in penalties from the government. Its difficult to generate day to day report manually. In this system to manage all the details of employees and customers is not too easy. In this system all the important documents are not completely secure because paper may be damaged naturally or by any human being. 1.1.2 Manual Inventory & Production Management In this company all the entries of purchases of raw-materials are done on paper. So, the chances of errors are very high. And counting of used, wastage raw materials and remaining raw materials are not done approximately .This system includes production records and raw-material purchases. This process is very complex as every detail has to written on paper. Different products which company manufactures or purchase from some other company has to be recorded manually. And manufacturing process take more time and not finished at proper time. In this system more chances of error in manufacturing process because manufacturing process is not handled electronically. So, product may not be finished properly as per planning.

Page 1

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

1.1.3 Customer Interface Management In this system customer cant be able to interact with company without visiting company .customer has to visit company for purchase any proper product. Even customer cannot get details of product, or purchase that he/she want to purchase without face to face interface. Many similar solutions are available in the market already. But users face several difficulties in using them. And it is not secure. User may require proper knowledge because it is not user friendly.

1.2 OBJECTIVES
The system we are going to develop has several objectives. Some of them are described below: Maintain employees information efficiently. Take price quota immediately. Easily determine price of goods. Easily manage manufacturing process. Easily manage inventory of raw-materials. Easily get different kind of business reports. Reduce their cost on managing organization.

1.3

Limitations of the system

During our visit at nasu engg. we were offered an ERP software for manufacturing Industry. Here are the problem points: Communication within the employees was not as fast as it should be. The time required for the preparation of the paper work, which when delays are involved makes it increasingly less valuable. Errors and inaccuracies detract from the value of the finished product. The security of the paperwork may not be considered soundproof and is always a threat when more important documents are considered. Requirements of employees were handled but there was not record of requirements so further planning was facing some problem. Rescheduling process needs all record of previous work. This task is very difficult here.

Page 2

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

1.4

Scope

Production Department Scope of ERP system is very broad in production department as this software includes Scheduling,Capacity,WorkflowManagement,CostManagement,QualityControl.

Supply Chain Management Inventory, Order Entry, Purchasing,, Supply Chain Planning, Supplier Scheduling, Inspection of goods.

Financials Cash Management, Accounts Payable , Accounts Receivable.

Projects Costing, Billing, Time and Expense, Activity Management

Human Resources Human Resources, Payroll, Training, Time & Attendance, Benefits

Customer Relationship Management Sales and Marketing , Service, Customer Contact .

Page 3

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

CHAPTER 2. BRIEF HISTORY OF THE WORK

When we visited nasu engg. We came to know about the problems they are facing in their industry.They told us three problems which are manual payroll system,manual inventory management and customer interface management.We will build an erp system which will solve all problems of the industry. Our first module is payroll system which will include all the employee attendance details.Then comes inventory management which will include all raw material details,sales,purchase order.Customer interface module will create interface between system and customer. We have included data flow diagrams,er diagram,and data dictionary.

Page 4

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

CHAPTER 3. LITERATURE SURVEY

3.1.

ERP MODULES

Enterprise resource planning (ERP) systems integrate internal and external management information across an entire organization, embracing finance/accounting, manufacturing, sales and service , customer relationship management, etc. ERP systems automate this activity with an integrated software application. Their purpose is to facilitate the flow of information between all business functions inside the boundaries of the organization and manage the connections to outside stakeholders.

3.1.1 Inventory Management Efficient inventory management should be able to rapidly respond to customer requirements; at the same time should be flexible enough to undertake any corrections when required, and do the so without adversely affecting operational efficiencies. The ERP Inventory Management module offers effective features to minimize warehousing costs and to optimize storage needs in line with the requirements at hand. The ERP inventory management module offers a host of advanced warehousing features such as modification, balancing, transfer, and reverse operations. Many features including management of multiple storage centers and locations, specialised inventory management features (serial numbers, batch tracking, and special stock), which are part of a diverse capability in inventory management, are included as standard functionality within the ERP Inventory Management module. Inventory management within the ERP system provides a high degree of flexibility for handling complex storage needs, and assures continuous update of warehouse inventory through multiple inventory methods and different types of auditing. All materials input and output transactions are fully automated due to the seamless integration with other associated modules within the system. This also enables efficient, prompt and trouble-free inventory transactions within enterprises.

3.1.2 PURCHASING MANAGEMENT ERP is an advanced, web-enabled Supply Chain Management and Execution solution. It is designed to reduce supply chain costs, reduce inventory and increase operational efficiencies. It delivers significant return on investment (ROI) by increasing supplier visibility, enabling inter-enterprise communication, and providing a high level of systems integration.

Page 5

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

3.1.3 CUSTOMER RELATIONSHIP MANAGEMENT

To achieve these objectives you need solutions that provide rapid access to centralized customer information. You should also be able to access detailed and up-to-date communication history to foster customer and prospect relationships, close sales and streamline all customer contact activities. ERP offers consistent and readily available customer and prospect data, allowing you to manage pre-sales activities, perform automated sales processes, deliver consistent customer service, evaluate sales and service successes and identify trends, problems and opportunities.

Benefits at a glance

Interaction with other areas of the system, gives you a 'clear' view of the customer Maximizing opportunities and retaining high value customers enhances revenue and profit. Provides value-added services enable you to stay ahead of your competitors. Improves product development and service delivery processes Prepare your personnel with in-depth knowledge of the customer's needs Organizes the customer experience through quick problem resolution

Successful customer interaction The ERP CRM module helps you know your customer better and includes many features such as activities, history, related contacts, addresses of your customers and their relations with your competitors. The flexible database structures enables you whatever information you would like to keep on your customer and maintains such information for your future reference. The ERP CRM module also facilitates control and organization of entire sales process, from offer to invoice. It empowers your sales staff by providing details such as inventory status, estimated costs and delivery time, risk status, habits and special demands, and previous trades during offer stage. The ERP CRM module offers an effective customer complaint management tool which also includes repairs processing and document management.

Page 6

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

3.1.4 Bill of Materials (BoM) Bills of Materials (BOM) are normally accessed according to production or procurement deadlines. The History Management function allows several types of BOM to be managed simultaneously, and can be operated according to the needs of the customer. The advantage of this function is that changes of (data regarding) common components need only be carried out in the Reference BOM-M. The data of BOMs is automatically shown against the work orders providing the ability to include configured items on a WO's BOM. This gives the stores department to check if the stock of materials is available for a product manufacturing or batch manufacturing. Once the individual customer order is entered, it specifies how much components are required, the quantity including wastage and at what level of production the components will be required. ERP Bills of Materials are completely integrated into the system and support:

The procurement of materials at the optimum time (Material Requirement Planning module) The placing of production orders (Production Planning and Control Module) The issue of goods (Inventory Management Module)

Page 7

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

CHAPTER 4. PROJECT PLANNING

4.1. SOFTWARE PROCESS MODEL

Software process model is a Software Development Life Cycle model, is a representation of various activities required to make software project. Each phase consists of various activities to develop the software project gradually. There are various process models viz. waterfall model, prototype model, spiral model, incremental model, etc. From these we are going to use waterfall model in our software project. The software development team must decide the life cycle model that is to be used for software project development. This is necessary because the software product development can be done systematically. Each team member will understand what the next activity is and how to do it. Waterfall model: Waterfall model is also known as Linear Sequential Model or Classic Life Cycle Model. It is the oldest software paradigm. This model suggests a systematic, sequential approach to software development. The software development starts with requirements gathering phase followed by analysis, design, coding, testing and maintenance The different phases of Software Development Life Cycle are as follows.

System Engineering Analysis

Design

Coding Testing

Page 8

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

i.

Phase - 1 -Problem Identification

In this phase, the Problem Statement is been defined which describes the user Problem as a whole.

ii.

Phase - 2- Requirement Analysis

In this phase, the document containing the details about the System to Be Is generated which is known as Software Requirement Specification (SRS). Objective of this document is to understand nature of system to be build. This Document covers details like problem statement, Man power required to build System, hardware & Software Configuration, Time Period, System Infrastructure etc. Simultaneously, Data collection is also performs in which the transactional & Master data of existing system are collected. These data will be used later at the Time of validation, verification and testing of new system.

iii.

Phase -3 - System Modeling

In this phase, the document known as Software Design Specification (SDS) is generated, which shows graphical representation like DFDs etc. of System to be? This phase mainly focuses on four distinct attribute of the system: Data structure, software architecture, interface representation and procedural Details. Using these diagrams the validation process is being carried out using The Collected data to validate software and procedural details.

iv.

Phase - 4 - Designing

In this phase, the system user interface is defined and verified against the SDS. If any conflict occurs in the problem definition or designing, the SRS or SDS Documents review or redesign.

v.

Phase 5 - Coding

After validating & verifying SDRS Documents, the design is translated into a Machine readable form. This phase perform this task. Simultaneously, user manuals are also generated for testing purpose.

vi.

Phase - 6 Testing

Once code has been generated, program testing begins with collected data. The Testing process focuses on the logical internals of the software, ensuring that all Statements have been tested, and functional externals; that are, conducting tests to uncover errors and ensure that defined input will produce actual results that Agree with required results. This phase includes both alpha & beta testing

Page 9

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

Software Model
Each project need to be developed with software model which makes the project with high quality, reliable and cost effective. We have chosen Waterfall Model for developing the ERP system.

I.

Introduction

The Waterfall Model derives its name due to the cascading effect from one phase to the other as is illustrated in Figure. In this model each phase well defined starting and ending point, with identifiable deliveries to the next phase The model consists of six distinct stages, namely:

i. Requirement Analysis Phase

In the Requirement Analysis phase The problem is specified along with the desired service objectives (goals) The constraints are identified

ii. Specification Phase

In the Specification phase, the system specification is produced from the detailed definitions of (a) and (b) above. This document should clearly define the product function.

iii. Design Phase

In the system and software design phase, the system specifications are translated into a software representation. The software engineer at this stage is concerned with: a) b) c) d) Data structure Software architecture Algorithmic detail and Interface representations

The hardware requirements are also determined at this stage along with a picture of the overall system architecture. By the end of this stage the software engineer should be able to identify the relationship between the hardware, software and the associated interfaces. Any faults in the specification should ideally not be passed down stream

Page 10

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

iv. Implementation and Testing Phase

In the implementation and testing phase stage the designs are translated into the software domain a) Detailed documentation from the design phase can significantly reduce the coding effort. b) Testing at this stage focuses on making sure that any errors are identified and that the software meets its required specification.

v. Integration and System Testing Phase

In the integration and system testing phase all the program units are integrated and tested to ensure that the complete system meets the software requirements. After this stage the software is delivered to the customer The maintenance phase is usually the longest stage of the software. In this Phase the software updated to:

vi. Maintenance

a) Meet the changing customer needs b) Adapted to accommodate changes in the external environment c) Correct errors and oversights previously undetected in the testing phases d) Enhancing the efficiency of the software Observe that feed loop allow for corrections to be incorporated into the model. For Example a problem/update in the design phase requires a revisit to the specification Phase. When changes are made at any phase, the relevant documentation should be updated to reflect that change.

II.

Advantages
i. ii. iii. Testing is inherent to every phase of the waterfall model It is an enforced disciplined approach It is documentation driven, that is, documentation is produced at every stage

The reason to choose this model for our project is: It is simple to implement. In our project, we have followed this model strategy which helps us to prepare a better final product. One effective use of this type of model is for product development, in which the developers (we) themselves provide the specifications and therefore have a lot of

Page 11

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

control on what specifications go in the system and what stay out. In fact, most products undergo this type of development process.

4.2.

TOOLS AND TECHNOLOGY

4.2.1 Hardware requirements for development:

A computer having 512 MB RAM or higher. Processor : Pentium or higher

4.2.2 Software requirements for development:

Platform: Windows XP or higher. Database: MS Access Language: C#.NET

4.2.3 Hardware requirements for implementation:

Client Side : Any GUI based terminal having at least 800 * 600 screen resolution 512 MB Ram Processor: Pentium 4 or higher

Server Side: RAM: 512 MB or higher Processor: Pentium 4 or higher

4.2.4 Software requirements for implementation:

Server Side : Platform: Windows XP or higher Web server: IIS Database: MS Access Server side scripting: ASP.NET

4.2.5 OVERVIEW OF ASP.NET

ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. Page 12

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages. Features of ASP.NET Improved performance Flexibility Configuration settings Security Web Hosting

Overview SQL Server 2008 Microsoft SQL Server is a relational database server, developed by Microsoft: It is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). SQL server 2008 makes giants strides in performance, reliability and scalability, giving your organization many opportunities to create intelligent, real world business solutions. By voicing a need for more simplified and cost-saving features, organizations inspired the following innovation in SQL Server 2008.

Scalable from laptop to multiprocessor luster Dynamic row-level locking Dynamic self-management Wide array of replication options SQL Server Desktop Integrated OLAP services Data transformation services Microsoft English query

These innovations, plus many more changes, make SQL Server highly scalable and excellent for data warehousing.

The software does not encourage the entry of any malware that can cause any problems with the computer of the user. The user is ensured that there would be no data loss while using this software.

Page 13

SVIT/COMP/2011-12/21 Why Visual Studio? Parallel Development

ERP FOR MANUFACTURING SYSTEM

Microsoft now provides an environment that will help do this through Visual Studio IDE support for Parallel development and Native C++ libraries and compiler support for parallel applications. Coding Improvements

A new editor uses Windows Presentation Foundation technology to provide integrated support that helps you understand your code. Web Development

A new set of ASP.Net tools allows developers to use TDD to build Model-ViewController (MVC) based websites. Modeling Tools

Using VSTS 2010 Architecture, both technical and non-technical users can work together to model business systems using either UML or DSL this modeling capability is part of the Oslo modeling platform.

4.3.

TEAM ORGANIZATION

Team organization is a complete management of distributing work in a team. Distributing equal workload according to the team members capability is a difficult task. Our team members consists of three members Ankit Patel , Ankit Panchal and Ankit patel. Team Organisation our system is: My team member Ankit Panchal will maintain the payroll system and will work on employee management. Second team member Ankit is working on inventory management where all sales and purchase orders are done. And third member of my team Ankit will look after customer interface management where he will look after customer requests.

Page 14

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

4.4

TIMELINE CHART

Activity

1 July-31 July

1 Aug-25 Aug

26 Aug-10 Sep

Problem summary

Feasibility Analysis

Requirement Determination

Fig 2. Timeline chart 1

Activity

10 Sep-25 Sep

26 Sep-20 Oct

20 Oct-21 Nov

Requirement Analysis

Requirement Specification

Procedural diagrams

Fig.3 Timeline chart 2

Page 15

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

Activity

22 Nov-25 jan

26 Jan-20 Mar

20 Mar-1Apr

Design

Coding

Testing

Fig.4 Timeline chart 3

Page 16

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

CHAPTER 5. SYSTEM ANALYSIS

5.1 FEASIBILITY STUDY

A Feasibility study is an evaluation of a proposal designed to determine the difficulty in carrying out a designated task. Main purpose of software we are going to built is to enable management to make decision easily on market trend and managing selling of product online. The new system will allow customers to place order online and buy the product online. A feasibility study helps answer Should we proceed with the proposed project idea? Is it a viable business venture? Feasibility studies aim to conducted in order to determine the viability of an idea BEFORE proceeding with the development of software. It is useful to see whether the solution to the problem is both economically and technically possible. Feasibility study is useful to identify whether the cost of development is justified by the expected benefits of not? It is also helps us to understand the alternatives possible and tradeoffs that need to be made. 5.1.1 TECHNICAL FEASIBILITY Technical feasibility identifies whether the following required for our system is available or not. It is a study of resource availability that may affect the ability to achieve and acceptable system. To find out whether the actual system is feasible or not i.e. whether our system will work properly or not, the technologies has to be investigated. Technical Feasibility determines whether the work for the project be done with the present equipment, current procedures, existing softwares technology and available personnel? Technical feasibility requires close examination to the present system.

Page 17

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

Technical feasibility performs following checks. Hardware resources Software resources Other support facilities There are number of technical issues which are generally raised during the feasibility stage of investigation. The technical feasibility involves the study about the availability of the tools required for the proposed system. Here the tools involve the hardware required for the development and the implementation of the system. The technical needs of the system may vary considerably, but might include: The facility to produce output in a given period of time. Response time under certain conditions. Ability to process a certain volume of transaction at a particular speed. Facility to communicate data to distant location.

Hardware Feasibility
Server: Client: CPU 1.8 GHz, dual core RAM 1GB Network 100Mb/s CPU 2.4 GHz, core i-5 RAM 4GB Network 1Gb/s

Software Feasibility
The S/W requirements for developing this system are as follows: Windows 7 / Vista / XP (Service Pack 3) Visual Studio 2010 (ASP.NET 4.0 using C#) SQL Server 2008 SP2

Page 18

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

Technical feasibility tries to answer the following question to develop the feasible software. The software or tools for building or running the application are easily available or not? Here, we have preferred Microsoft visual Studio for development of our application which is already available in our company. The compatibility amongst software exists or not? Yes this software is compatible. Are developers aware of these chosen technologies? Yes, these selected technology has greater advantages. So all developers are aware of it. What about the alternatives of these chosen technologies? Enough hardware requirements like 1 GB RAM, 80 GB HARD DISK, P4 3.0 GHz Processor are provided by the company. So, the project is technical feasible.

5.1.2 ECONOMICAL FEASIBILITY

Economic analysis is the most frequency used method for finding the perfectness of a new system. In Economic feasibility cost benefit analysis is done in which expected costs and benefits are evaluate. Economic analysis is used for evaluating effectiveness of proposed system. In our system profits are high because of good selling of products. As there are less complexities in our project, chances are very less of company getting into financial loses. So this project is economical feasible.

Page 19

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

5.1.3 SCHEDULE FEASIBILITY

The most important thing is that the project gets completed in allotted time. We have project duration of 2-semester (i.e. one year) and all the work should be performed by us.

5.1.4 OPERATIONAL FEASIBILITY

Building of application is different from operating it. Operational feasibility includes whether software we are going to built will work properly or not. In operational feasibility, basic question which is needed to be answered is Is it possible to maintain and support this application once it is ready? Operational feasibility checks whether user of the system will be able to work with the software or not. The basic need of this feasibility check is if user is not satisfied with system that is if user is not able to work with the system then coded system is just wastage of time as well as money too. This phase checks whether the software is user friendly or not. Operational feasibility measures how well the solution will work in the organization and how will end-user fells about the system. Proposed system is helpful for the analyzing and decision making related to material requirement, planning and scheduling. Thus, system is operationally feasible to develop the proposed system.

Page 20

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

5.2 REQUIREMENT SPECIFICATION

5.2.1 FUNCTIONAL REQUIREMENT
Functional requirement should describe all the required functionality or system services. Functional requirement are heavily dependent upon the type of software, expected users and the type of system where the software is used. For our system the functional requirements is listed below: The system should store the data safely and never reveal that data. This is done by security methods (authentication). The system shall be able to map the sales order invoice entry with clients purchase order so that the receipt is generates automatically. The required information would be evaluated for completeness and validity. Upon success, the information will be recorded in the database for later use. Manager must Work can be allotted to the employees from anywhere. Ease of expansion/growth and increased flexibility. It provides a comprehensive enterprise view. It makes realtime information available to management anywhere, any time to make proper decisionsbe able to see purchase order provided by the related employee. User management is handled by Employee Management module of the system. This provides information of user when needed Any kind of defects can be handled from any time anywhere

5.2.2 NONFUNCTIONAL REQUIREMENT

The non functional requirement defines properties and constraints. Non functional requirements are more critical than functional requirements. If the non functional requirement do not meet then the complete system is of no use. Non functional requirement of our system are defined below: Reliability: The software we are going to develop is reliable. Interoperability: This software is capable of running on any system of intergroup companies. The software is interoperable. Security: The data stores in the database are secure. We provide the username and password type facility, so any intruder cant be able to reveal data.

Page 21

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

Flexible: The software is flexible. That means it is easy to use. Anyone can able to operate this software. User manual will be provided for better understanding. Supportability: Supportability refers to the software's ability to be easily modified or maintained to accommodate typical usage or change scenarios. For instance, in our help desk example, how easy should it be to add new applications to the support framework? Here are some examples of supportability requirements: The system shall allow users to create new workflows without the need for additional programming. The system shall allow the system administrator to create and populate Email and news. Security refers to the ability to prevent and/or forbid access to the system by unauthorized parties. Only authorized system administrators shall be permitted to access employee profile. Usability : Usability describes the ease with which the system can be learned or used. A typical usability requirement might state:

The system should allow novice users to install and operate it with little or no training. The end user shall be able to given privileges as per the role of the user. The end user shall be able to access page within four seconds.

Page 22

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

CHAPTER 6. SYSTEM DESIGN

Design is needed to develop a quality product. Design is the only way by which we can accurately translate the customers requirements into a finished software product or system. Design allows a software engineer to create a model of the system that is to be built. A large number of users can be involved in development process if design model is prepared. In short, design is a place where software quality can be assured.

6.1 DESIGN METHODOLOGY

For designing the system, there are two methods: 1. Object oriented method 2. Procedural method We are going to use procedural method. We have design the data flow for software by using some diagrams (DFDs and E-R diagrams). In procedural methodology, the analyst draws data flow diagram for showing proper flow of data and entity relationship diagram to show relationship between entities. The main advantage for this method is thorough understanding of data flow and relationship between entities. The reason for choosing this methodology is to draw less and efficient diagrams for better implementation. The DFD and ER-Diagram is shown in the next section.

Page 23

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

6.2 DATA FLOW DIAGRAMS

Page 24

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

Page 25

SVIT/COMP/2011-12/21 DFD LEVEL -2 OF PAYROLL SYSTEM

ERP FOR MANUFACTURING SYSTEM

Page 26

SVIT/COMP/2011-12/21 LEVEL -2 OF INVENTORY SYSTEM

ERP FOR MANUFACTURING SYSTEM

Page 27

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

6.3 DATABASE DESIGN

6.3.1 E-R DIAGRAM

Page 28

SVIT/COMP/2011-12/21 6.3.2: DATA DICITONARY

ERP FOR MANUFACTURING SYSTEM

The data dictionary can be defined as an organized collection of all the data elements of the system with precise and rigorous definitions so that user and system analyst will have a common understanding of inputs, outputs, components of stores and intermediate calculations. The data models are less detail hence there is need of data dictionary. Data dictionaries are list of all of the names used in the system. Descriptions of the entities, relationships and attributes are also included in data dictionary. The data dictionary stores following type of information: 1. Table Name : Employee_Master Primary Key : EmpId Description : Contains details of Employee.

Serial No. 1

Field Name EmpId

Data Type Int

Constraints Primary key

Description Identification of Employee Name employee Address employee Gender employee Mobile no employee of

Name

nvarchar(15)

Not Null

Address

nvarchar(100)

Not Null

of

Gender

nvarchar(7)

Not Null

of

Mobileno

Int

Not Null

of

Page 29

SVIT/COMP/2011-12/21 2. Table Name: Client_Master Primary Key : ClientId Foreign Key : City Id Description : Contains details of Client.

ERP FOR MANUFACTURING SYSTEM

Serial No. 1

Field Name ClientId

Data Type Int

Constraints Primary key

Description Identification of client Name of client City of client Mobile client Office client Email client no of

2 3 4

ClientName CityId MobileNo

Nvarchar(50) Nvarchar(100) Text

Not Null Not Null Foreign Key

Office No

Int

Not Null

no.

of

Email Id

nvarchar(25)

Not Null

Id

of

3.Table Name: Product Order Foreign Key: OrderRefID Description: Contains details of product Order Serial No. 1 Field Name OrderRefID Data Type Int Constraints Foreign Key Description Order Ref ID of product IdNo of product Description Product of

2 3

IdNo. Description

Int Nvarchar(50)

Not Null Not Null

Rate

Int

Not Null

Rate of product

Page 30

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

4.Table Name: Sales Order Primary Key: Name Foreign Key: ObjectRefId Description: Details of Sales Order

Serial No. 1

Field Name ObjectRefId

Data Type Int

Constraints Foreign Key

Description Reference id of product Rate of Product Name product Quantity product of

2 3

Rate Name

Int nvarchar(32)

Not Null Primary Key

Quantity

Int

Not null

of

5.Table Name : Admin Primary Key : AdminId Description : Administration Login Data. Serial No. 1 Field Name AdminId Data Type nvarchar(15) Constraints Primary Key Description Identification Admin no. of

Password

nvarchar(15)

Not Null

Password of Admin

Page 31

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

6. Table Name: Scheduling_Work Primary Key: ScheduleId Foreign Key: DefectID , WorkID

Description: Rescheduled Work Information Serial No. 1 Field Name DefectID Datatype int Constraints Foreign Key Description Identification Defect work no. of

2 3 4 5 6

WorkId WorkDesc. ScheduleID ScheduleDate WorkAllocID

Int nvarchar(200) Int Date Int

Foreign Key Not Null Primary Key Not Null Not Null

Identification no. of work Description of Work Rescheduled Work ID Rescheduled Date Rescheduled Identification no. Work

7. Table Name: Item_Price Description : Price of Items Serial No. 1 2 Field Name item_name sales_price Datatype nvarchar(15) nvarchar(5) Constraints Reference Reference Description Name of Items Sales price of items

Page 32

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

8. Table Name: Bill of Material Primary Key: Name Description: Stores BOM information Serial No. 1 2 3 Field Name Name Quantity unit_name Datatype nvarchar(15) nvarchar(3) nvarchar(5) Reference Constraints Primary Description

Page 33

SVIT/COMP/2011-12/21

ERP FOR MANUFACTURING SYSTEM

REFERENCES
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. The Flow of Information in an Accounting System, http://financial-education.com/2008/08/01/theflow-of-information-in-an-accounting-system ERP Implementation Life Cycle, http://www.open-source-erp-site.com/erp-implementation-lifecycle.html ERP modules , http://www.open-source-erp-site.com/erp-modules.html The Accounting Cycle , http://www.quickmba.com/accounting/fin/cycle Google Transliteration, http://www.google.co.in/transliterate/indic Busy Accounting Software, http://www.busy.in/index.php?p=features-ee Adding Multi-Language Support to Web Applications with PHP and PEAR, http://devzone.zend.com/article/4469 Internationalizing a GUI Form, http://netbeans.org/kb/docs/java/gui-automatic-i18n.html General observations about locales in .net and dotnetnuke, http://www.dotnetnuke.com/Resources/Forums/forumid/78/threadid/6926/scope/posts.aspx Localization in Indian(Gujarati Language), http://javabiz.wordpress.com/2010/05/12/workingwith-indiangujarati-language/ User experience, http://en.wikipedia.org/wiki/User_experience Why Localize?, http://www.gala-global.org/why-localize

Page 34