Background of the Study

The generations of today lived in a life million times easier compared to our associates. The undeniable evidence of modern technology could be seen everywhere. Nowadays, complex processing of tasks such as those done in payroll, inventory systems and decision-making in companies, industries and institution relied much on computers. As a result, they were able to cope up with the technological advancements. One area where the technological advancement could be employed was the tedious manual entry of every product in a typical warehouse.

Warehouse Management Systems (WMS) have been available since the earliest computer systems and were allowed simple storage location functionality. Today WMS systems can be standalone or part of an Enterprise Resource Planning (ERP) system and can include complex technology such as Radio Frequency Identification (RFID) and voice recognition. However the basic principle of the warehouse system has remained the same, which is to provide information to allow efficient control of the movement of materials within the warehouse.

The implementation of a WMS is often complex. Project planning is critical to the success of any WMS implementation. The project requires warehouse resources to collect data on the physical warehouse, materials, inventory as well as defining the strategies required to operate the warehouse. There is the added challenge of implementing the system whilst still operating the warehouse. A major factor of all projects is still ship product whilst the WMS is being implemented.

The complexity of a WMS implementation varies with every business. The physical dimensions and characteristics of each item in the warehouse are required to be collected and entered into the new system. Capacity calculations require the physical size and weight of the item as well as the dimensions of all the storage bins or racks in the warehouse. The storage options for each item are required, for example if the item can be stored separately, in box, pallet or if it can be stacked. Each item must be reviewed to see if it is physical limitations on its storage, such as requiring refrigeration. Hazardous material information needs to be collected so that the item is not stored in certain areas. This information is only part of the requirements of the WMS implementation.

. The system requires decisions or configuration to be made on how items are to be placed or removed from the system, in what order, for what types of materials and what methods of placement and removal should be used. The implementation requires significant input from the resources that operate the warehouse on a day to day basis and this can be a strain on warehouse operations. A successful project will recognize this fact and ensure that the key personnel required for the implementation are given adequate back up so that warehouse operations do not suffer.

After the successful launch of the WMS system, many businesses will find that the resources required to operate the system is greater than prior to the implementation. This is primarily due to the data intensive nature of the software and the fact that warehouses are in a state of flux; racks are moved, placement and removal strategies changed, new items added, new processes developed. Warehouse accuracy is paramount for the software to operate and to do this data will need to be entered accurately and in a timely fashion. Although most WMS implementations will reduce labor costs in the placement and removal of materials, there is often an added warehouse management function required just to operate the system software.

Not only will placement and removal cycle times be reduced, but inventory accuracy should be improved as well as increased system capacity, more organized storage of materials and greater flexibility of warehouse operations. Thus, the researchers proposed a system to change the existing system operation in the warehouse of Ginebra San Miguel Incorporated in order to minimize problems often encountered and to lessen the time spent in manual entry of products.

In the development of a warehouse management system, it was important to consider a process model as an approach for system development. The structure of system popularly known as RAD (Rapid Application Design) was the frame reference in the development of the proposed system. It was widely used in the design of systems that could easily be understood and has well - defined workflows.

In the development of a warehouse management system, it was important to consider a process model as an approach for system development. The structure of system popularly known as RAD (Rapid Application Design) was the frame reference in the development of the proposed system. It was widely used in the design of systems that could easily be understood and has well - defined workflows.

Rapid Application Development (RAD) is a term originally used to describe a software development process first developed and successfully deployed during the mid 1970s by the New York Telephone Co's Systems Development Center under the direction of Dan Gielan. Following a series of remarkably successful implementations of this process, Gielan lectured extensively in various forums on the methodology, practice, and benefits of this process.

Rapid application development was a response to processes developed in the 1970s and 1980s, such as the Structured Systems Analysis and Design Method and other Waterfall models. One problem with previous methodologies was that applications took so long to build that requirements had changed before the system was complete, resulting in inadequate or even unusable systems. Another problem was the assumption that a methodical requirements analysis phase alone would identify all the critical requirements. Ample evidence attests to the fact that this is seldom the case, even for projects with highly experienced professionals at all levels. Starting with the ideas of Brian Gallagher, Alex Balchin, Barry Boehm and Scott Shultz, James Martin developed the rapid application development approach during the 1980s at IBM and finally formalized it by publishing a book in 1991, Rapid Application Development.

Requirements Planning phase combines elements of the system planning and systems analysis phases of the System Development Life Cycle (SDLC). Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. It ends when the team agrees on the key issues and obtains management authorization to continue.

User design phase during this phase, users interact with systems analysts and develop models and prototypes that represent all system processes, inputs, and outputs. The RAD groups or subgroups typically use a combination of Joint Application Development (JAD) techniques and CASE tools to translate user needs into working models. User Design is a continuous interactive process that allows users to understand, modify, and eventually approve a working model of the system that meets their needs.

Construction phase focuses on program and application development task similar to the SDLC. In RAD, however, users continue to participate and can still suggest changes or improvements as actual screens or reports are developed. Its tasks are programming and application development, coding, unitintegration and system testing.

Cutover phase resembles the final tasks in the SDLC implementation phase, including data conversion, testing, changeover to the new system, and user training. Compared with traditional methods, the entire process is compressed. As a result, the new system is built, delivered, and placed in operation much sooner. Its tasks are data conversion, fullscale testing, system changeover, user training.

Weather Forecasting System for NASA

This system connects to the NASA satellites and

collects various weather related information throughout the day and after analysis of that data NASA computers generates the various kind of weather information for the next 24 hours like Temperature, Humidity, Wind Speed, Pressure. Nowadays because of the US government open knowledge policy the other organizations has started demanding these information from NASA weather system. Currently NASA has no system in place that can be used by any system in the world to download the information for NASA weather systems computers and use it. NASA is planning to develop a API that can be used by any external client to download the information from the NASA systems.

Bonus System for Mercedes Benz customers

The bonus system is a way for a Mercedes owner

that also owns a Smart Card to receive benefits for using Mercedes dealers for their service needs. Whenever maintenance is performed on the owner's Mercedes, they will earn a certain number of bonus points based on the type of service. These bonus points can be redeemed for other services or products.

General Objective:
This study aimed to develop a Warehouse

Management System of Ginebra San Miguel Corporation. The existing system was observed to be time consuming in processing data entry of every goods and products due to its manual operations.

Specific Objectives:
To develop an effective and efficient procedure

involved in the recording, retrieving and sorting of goods and products in warehouse management system of Ginebra San Miguel, Corporation. To minimize the problems encountered by personnel and clients in relation to the existing system. To simplify the process of the current systems by making it more systematic and organized that would be of tremendous help in the future use.

The personnel In- charge, as it was not be too tedious and laborious but instead it lessen the time and effort to record, retrieve and sort data of every goods and products and hence could perform to do other tasks and responsibilities inside the corporation. The Client, as it served as the target market of a particular firm it would be of great help in the sake of the clients because it lessens the time they would have to spend in waiting for the goods and products that theyve ordered.

The personnel In- charge, as it was not be too tedious and laborious but instead it lessen the time and effort to record, retrieve and sort data of every goods and products and hence could perform to do other tasks and responsibilities inside the corporation. The Client, as it served as the target market of a particular firm it would be of great help in the sake of the clients because it lessens the time they would have to spend in waiting for the goods and products that theyve ordered.

The Management, as it helped them tremendously in managing every goods and products of the corporation providing them the ease of access in every goods and product that they wish to check if any problem occurs and check if there is any evaluation conducted.
The Other Researchers, as it helped them understand further the processed involved in warehouse management system. This study also used as reference by other researchers who were into developing warehouse management system in managing goods and products in a corporation.

The system will be limited to the following services:

Management of Warehouse Inventory Addition, Updating, and Removal of Product

Information Addition, Updating, and Removal of Warehouse Personnel Information who will be using the system. Addition, Updating, and Removal of Distributor Information Generate Reports Stock Transfer Report Inventory Reports Transactions Report Warehouse Incident Report

Data analysis is a process in which raw data are ordered and organized so that useful information can be extracted from it. It is a process of organizing and thinking about data is a key to enhanced understanding what the data does and does not contain. Likewise, it is also a process of evaluating data using analytical and logical reasoning to examine each component of the data provided. An entityrelationship diagram is a data modeling technique that creates a graphical representation of the entities, and the relationships between entities within an information system. A graphical procedure used to describe an information system which shows the logical associations among system entities.

INPUT

PROCESS

OUTPUT

Warehouse Data Report Formats User Privileges Report Generation Policies

RAPID APPLICATION DEVELOPMENT

WAREHOUSE MANAGEMENT SYSTEM

WAREHOUSE MANAGEMENT SYSTEM USE CASE

Maintain Product Information

* Update Inventory
*

*
Create Reports * * **

* Employee Record Warehouse Transactions

Administrator *

Maintain Distributor Information