Free Essay

Warehousing System

In: Business and Management

Submitted By akhyar
Words 4159
Pages 17
Warehouse Management Systems (WMS).
By Dave Piasecki
© Copyright. Content on InventoryOps.com is copyright-protected and is not available for republication.
The evolution of warehouse management systems (WMS) is very similar to that of many other software solutions. Initially a system to control movement and storage of materials within a warehouse, the role of WMS is expanding to including light manufacturing, transportation management, order management, and complete accounting systems. To use the grandfather of operations-related software, MRP, as a comparison, material requirements planning (MRP) started as a system for planning raw material requirements in a manufacturing environment. Soon MRP evolved into manufacturing resource planning (MRPII), which took the basic MRP system and added scheduling and capacity planning logic. Eventually MRPII evolved into enterprise resource planning (ERP), incorporating all the MRPII functionality with full financials and customer and vendor management functionality. Now, whether WMS evolving into a warehouse-focused ERP system is a good thing or not is up to debate. What is clear is that the expansion of the overlap in functionality between Warehouse Management Systems, Enterprise Resource Planning, Distribution Requirements Planning, Transportation Management Systems, Supply Chain Planning, Advanced Planning and Scheduling, and Manufacturing Execution Systems will only increase the level of confusion among companies looking for software solutions for their operations.
Even though WMS continues to gain added functionality, the initial core functionality of a WMS has not really changed. The primary purpose of a WMS is to control the movement and storage of materials within an operation and process the associated transactions. Directed picking, directed replenishment, and directed putaway are the key to WMS. The detailed setup and processing within a WMS can vary significantly from one software vendor to another, however the basic logic will use a combination of item, location, quantity, unit of measure, and order information to determine where to stock, where to pick, and in what sequence to perform these operations.
At a bare minimum, a WMS should: * Have a flexible location system. * Utilize user-defined parameters to direct warehouse tasks and use live documents to execute these tasks. * Have some built-in level of integration with data collection devices.
Do You Really Need WMS?
Not every warehouse needs a WMS. Certainly any warehouse could benefit from some of the functionality but is the benefit great enough to justify the initial and ongoing costs associated with WMS? Warehouse Management Systems are big, complex, data intensive, applications. They tend to require a lot of initial setup, a lot of system resources to run, and a lot of ongoing data management to continue to run. That’s right, you need to "manage" your warehouse "management" system. Often times, large operations will end up creating a new IS department with the sole responsibility of managing the WMS.
The Claims: * WMS will reduce inventory! * WMS will reduce labor costs! * WMS will increase storage capacity! * WMS will increase customer service! * WMS will increase inventory accuracy!
The Reality:
The implementation of a WMS along with automated data collection will likely give you increases in accuracy, reduction in labor costs (provided the labor required to maintain the system is less than the labor saved on the warehouse floor), and a greater ability to service the customer by reducing cycle times. Expectations of inventory reduction and increased storage capacity are less likely. While increased accuracy and efficiencies in the receiving process may reduce the level of safety stock required, the impact of this reduction will likely be negligible in comparison to overall inventory levels.The predominant factors that control inventory levels are lot sizing, lead times, and demand variability. It is unlikely that a WMS will have a significant impact on any of these factors. And while a WMS certainly provides the tools for more organized storage which may result in increased storage capacity, this improvement will be relative to just how sloppy your pre-WMS processes were.
Beyond labor efficiencies, the determining factors in deciding to implement a WMS tend to be more often associated with the need to do something to service your customers that your current system does not support (or does not support well) such as first-in-first-out, cross-docking, automated pick replenishment, wave picking, lot tracking, yard management, automated data collection, automated material handling equipment, etc.
WMS Setup
The setup requirements of WMS can be extensive. The characteristics of each item and location must be maintained either at the detail level or by grouping similar items and locations into categories. An example of item characteristics at the detail level would include exact dimensions and weight of each item in each unit of measure the item is stocked (eaches, cases, pallets, etc) as well as information such as whether it can be mixed with other items in a location, whether it is rackable, max stack height, max quantity per location, hazard classifications, finished goods or raw material, fast versus slow mover, etc. Although some operations will need to set up each item this way, most operations will benefit by creating groups of similar products. For example, if you are a distributor of music CDs you would create groups for single CDs, and double CDs, maintaining the detailed dimension and weight information at the group level and only needing to attach the group code to each item. You would likely need to maintain detailed information on special items such as boxed sets or CDs in special packaging. You would also create groups for the different types of locations within your warehouse. An example would be to create three different groups (P1, P2, P3) for the three different sized forward picking locations you use for your CD picking. You then set up the quantity of single CDs that will fit in a P1, P2, and P3 location, quantity of double CDs that fit in a P1, P2, P3 location etc. You would likely also be setting up case quantities, and pallet quantities of each CD group and quantities of cases and pallets per each reserve storage location group.
If this sounds simple, it is…well… sort of. In reality most operations have a much more diverse product mix and will require much more system setup. And setting up the physical characteristics of the product and locations is only part of the picture. You have set up enough so that the system knows where a product can fit and how many will fit in that location. You now need to set up the information needed to let the system decide exactly which location to pick from, replenish from/to, and putaway to, and in what sequence these events should occur (remember WMS is all about “directed” movement). You do this by assigning specific logic to the various combinations of item/order/quantity/location information that will occur.
Below I have listed some of the logic used in determining actual locations and sequences. * Location Sequence. This is the simplest logic; you simply define a flow through your warehouse and assign a sequence number to each location. In order picking this is used to sequence your picks to flow through the warehouse, in putaway the logic would look for the first location in the sequence in which the product would fit. * Zone Logic. By breaking down your storage locations into zones you can direct picking, putaway, or replenishment to or from specific areas of your warehouse. Since zone logic only designates an area, you will need to combine this with some other type of logic to determine exact location within the zone. * Fixed Location. Logic uses predetermined fixed locations per item in picking, putaway, and replenishment. Fixed locations are most often used as the primary picking location in piece pick and case-pick operations, however, they can also be used for secondary storage. * Random Location. Since computers cannot be truly random (nor would you want them to be) the term random location is a little misleading. Random locations generally refer to areas where products are not stored in designated fixed locations. Like zone logic, you will need some additional logic to determine exact locations. * First-in-first-out (FIFO). Directs picking from the oldest inventory first. * Last-in-first-out (LIFO). Opposite of FIFO. I didn't think there were any real applications for this logic until a visitor to my site sent an email describing their operation that distributes perishable goods domestically and overseas. They use LIFO for their overseas customers (because of longer in-transit times) and FIFO for their domestic customers. * Quantity or Unit-of-measure. Allows you to direct picking from different locations of the same item based upon the quantity or unit-of-measured ordered. For example, pick quantities less than 25 units would pick directly from the primary picking location while quantities greater than 25 would pick from reserve storage locations. * Fewest Locations. This logic is used primarily for productivity. Pick-from-fewest logic will use quantity information to determine least number of locations needed to pick the entire pick quantity. Put-to-fewest logic will attempt to direct putaway to the fewest number of locations needed to stock the entire quantity. While this logic sounds great from a productivity standpoint, it generally results in very poor space utilization. The pick-from-fewest logic will leave small quantities of an item scattered all over your warehouse, and the put-to-fewest logic will ignore small and partially used locations. * Pick-to-clear. Logic directs picking to the locations with the smallest quantities on hand. This logic is great for space utilization. * Reserved Locations. This is used when you want to predetermine specific locations to putaway to or pick from. An application for reserved locations would be cross-docking, where you may specify certain quantities of an inbound shipment be moved to specific outbound staging locations or directly to an awaiting outbound trailer. * Nearest Location. Also called proximity picking/putaway, this logic looks to the closest available location to that of the previous putaway or pick. You need to look at the setup and test this type of logic to verify that it is picking the shortest route and not the actual nearest location. Since the shortest distance between two points is a straight line, this logic may pick a location 30 feet away (thinking it’s closest) that requires the worker to travel 200 feet up and down aisles to get to it while there was another available location 50 feet away in the same aisle (50 is longer than 30). * Maximize Cube. Cube logic is found in most WMS systems however it is seldom used. Cube logic basically uses unit dimensions to calculate cube (cubic inches per unit) and then compares this to the cube capacity of the location to determine how much will fit. Now if the units are capable of being stacked into the location in a manner that fills every cubic inch of space in the location, cube logic will work. Since this rarely happens in the real world, cube logic tends to be impractical. * Consolidate. Looks to see if there is already a location with the same product stored in it with available capacity. May also create additional moves to consolidate like product stored in multiple locations. * Lot Sequence. Used for picking or replenishment, this will use the lot number or lot date to determine locations to pick from or replenish from.
It’s very common to combine multiple logic methods to determine the best location. For example you may chose to use pick-to-clear logic within first-in-first-out logic when there are multiple locations with the same receipt date. You also may change the logic based upon current workload. During busy periods you may chose logic that optimizes productivity while during slower periods you switch to logic that optimizes space utilization.
© Copyright. Content on InventoryOps.com is copyright-protected and is not available for republication.
Other Functionality/Considerations
Wave Picking/Batch Picking/Zone Picking.
Support for various picking methods varies from one system to another. In high-volume fulfillment operations, picking logic can be a critical factor in WMS selection. See my article on Order Picking for more info on these methods.
Task Interleaving.
Task interleaving describes functionality that mixes dissimilar tasks such as picking and putaway to obtain maximum productivity. Used primarily in full-pallet-load operations, task interleaving will direct a lift truck operator to put away a pallet on his/her way to the next pick. In large warehouses this can greatly reduce travel time, not only increasing productivity, but also reducing wear on the lift trucks and saving on energy costs by reducing lift truck fuel consumption. Task interleaving is also used with cycle counting programs to coordinate a cycle count with a picking or putaway task.
Automated Data Collection (ADC).
It is generally assumed when you implement WMS that you will also be implementing automatic data collection, usually in the form of radio-frequency (RF) portable terminals with bar code scanners. I recommend incorporating your ADC hardware selection and your software selection into a single process. This is especially true if you are planning on incorporating alternate technologies such as voice systems, RFID, or light-directed systems. You may find that a higher priced WMS package will actually be less expensive in the end since it has a greater level of support for the types of ADC hardware you will be using. In researching WMS packages you may see references like “supports”, “easily integrates with”, “works with”, “seamlessly interfaces with” in describing the software’s functionality related to ADC. Since these statements can mean just about anything, you’ll find it important to ask specific questions related to exactly how the WMS system has been programmed to accommodate ADC equipment. Some WMS products have created specific versions of programs designed to interface with specific ADC devices from specific manufacturers. If this WMS/ADC device combination works for your operation you can save yourself some programming/setup time. If the WMS system does not have this specific functionality, it does not mean that you should not buy the system, it just means that you will have to do some programming either on the WMS system or on the ADC devices. Since programming costs can easily put you over budget you’ll want to have an estimate of these costs up front. As long as you are working closely with the WMS vendor and the ADC hardware supplier at an early stage in the process you should be able to avoid any major surprises here. Read my article on ADC.
Integration with Automated Material Handling Equipment.
If you are planning on using automated material handling equipment such as carousels, ASRS units, AGVs, pick-to-light systems, or sortation systems, you’ll want to consider this during the software selection process. Since these types of automation are very expensive and are usually a core component of your warehouse, you may find that the equipment will drive the selection of the WMS. As with automated data collection, you should be working closely with the equipment manufacturers during the software selection process.
Advanced Shipment Notifications (ASN).
If your vendors are capable of sending advanced shipment notifications (preferably electronically) and attaching compliance labels to the shipments you will want to make sure that the WMS can use this to automate your receiving process. In addition, if you have requirements to provide ASNs for customers, you will also want to verify this functionality.
Cycle Counting.
Most WMS will have some cycle counting functionality. Modifications to cycle counting systems are common to meet specific operational needs. Read my article on Cycle Counting and check out my book on Inventory Accuracy and Cycle Counting.
Cross Docking.
In its purest form cross-docking is the action of unloading materials from an incoming trailer or rail car and immediately loading these materials in outbound trailers or rail cars thus eliminating the need for warehousing (storage). In reality pure cross-docking is less common; most "cross-docking" operations require large staging areas where inbound materials are sorted, consolidated, and stored until the outbound shipment is complete and ready to ship. If cross docking is part of your operation you will need to verify the logic the WMS uses to facilitate this.
Pick-to-Carton.
For parcel shippers pick-to-carton logic uses item dimensions/weights to select the shipping carton prior to the order picking process. Items are then picked directly into the shipping carton. When picking is complete, dunnage is added and the carton sealed eliminating a formal packing operation. This logic works best when picking/packing products with similar size/weight characteristics. In operations with a very diverse product mix it's much more difficult to get this type of logic to work effectively.
Slotting.
Slotting describes the activities associated with optimizing product placement in pick locations in a warehouse. There are software packages designed just for slotting, and many WMS packages will also have slotting functionality. Slotting software will generally use item velocity (times picked), cube usage, and minimum pick face dimensions to determine best location. Read my article on Slotting.
Yard Management.
Yard management describes the function of managing the contents (inventory) of trailers parked outside the warehouse, or the empty trailers themselves. Yard management is generally associated with cross docking operations and may include the management of both inbound and outbound trailers.
Labor Tracking/Capacity Planning.
Some WMS systems provide functionality related to labor reporting and capacity planning. Anyone that has worked in manufacturing should be familiar with this type of logic. Basically, you set up standard labor hours and machine (usually lift trucks) hours per task and set the available labor and machine hours per shift. The WMS system will use this info to determine capacity and load. Manufacturing has been using capacity planning for decades with mixed results. The need to factor in efficiency and utilization to determine rated capacity is an example of the shortcomings of this process. Not that I’m necessarily against capacity planning in warehousing, I just think most operations don’t really need it and can avoid the disappointment of trying to make it work. I am, however, a big advocate of labor tracking for individual productivity measurement. Most WMS maintain enough data to create productivity reporting. Since productivity is measured differently from one operation to another you can assume you will have to do some minor modifications here (usually in the form of custom reporting).
Activity-based costing/billing.
This functionality is primarily designed for third-party logistics operators. Activity-based billing allows them to calculate billable fees based upon specific activities. For example, a 3PL can assign transaction fees for each receipt, and shipment transaction, as well as fees for storage and other value-added activities.
Integration with existing accounting/ERP systems.
Unless the WMS vendor has already created a specific interface with your accounting/ERP system (such as those provided by an approved business partner) you can expect to spend some significant programming dollars here. While we are all hoping that integration issues will be magically resolved someday by a standardized interface, we ain’t there yet. Ideally you’ll want an integrator that has already integrated the WMS you chose with the business software you are using. Since this is not always possible you at least want an integrator that is very familiar with one of the systems.
WMS + everything else = ?
As I mentioned at the beginning of this article, a lot of other modules are being added to WMS packages. These would include full financials, light manufacturing, transportation management, purchasing, and sales order management. I don’t see this as a unilateral move of WMS from an add-on module to a core system, but rather an optional approach that has applications in specific industries such as 3PLs. Using ERP systems as a point of reference, it is unlikely that this add-on functionality will match the functionality of best-of-breed applications available separately. If warehousing/distribution is your core business function and you don’t want to have to deal with the integration issues of incorporating separate financials, order processing, etc. you may find these WMS based business systems are a good fit.
Implementation Tips
Outside of the standard “don’t underestimate”, “thoroughly test”, “train, train, train” implementation tips that apply to any business software installation (read my article Software Selection and Implementation Tips) it’s important to emphasize that WMSs are very data dependent and restrictive by design. That is, you need to have all of the various data elements in place for the system to function properly. And, when they are in place, you must operate within the set parameters.
A warehouse is a commercial building for storage of goods. Warehouses are used by manufacturers, importers, exporters, wholesalers, transport businesses, customs, etc. They are usually large plain buildings in industrial areas of cities and towns and villages. They usually have loading docks to load and unload goods from trucks. Sometimes warehouses are designed for the loading and unloading of goods directly from railways, airports, or seaports. They often have cranes and forklifts for moving goods, which are usually placed on ISO standard pallets loaded into pallet racks. Stored goods can include any raw materials, packing materials, spare parts, components, or finished goods associated with agriculture, manufacturing, or commerce. Wikipedia.com
Warehouse management system
From Wikipedia, the free encyclopedia
Jump to: navigation, search | This article has multiple issues. Please help improve it or discuss these issues on the talk page. This article does not cite any references or sources. (February 2012) | This article's tone or style may not reflect the encyclopedic tone used on Wikipedia. (April 2012) | This article may contain too much repetition or redundant language. (April 2012) | |
A warehouse management system, or WMS, is a key part of the supply chain and primarily aims to control the movement and storage of materials within a warehouse and process the associated transactions, including shipping, receiving, putaway and picking. The systems also direct and optimize stock putaway based on real-time information about the status of bin utilization.
Warehouse management systems often utilize .....Auto ID Data Capture (AIDC) technology, such as barcode scanners, mobile computers, wireless LANs and potentially Radio-frequency identification (RFID) to efficiently monitor the flow of products. Once data has been collected, there is either a batch synchronization with, or a real-time wireless transmission to a central database. The database can then provide useful reports about the status of goods in the warehouse.
The objective of a warehouse management system is to provide a set of computerized procedures to handle the receipt of stock and returns into a warehouse facility, model and manage the logical representation of the physical storage facilities (e.g. racking etc.), manage the stock within the facility and enable a seamless link to order processing and logistics management in order to pick, pack and ship product out of the facility.
Warehouse management systems can be stand alone systems, or modules of an ERP system or supply chain execution suite.
The primary purpose of a WMS is to control the movement and storage of materials within a warehouse – you might even describe it as the legs at the end-of-the line which automates the store, traffic and shipping management.
In its simplest form, the WMS can data track products during the production process and act as an interpreter and message buffer between existing ERP and WMS systems. Warehouse Management is not just managing within the boundaries of a warehouse today, it is much wider and goes beyond the physical boundaries. Inventory management,inventory planning, cost management, IT applications & communication technology to be used are all related to warehouse management. The container storage, loading and unloading are also covered by warehouse management today.Warehouse management today is part of SCM and demand management. Even production management is to a great extent dependent on warehouse management. Efficient warehouse management gives a cutting edge to a retail chain distribution company. Warehouse management does not just start with receipt of material but it actually starts with actual initial planning when container design is made for a product. Warehouse design and process design within the warehouse (e.g. Wave Picking) is also part of warehouse management. Warehouse management is part of Logistics and SCM.
Warehouse Management monitors the progress of products through the warehouse. It involves the physical warehouse infrastructure, tracking systems, and communication between product stations.
Warehouse management deals with receipt, storage and movement of goods, normally finished goods, to intermediate storage locations or to final customer. In the multi-echelon model for distribution, there are levels of warehouses, starting with the Central Warehouse(s), regional warehouses serviced by the central warehouses and retail warehouses serviced by the regional warehouses and so on. The objective of warehouse management is to help in optimal cost of timely order fulfillment by managing the resources economically. Warehouse management = "Management of storage of products and services rendered on the products within the four walls of a warehouse"

Similar Documents

Premium Essay

Warehousing in Logistics System

...Warehousing in logistics system Name Institution The role of warehousing in logistics system A warehouse is the building for storing goods while warehousing refers to the place or building where goods are stored. Warehousing plays the role of consolidation in the logistics system. Consolidation is the process of reducing the costs of transportation by consolidating the movement (Ross, 2004). Most of the companies supply their client with the same goods through a warehouse. From the warehouse; commodities are sent in a bulk shipment to the consumer. Therefore, rather than transporting the products in small shipment, it is economical having a consolidation warehouse. Safety stocking is another role of warehousing. In meeting different contingencies like stock outs or delays in the transportation, safety stocks should be maintained (Voortman, 2004). Safety stocking ensures that the inbound site of production does not arise, and the needs and requirements of the consumers are fulfilled in time as planned. Docking also enables the issue of full shipment from different suppliers like manufacturer and the process of distributing directly to the consumer without storage in the warehouse (Ross, 2004). After receiving the shipment, the products are located to the respective clients and moved to the vehicle for onward delivery to relevant consumers. Product mixing role enables the company...

Words: 1240 - Pages: 5

Free Essay

Warehousing Management System

...Warehouse Management Systems (WMS) The evolution of warehouse management systems (WMS) is very similar to that of many other software solutions.  Initially a system to control movement and storage of materials within a warehouse, the role of WMS is expanding to including light manufacturing, transportation management, order management, and complete accounting systems.  To use the grandfather of operations-related software, MRP, as a comparison, material requirements planning (MRP) started as a system for planning raw material requirements in a manufacturing environment.  Soon MRP evolved into manufacturing resource planning (MRPII), which took the basic MRP system and added scheduling and capacity planning logic. Eventually MRPII evolved into enterprise resource planning (ERP), incorporating all the MRPII functionality with full financials and customer and vendor management functionality.  Now, whether WMS evolving into a warehouse-focused ERP system is a good thing or not is up to debate.  What is clear is that the expansion of the overlap in functionality between Warehouse Management Systems, Enterprise Resource Planning, Distribution Requirements Planning, Transportation Management Systems, Supply Chain Planning, Advanced Planning and Scheduling, and Manufacturing Execution Systems will only increase the level of confusion among companies looking for software solutions for their operations. Even though WMS continues to gain added functionality, the initial core functionality...

Words: 3743 - Pages: 15

Free Essay

Teradata Introduction

...Coffing Data Warehousing Education Outline 02/17/05 TERADATA EDUCATION OUTLINE Coffing Data Warehousing has provided quality Teradata education, products and services for over a decade. We offer customized solutions to maximize your warehouse. Toll Free: 1-877-TERADAT Business Phone: 1-937-855-4838 Email: mailto:CDWSales@CoffingDW.com Website: http://www.CoffingDW.com In addition to the course material listed in this outline, we also offer Teradata classes in Teradata Basics, Implementation, SQL, Database Administration, Design and Utilities. Please contact us so we can customize a course to fit your specific needs. © 2006 Coffing Data Warehousing – All rights reserved. Confidential. 1 Coffing Data Warehousing Education Outline 02/17/05 PURPOSE Coffing Data Warehousing has been providing quality Teradata education for over a decade. We offer customized courses to maximize the effectiveness of each class. The purpose of this proposal is to build a lasting relationship with your company. To this end, we have combined our comprehensive Teradata education services in a unique package that we feel best suits the diverse needs of your company while offering our high quality product at competitive pricing. Coffing Data Warehousing is excited to offer you, our preferred partner, an innovative new way to look at training at the CoffingDW Teradata University (CDW-TU). This approach provides the ability to maximize learning potential. Our goal is to make your employees...

Words: 1512 - Pages: 7

Premium Essay

System Analyst

...Data Warehouse Design: Dimensional Modeling II Data Technology Chularat Tanprasert, Ph.D. Recap  Dimensional modeling      Popular, useful, and pragmatic approach Based on Kimball Fact table Dimension tables Design process in steps Database Schema Design Star Schema (With Attributes) Example Designs     A useful way to learn about data warehouse design principles is by using examples – reuse. Kimball – Data warehouse lifecycle toolkit Adamson & Venerable – Data warehouse design solutions Let’s take a look at inventory, shipments, and financial services. Inventory   An inventory system serves as a “middleman” between the manufacturer and the retailer – value adding process. There are threee types of inventory model    Inventory snapshot Delivery status Transaction Inventory Snapshot Model For specific time periods, inventory levels are measured and recorded. Delivery Status Model Create one record for each complete shipment of a product to a warehouse. Transaction Model Record every transaction that affects the inventory. Shipments    The shipments process is where the product leaves a company and is delivered to a customer. Typically, accompanying each shipment is a shipment invoice. Each line item on the shipment invoice corresponds to an SKU. Shipments Shipments Shipments Financial Services   Typically a large bank. Services...

Words: 1220 - Pages: 5

Premium Essay

Data Warehousing

...Data Warehouses The basic reasons organizations implement data warehouses are: To perform server/disk bound tasks associated with querying and reporting on servers/disks not used by transaction processing systems most firms want to set up transaction processing systems so there is a high probability that transactions will be completed in what is judged to be an acceptable amount of time. Reports and queries, which can require a much greater range of limited server/disk resources than transaction processing, run on the servers/disks used by transaction processing systems can lower the probability that transactions complete in an acceptable amount of time. Or, running queries and reports, with their variable resource requirements, on the servers/disks used by transaction processing systems can make it quite complex to manage servers/disks so there is a high enough probability that acceptable response time can be achieved. Firms therefore may find that the least expensive and/or most organizationally expeditious way to obtain high probability of acceptable transaction processing response time is to implement a data warehousing architecture that uses separate servers/disks for some querying and reporting. To use data models and/or server technologies that speed up querying and reporting and that are not appropriate for transaction processing There are ways of modeling data that usually speed up querying and reporting (e.g., a star schema) and may not be appropriate for transaction...

Words: 1160 - Pages: 5

Free Essay

Case Study: the Big Data Challenges

...Week 3 - The Big Data Challenges May 2014 Case Study: The Big Data Challenges Glendoria Early Strayer University CIS 500 – Information Systems for Decision Making Dr. Vince Osisek May 12, 2014 Case Study: The Big Data Challenges Week 3 - The Big Data Challenges Page 2 What if your car could talk? Well Volvo CIO's had to wonder the same thing as well. Volvo, a Swedish multinational manufacturing company, that not only produce cars, but light and heavy weight trucks as well as buses. Volvo Car Corporation has a history of using innovation to produce premium automobiles. The manufacture chose to rely on information technology to gain the innovative edge to help the company grow by integrating the cloud infrastructure into their networks. The Volvo Data Warehousing Program, started in 2006 (Data in the Driver's Seat), it draws insight from this multi-terabyte resource to create clear business advantage by integrating information from four primary sources: a system for managing vehicle and hardware specifications, one for managing on-board software specifications, the system that collects vehicle diagnostic data from service centers worldwide, and the warranty administration system. (Tobey, 2010) Joining all the various pieces of data together, Volvo can be warned about potential mechanical issues that may show up in the early part of a car's lifecycle. Volvo can spot patterns from the data that may indicate a potential flaw in a particular part well before a...

Words: 577 - Pages: 3

Free Essay

Ecommarce

...Objective To become Data warehousing Techno-Functional Consultant Current Role: Team member Synopsis of Experience: ➢ Over 2+ years of IT experience in Application Development, Testing of Data Warehousing Projects. ➢ Worked extensively on ETL tool (Informatica 9.1). ➢ Working knowledge on BI Tool (BOXI) ➢ Good exposure to data analysis, data extraction and data loading. ➢ Extensively worked on Oracle 10G. ➢ Strong understanding of Dimensional Modeling, Star and Snowflake Schemas. ➢ Having good inter-personal, analytical and communication skills. Work Experience: ➢ Have been working since Dec 2011 to Till Date as Developer in Vertiv solutions (INDIA) pvt ltd. Education: B.Tech from Jawaharlal Nehru Technological University Technical Skills: Operating System : MS-DOS, Window 7, UNIX Database : Oracle 9i, MS-SQL Server ETL Tool : Informatica Power Center 9.1 OLAP Tool : Business Objects Scheduler : Autosys Other Utilities : TOAD 8.0 Project Information: Project#1 Vertiv solutions (INDIA) pvt ltd. Client: Hewlett Packard, Houston USA Project: E-WARRANTY MANAGEMENT SYSTEM Duration: Dec 2011 – Mar 2013 Environment: Windows XP, UNIX, Informatica 7.1.2, Business Objects 6.5, Oracle9i, TOAD8.0, MS-SQL Server2000, MS-DTS About the Client: Hewlett Packard...

Words: 593 - Pages: 3

Premium Essay

Tools for Business

...inclusive of appendices Date: 2010-03-17 M.Sc. Thesis in Computer Engineering AV, 30 higher education credits Tools for Business Intelligence A comparison between Cognos 8 BI, Microsoft BI and SAP BW/NetWeaver Katarina Lundqvist Abstract 2010-03-17 Tools for Business Intelligence A comparison between Cognos 8 BI, Microsoft BI and SAP BW/NetWeaver Katarina Lundqvist Abstract The aim of the thesis was to conduct a general study of Business Intelligence and BI systems followed by a comparison of Cognos 8 BI, Microsoft BI and SAP BW/NetWeaver. The goal was to distinguish similarities and differences between the tools regarding technique, cost, usability and educational need and to provide a mapping for different customer situations. The method consisted of a theoretical study followed by a practical part including development, testing and interviews. The comparison showed that SAP and Microsoft both use the client/server model while Cognos is an integrated web-based system built on SOA. SQL Server can only be installed on Windows while BW and Cognos also support UNIX, Linux and IBM. SSRS report formats are HTML, PDF, CSV, XML, TIFF, Word and Excel. In BW, query results can be viewed as HTML, CSV and Excel. Cognos report formats are HTML, PDF, CSV, XML and Excel. The educational need for SQL Server and Cognos is low and may often be solved internally or through e-learning. In contrast, BW uses its own terminology and the enhanced star schema,...

Words: 25350 - Pages: 102

Premium Essay

Star Schem & Snowflake Schema

...Hello One and All, In my last Blog we discussed about Dimensional Modelling and some of its components. Today we will go through different Schema that can be used during Dimensional Modelling to create a Data Warehouse. Before we start with today's topic , For my viewers those who are new to this field i would like to revisit some of the key points of my previous blogs: 1) Business Intelligence is mainly divided into three parts as per my understanding a) Data Warehouse design and Implementation (ETL process) b) Data Analysis (Using OLAP cubes) c) Reporting and Dashboard Creation For further details revisit my First blog 2) Important Components involved in Dimensional Modelling or Data Warehouse Designing a) Fact Tables (Additive Facts, Semi-Additive Facts, Non- Additive Facts) b) Dimension Table c) Grain For further details revisit my Second blog After a thorough revision of previous concepts lets start our today's discussion about different Schema involved in Dimensional Modelling or Data Warehouse Designing. First of all i would like to explain the meaning of the topic i.e Snow Covered Wagon Hitched to a Star = SnowFlake Schema and Star Schema are two types of Schema that are used while designing a Data Warehouse, Hence they can be explained as follows: Star Schema: A Star Schema is one of the simplest and easiest schema to understand. A...

Words: 557 - Pages: 3

Premium Essay

Business Data Warehouse

...1. Define, and illustrate using a diagram, the following: Primary Data Warehouse and Data Mart. In this connection, explain the difference between ROLAP and MOLAP. A Primary Data Warehouse is a central repository of a database of a complete organization. It holds multiple subject areas and very detailed information. A Data Mart is a subset or an aggregation of the data stored to a primary data warehouse. It often holds only one subject area – for example, a specific department, finance or sales. It may hold more summaried data, and is typically smaller than a warehouse because of its employment on a different grain. Figure 1.1 illustrates the difference between data mart and a primary data warehouse. Since the data mart typically holds one subject area, it is much smaller than a primary data warehouse. These data marts can be viewed as small, local data warehouses replicating the part of primary data warehouse which is required by a specific domain or department. Data Warehouse Data Mart Data Warehouse Data Mart Figure 1.1 A data warehouse does not necessarily use a dimensional model, since it is partly normalized RDBMS, but data marts are multidimensional cubes. This connection gives arise to two concepts, ROLAP and MOLAP. ROLAP is an implementation based on a relational database, in our case which is a primary data warehouse, and MOLAP is an implementation based on a multidimensional database which are data marts. ROLAP tools use the relational database to access...

Words: 685 - Pages: 3

Premium Essay

Rarara

...in building data warehouses and data marts to obtain timely and actionable information that will give them better business insight. This will enable them to achieve, among other things, sustainable competitive advantage, increased revenues and a better bottom line. In the early '90s, data warehousing applications were either strategic or tactical in nature. Trending and detecting patterns was the typical focus of many solutions. Now, companies are implementing data warehouses or operational data stores which meet both strategic and operational needs. The business need for these solutions usually comes from the desire to make near real-time actions in a constantly changing environment while receiving information from both internal as well as external source systems. Dealing with missing or unknown data is critical in these types of environments. Unknowns skew metrics and results to produce incorrect decisions. Knowledge of the unknown allows at least for further examination of any conclusions drawn from incomplete data. Furthermore, in a well-designed business intelligence environment, these unknowns are often resolved later as data that is more complete is entered into the operational systems. Irrespective of the nature of the applications, missing information has always been a problem for data warehouses. As business intelligence environments become more mature, real time and mission critical, the increased number of operational applications accentuates this problem. It is important...

Words: 988 - Pages: 4

Premium Essay

Management Essay

...reason why I chose this company is because I have done internships in both COMPANY X and Sun Life Malaysia and through that I am equipped with firsthand knowledge about the company. COMPANY X is based in Kuala Lumpur, Malaysia and their primary business lies around Southeast Asia. It is considered a huge company with 1,080 branches across the region and over 40000 employees. The first problem that I see when I was working there is that there were too many paper works. They have been using data from periodic paper report, data from other regional office through papers and many other reports that were manually submitted through papers. Some of the employee’s full time job is to extract details from these papers and upload them to their system in the HQ. For an example, I was doing my internship in the procurement department, basically the purchases are all made through Oracle software and communication between us and the vendors are all done through that. The accounting departments have their own software where they work on Accounts Payable, Invoices and things like that. The way they integrate to data to match the amounts, units purchased between the purchasing department and the accounting department is all manual. Obviously this is inefficient because there is always time lag and human error which will cause mismatches in accounts and delay payments. The main reason why this is happening is because different departments use different software hence reports are generated in...

Words: 1522 - Pages: 7

Premium Essay

Data Warehouse

...• Provide a consistent information of various cross functional activity. Historical Data. Access, Analyze and Report Information. Augment the Business Processes Why is BI so Important Information Maturity Model Return on Information BI Solution for Everyone BI Framework Business Layer Business goals are met and business value is realized Administration & Operation Layer Business Intelligence and Data Warehousing programs are sustainable Implementation Layer Useful, reliable, and relevant data is used to deliver meaningful, actionable information BI Framework Business Requirements Data Sources Data Sources Data Acquisition, Cleansing,& Integration Data Acquisition, Cleansing, & Integration Data Stores Data Stores Information Services Information Delivery Information Delivery Business Analytics Business Analytics Business Applications Business Applications Business Value Business Value Development Data Resource Administration Data Resource Administration Data Warehousing BI & DW Operations Program Management BI Architecture ERP/BI Evolution Data Warehouse Standard Reports ROI Custom Reports Effort ERP Rollout Data Marts Views Excel Key Sites BI Focus Smaller Sites Time Customer Satisfaction BI Foundation Key Concepts: • Single source of the...

Words: 3637 - Pages: 15

Free Essay

Paper

...knowledge of Teradata as a Developer with proficiencies in Teradata SQL Assistant utilities like Fastload, Multiload, BTEQ, FastExport, and Tpump. * Experience in Teradata Data Warehouse architecture. * Proficient in application development and support, for batch processes hosted on an IBM mainframe, with a core focus in COBOL, DB2, JCL and VSAM. * Hands on experience in performance tuning, resolving on-going maintenance issues and monitoring of production runs. * Data modeling using Erwin, Star Schema, Snowflake, FACT and dimension tables. * Hands on experience in UNIX shell scripting. * Excellent communication and interpersonal skills. TECHNICAL SKILLS Frameworks | Informatica Data Director (IDD), Informatica System Integration Framework (SIF), Teradata version 12, Mainframe z/OS | Application Modules | UNIX, Informatica Application Designer, Workflow Manager, Workflow Monitor, Repository Manager, Informatica B2B...

Words: 1062 - Pages: 5

Premium Essay

Healthcare Data Warehousing

...Healthcare Data Warehousing Doug Kelley Health Informatics I Professor Lu December 7, 2012 Abstract ` Dimensional modeling lays the groundwork for data warehouses. Dimensional modeling is a similar process to traditional Entity/Relationship modeling in regards to tables (entities) having joins (relationships) with other tables via primary keys. Dimensional modeling has been used as a standard in industry for decision support systems in other areas such as transportation, production, sales and marketing. (Parmanto, 1) Because healthcare has many complex events, it has lagged behind other industries in terms of data warehousing. This paper will discuss several techniques that can help overcome these complexities. Introduction A data warehouse has been defined as a database optimized for long-term storage, retrieval, and analysis of records aggregated across patient populations, often serving the longer-term business and clinical analysis needs of an organization (Shortliffe, 932). For a data warehouse to perform these roles, it must be architected or modeled appropriately. There are a couple of different approaches to modeling data warehouses. Dimensional modeling is becoming standard approach. Background Review Designing a data warehouse for healthcare presents many unique challenges for designing a database. These include such complexities as multiple diagnoses, multiple payers, multiple physicians; primary and secondary, and late arriving data, such...

Words: 1887 - Pages: 8