Introduction to Industrial Engineering & Productivity

What industrial engineers do: design, improve and manage systems of people, machines, materials, information and money. Learn the history (Taylor, Gilbreths, Ford, Toyota), the systems view, productivity (partial and total factor), efficiency, utilisation and capacity, the key sub-fields (work study, operations research, production planning, quality, lean, supply chain, ergonomics, economics) and how IE applies to factories, hospitals, airports and software — with Python for productivity and utilisation.

Industrial engineering (IE) is the engineering of systems: how to produce goods or deliver services with the least waste of time, money, materials, energy and human effort, while keeping quality and safety high. Where a mechanical engineer designs a machine, an industrial engineer designs the factory, the process and the work around it.

IE thinking is everywhere: in hospital bed scheduling, airline crew planning, e-commerce warehouses, call-centre staffing, and lean start-ups. Its tools — measurement, modelling, optimisation, statistics and human factors — are universal.

An analogy

If a factory were an orchestra, mechanical and electrical engineers build the instruments; the industrial engineer is the conductor and arranger, making sure every player comes in at the right time, nobody waits idle, and the whole performance is efficient and harmonious.

History and scope

Frederick Taylor's scientific management (1911) timed and standardised work; Frank and Lillian Gilbreth studied motions and human factors; Henry Ford's moving assembly line (1913) cut Model T assembly from 12 h to 93 min; Shewhart and Deming brought statistical quality; the Toyota Production System created lean manufacturing. Today IE also draws on operations research, data science and systems engineering.

IE sub-fields

The toolbox of this branch:

Measures of performance

Productivity (output per input), utilisation (time busy/time available), efficiency (actual vs standard), capacity (design, effective, actual), throughput, lead time, work-in-process (WIP), cost, quality and on-time delivery. Little's law (WIP = throughput × lead time) links three of them and applies to any stable system.

Systems thinking and Industry 4.0

Improving one machine can make the whole system worse if it isn't the bottleneck (Theory of Constraints). IE takes a system view: define objectives, model interactions, test changes (simulation), implement, measure, standardise. Industry 4.0 brings sensors, digital twins, real-time scheduling and AI — but the IE fundamentals of flow, variability and human-centred design still decide results.

Formulas

Worked example: Labour productivity

Given: 1200 units, 320 labour-hours

Find: Productivity.

Answer: 3.75 units per labour-hour

Worked example: Utilisation and efficiency

Given: Design capacity 100/h, effective 80/h, actual 72/h

Find: U and E.

Answer: U = 72%, E = 90%

Worked example: Multifactor productivity

Given: Output worth ₹10 lakh; labour ₹3 lakh, materials ₹4 lakh, overhead ₹1 lakh

Find: MFP.

Answer: 1.25

Productivity and utilisation of a machining cell

# Productivity and utilisation of a machining cell
output_units, labour_h, machine_h = 1200, 320, 400
avail_h = 3 * 8 * 22             # 3 machines x 8 h x 22 working days (one month)
print(f"labour productivity {output_units/labour_h:.2f} units/labour-h")
print(f"machine utilisation {machine_h/avail_h*100:.0f}% of {avail_h} available hours")
# Productivity change after an improvement
before, after = 1200 / 320, 1350 / 300
print(f"productivity gain {(after/before - 1)*100:.1f}%")
# labour productivity 3.75 units/labour-h
# machine utilisation 76% of 528 available hours
# productivity gain 20.0%

Producing more (1350) with fewer labour-hours (300) raises labour productivity by 20%. Industrial engineers track several partial measures together — improving labour productivity by buying expensive robots may reduce capital productivity.

Common mistakes

Applications

Key takeaways

Going further