WELCOME

PROJECT REPORT ON INVENTORY MANAGEMENT SYSTEM (IMS) UNDERGONE AT

RELIANCE INFRASTRUCTURE LTD.

(FORMERLY RELIANCE ENERGY)

COMPANY PROFILE
Engaged in the generation, transmission and distribution of electricity. Leading player in India in the EPC segment of the power sector. Thermal, hydro, Co-generation and gas based power generating stations. Renovation and Modernization of Delhi distribution network and other civil works.

What Is An Inventory?
Inventory is a list for goods and materials, or those goods and materials themselves, held available in stock by a business. Inventory are held in order to manage and hide from the customer the fact that manufacture/supply delay is longer than delivery delay, and also to ease the effect of imperfections in the manufacturing process that lower production efficiencies if production capacity stands idle for lack of materials.

Reasons For Keeping an Inventory:

Time : to keep a track of time lags present in the supply chain, from supplier to user at every stage Uncertainty : to meet uncertainties in demand, supply and movements of goods. Economies of Scale : one unit at a time at a place where user needs it, when he needs it" principle tends to incur lots of costs in terms of logistics.

What is an Inventory Management System?

Provides information to efficiently manage the flow of materials, effectively utilize people and equipment, coordinate internal activities, and communicate with customers It provides the information to managers who make more accurate and timely decisions to manage their operations.

System Analysis
Identify the customer s need. Evaluate the system concept for feasibility. Perform economic and technical analysis. Allocate functions to hardware, software people, database and other system elements. Establish cost and schedule constraints. Create a system definition that forms the foundation for all the subsequent engineering work.

PERFORMANCE REQUIREMENTS
User Friendliness User Satisfaction Response Time Error Handling Safety Robustness

ACCEPTANCE CRITERIA
The project will be acceptable in case it fulfills the following criteria : User Friendliness Modularity Maintainability Timeliness Accurate Scope to foresee modifications

FEASIBILITY STUDY
Each project has to be measured in terms of resources and time taken. Thus the feasibility of the project has to be measured as a result of which we have made use of the concept of reusability.

Contd..
There are three basic types of feasibility study : Economic Feasibility Technical Feasibility Behavioral Feasibility

ECONOMIC FEASIBILITY
Used for evaluating the effectiveness of the candidate system. It considers the cost to conduct a full system investigation. The cost of hardware and software for the application. The benefits in form of reduced costs.

TECHNICAL FEASIBILITY
It takes care of the current system hardware and software. If additional hardware required then it also considers the financial considerations. It also considers that the tools, OS and other softwares used are compatible with the existing one.

BEHAVIORAL FEASIBILITY
It measures as to how strong a reaction would be towards the development of the computerized system. New system requires efforts to train and educate new staff. It sees thet the software developed is user friendly and easy to learn.

SOFTWARE REQUIREMENT SPECIFICATION

A Software Requirements Specification (SRS) is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. Use cases are also known as functional requirements.

HARDWARE REQUIRED
Celeron Processor 512MB RAM or more 2.5GB of free Hard Disk

SOFTWARE REQUIRED
Windows Operating System (doesn't run on other OS like Mac, Linux, Solaris etc.) Oracle 9i(this acts as the back end for the software) Microsoft Visual Basic 6.0(not needed if directly run from the .exe file and it also acts the front end)

PROJECT DESIGN

DESIGN GOALS
Should be user-friendly: This was necessary so that project could be used efficiently and it could act as catalyst in achieving objectives. Compatibility: It should fit in the total integrated system. Future maintenance and enhancement must be less. It should integrate other modules of system into itself. Should be reliable, understandable and costeffective.

Entity-Relationship(ER) Diagram

OVERVIEW OF IMS
An IMS requires the following entities : Product Stores Vendor Bill Storage Purchase Order Users

RELATION B/W ENTITIES

Each Product has a Product ID, which is an associative entity supporting a relation between Product and the vendor of the item. A bill will come into place when an order is placed and the quantities received, thus the Vendor ID will be an associative entity supporting the relation between them.

Contd
A Bill includes one or more products, each of which corresponds to an Inventory Item. Obviously, a product cannot exist without an associated bill, and overtime there will be zero-to-many receipts for a product.

FLOWCHARTS USED

1.How to place an order with the vendor?

2.Order Received

3.Generation of bill of the order received

4.Add received quantity to store

5.Delete product from store

PROBLEMS FACED
Handling null values Parent key is violated while deleting child records Handling blank passwords Case sensitivity of oracle Date manipulation

SCREEN SHOTS

Start of IMS

User Authentication

Main Screen

Place an order

Add a Product

Product is Received

Manage Stores

Bill Entry

Delete an order

Manage Bills

Product Details

Store Details

Products

Product Search

Vendor

Generating Reports

User Accounts

Quitting Project

CONCLUSION
IMS meets all the proposed requirements. It automates the whole procedure, thus reducing the workload. Security was also kept in mind as it was one of the primary concerns. IMS made in from different modules thus enabling the scope for future modifications.

Questions ?