1.

INTRODUCTION
1.1 Data Management and Industrial Engineering
Industrial Engineering (IE) the broadest engineering discipline. IEs in almost every sector of the economy: Manufacturing sector - automotive, electronics, etc. Service sector - restaurant chains, hotels, etc.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 1

 Financial sector banks, financial companies (e.g., Cap One) Healthcare - hospitals, nursing

homes, etc.
Government commerce, defense, etc. Transportation/Distribution - trucking firms, distribution centers, etc. Entertainment amusement parks, video games, etc.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 2

Regardless of what area an IE works in or his/her exact job description, it is almost certain to involve data management.

DATA MANAGEMENT
- the process of identifying what types of data are of interest, developing suitable methods for acquiring, storing, and using this data, and implementing such methods in practice.

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 3

What types of data are of interest to IEs? Production data Cost data Capacity data

Human (Employee) data Sales/Marketing data + others.

2009 John P. Shewchuk ISE 3024 Course Notes Introduction 4

What do IEs typically use data for? Problem solving - layout, scheduling, inventory control, etc. Decision making - choosing between alternatives (e.g., make vs. buy) Operations - data needed to run facility Location and Tracking Recordkeeping and Reporting + others.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 5

Whatever IE area we work in and particular need we have for data, we must be sure weve designed an appropriate data management application. What things must we consider in developing a data management application? Types of data (e.g., numeric, text, pictures) Volume of data (e.g., 100 data items vs. 100,000,000). Frequency with which accessed (e.g., hourly vs. monthly).

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 6

 Type of data access - Simple record storage/retrieval? Or queries too? Who needs access and where. Data integrity requirements (low vs. high). Data storage requirements (e.g., weeks vs. decades). Data security requirements (how critical)?

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 7

Additional considerations: Designing data management system - How difficult? - Specially-trained personnel needed/available? - Software/hardware purchase necessary? Maintaining data management system - Specially-trained personnel needed/available?

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 8

We will study four main data management approaches: 1) Manual filing systems forms and filing cabinets. 2) Computerized File-Based Systems store/access data, as separate files, via computer. 3) Database Systems store/access data, as related data structures, via computer. 4) Web-based Databased Systems database systems accessed over the Internet, using Web technology.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 9
1 2 3 4 5 6 7 8

Focus in this course: computerized file-based systems, database systems, and Web-based database systems. in the context of typical IE problems. We will use MS Excel (2007), Access (2007), SQL Server Express with Tools (2008) and Visual Web Developer Express (2008), all on PC (Windows or Vista), to demonstrate how various spreadsheet, database, and Web-based concepts can be applied, respectively. Keep in mind, however, that the goal of this course is NOT to teach you the above software packages and programming languages. focus: theory, concepts, techniques.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 10

1.2 Overview of Data Management Approaches

1.2.1 Manual Filing Systems

Manual filing system = collection of

file folders, each properly identified and stored in a particular filing cabinet drawer. Each folder: one or more documents of information. How is data structured in such systems? To answer this, we need some basic file terminology:
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 11

 Data = smallest item that can convey some specific information to us. e.g., John Smith, 41X-02265 Field = label identifying a particular type of data e.g., customerName, partNumber Record Type = unique collection of fields, specifying how to define similar objects of interest. e.g., customers: customerName customerState products: partNumber, partName
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 12

 Record = unique collection of data, per the associated record type, defining a particular object of interest. e.g., Customer records: John Smith, VA Alice Jones, NY Product records: 41X-02265, Widget File = collection of records of the same type. e.g., Customer file: collection of Customer records Product file: collection of Product records

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 13

Typical manual filing system: each filing cabinet drawer (set of drawers) = file each folder of information = record while the information in each folder may be different, data types (i.e., fields) are the same. (i.e., same record type, all folders that drawer.)
1985 1982

1987 1984

1986 1983

e.g., CUSTOMER file: each folder has information on a different customer. preprinted forms ensure records all same type.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 14

Data in a manual filing system is typically organized functionally. For example, any company which sells stock items to customers will likely have the following files (plus others) in a manual system: Customer file Product file customer name, address, account #, etc. what different products sold: price, description etc. availability of each product.

Inventory file Order file

what customer orders are open, details on each.

ISE 3024 Course Notes Introduction 15

2009 John P. Shewchuk

Where would we find manual filing system data? small firm: centralized storage (e.g., several filing cabinets in the main office). large firm: decentralized storage (e.g., Customer file in main office, Order file in Sales department, Inventory file cabinet on shop floor).

If the # of items is small or we are simply interested in storage and retrieval of individual records, the manual approach may well work fine.

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 16

The manual system falls apart, however, when we need to process data in more ways than simply retrieving individual records. For example, given the preceding manual files, how would you expect to answer each of the following queries (questions): How many customers reside in VA? Which products cost $10 or less? Which items are ordered in quantities of 2 or more? VA

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 17

Manual system even worse when we need to crossreference or process data from multiple files: Which customers have ordered a particular item? - must access both Customer and Order files What is the average inventory for all items in the $10-or-less category? - Product and Inventory files How many open orders contain hot items (< 5 units available) costing more than $50 and headed for the state of CA? - Customer, Product, Inventory, Order files!
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 18

Other disadvantages of manual filing systems: Lots of physical space (floor space) required. Excessive time entering/retrieving data. Error prone. Security/access concerns. Back-up concerns. Lots of duplicate data (i.e., same data in different files). more wasted space, time/effort, errors!

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 19

So, while manual systems have many disadvantages, its still important to be familiar with them: many file-based systems still in use today. understanding the manual system and its shortcomings helps you better understand how to implement a good computer-based system. Additionally, a manual system may sometimes be best! very small amount of data. v workers lack sufficient computer knowledge, skills. data processing limited to record storage/retrieval. main need is record keep (contractual)
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 20

1.2.2 Computerized File-Based Systems A computerized file-based system works like a manual filesystem, the difference being that a computer is used to store data for each file rather than one or more filing cabinet drawers.

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 21

Substantial improvement over manual filing systems: data processing many times faster and more accurate: can be automated. computerized data storage allows for data access via different application programs.

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 22

Resulting structure: Customer records

Customer applications

Product records

Product applications

Inventory records

Inventory applications

(etc.)
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 23

Various software packages (e.g., Excel) are available for this approach. one spreadsheet (ideally) each file. spreadsheet interface separates data from application.
1 2 3 4 5 6 7 8

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 24

1.2.3 Database Systems A database system is an organized set of components that define and control the collection, storage, management, and use of data. Consists of two components: Database collection of files, in an organized manner, capturing the relationships between the various records. Database Management System (DBMS) system (software) which allows users to interact with the database.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 25

Basic structure:

Customer applications DATABASE DBMS Inventory applications Product applications

(etc.)
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 26

Databases are a great improvement over computerized (and hence manual) file-based systems: minimal data duplication. m easy to share data (across files). standard methods for data management (DBMS). greater querying flexibility. Still, some disadvantages: increased initial cost. more complex. higher impact of failure.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 27

Compared to the computerized file-based approach, when should a database system be used? When we need to capture the relationships between the various objects of concern. Most important reason! allow multiple users to access the data at the same time. accomodate a larger amount of data. integrate with databased-specific applications (e.g., Web).

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 28

1.2.4 Web-Based Database Systems A Web-based database system is a database system Webwhere data input, modification, and utilization is done over a network (typically the Internet), using Web applications/technology.

2009 John P. Shewchuk

ISE 3024 Course Notes

Introduction 29

This approach to databases is popular as it offers improved accessibility (browsers everywhere). improved ease-of-use (everyone familiar with Web). You are all familiar with Web-based databases already! e.g., VT website, online shopping. Web-based database systems can also be used for internal company data management applications. and hence IE problem-solving! Thus, it is important that you have some idea of how these systems are designed and implemented.
2009 John P. Shewchuk ISE 3024 Course Notes Introduction 30