ENGINEERING MANAGEMENT

ENGE5201 — Explained Course Notes

Content + intuition: not just what, but why

National Higher Polytechnic Institute (NAHPI)

The University of Bamenda

Course Master: Dr Mekam / Engr Wetka T.

Orange boxes throughout explain the reasoning behind

each concept — read them to understand, not just
memorise.

Engineering Management (ENGE5201) — Explained Notes | Page 1 of 22

ENGINEERING MANAGEMENT (ENGE5201) —
EXPLAINED COURSE NOTES
NAHPI / The University of Bamenda — Course Master: Dr Mekam / Engr Wetka T.

How this document works: the normal text gives you the course content; the indented "In plain
terms", "Why it matters" and "Intuition" boxes explain why each idea is true and how to think
about it. Read both — the boxes are what turn memorised facts into understanding you can defend
in an exam answer.

Engineering Management (ENGE5201) — Explained Notes | Page 2 of 22

CHAPTER 1 — INTRODUCTION TO ENGINEERING
MANAGEMENT

1.1 What the field is and why it exists

Engineering management is a specialised form of management concerned with applying engineering

principles to business practice. In a modern economy customers' needs change fast, markets are
global, and technology moves quickly, so companies need leaders who understand both technology
and business.

In plain terms: an engineer knows how to build the thing; a manager knows how to run the
business. Engineering management is the overlap — the person who can talk to both the lab and
the boardroom. The whole subject exists because that overlap is rare and valuable: a brilliant
engineer who can't budget, and an MBA who can't read a technical drawing, both fail in a tech
company.

A manager is an employee trusted to: use communication, make critical decisions, take action, apply
resources, and guide the behaviour of teams and partners to reach company goals.
- Decisions weigh three things together: technical feasibility, resource conservation, economic
viability.
- Actions are the four management functions: planning, organizing, leading, controlling.
- Resources include people, time, capital, equipment, facilities, technology, know-how, relationships.

Why it matters: notice decisions are never only technical. "Can we build it?" is not enough — you
also ask "is it worth the resources?" and "will it make money?". That triple test is the heart of the
whole course.

Key statistic to quote: engineers reach a career decision point 3–7 years after graduation —
technical-specialty route vs. technical-management route — and more than 75% choose
management while keeping their technical identity. Yet engineers are rarely trained for management,
which is exactly the gap this course fills.

1.3 Definitions

Engineering — the profession in which knowledge of mathematical and natural sciences (gained by
study, experience, practice) is applied with judgment to develop ways to economically utilise the
materials and forces of nature for the benefit of mankind.

In plain terms: the three key words examiners look for are judgment, economically, and for
mankind. Science gives you knowledge; engineering adds judgment (choosing the best practical
option) and the goals of being cheap enough to be useful and beneficial to people.

Management — the process of leading and directing an organisation through the deployment of
resources (human, financial, material, intellectual, intangible). From Latin manu agere = "to lead by
the hand."
Engineering Management — the functional management of technical professionals.

Engineering Management (ENGE5201) — Explained Notes | Page 3 of 22

 Why "technical professionals" is the key phrase: engineers are typically driven by problem-
solving curiosity, not entrepreneurial profit. So managing them isn't like managing salespeople —
you need technical credibility to earn their respect (a "technically inept" manager loses the team)
and commercial sense to survive in the market (a "non-commercial" manager can't deliver value).
That dual requirement is why engineering management is treated as its own discipline.

18 types of engineering (Agricultural, Architectural, Bio/Biomedical, Ceramic, Chemical, Civil,

Computer, Electrical, Environmental, Fire Protection, Industrial, Manufacturing, Mechanical, Metallurgy
& Materials, Mineral & Mining, Nuclear, Ocean, Transportation) and 30 areas of management
(Change, Communications, Constraint, Cost, Crisis, Customer relationship, Earned value,
Engineering, Enterprise, Facility, Integration, Knowledge, Marketing, Micromanagement, Pain,
Perception, Procurement, Program, Project, Process, Product, Quality, Resource, Risk, Skills, Spend,
Supply chain, Systems, Time, Stress).

1.4 Management responsibilities — the five stakeholders

Management must satisfy five stakeholder groups, each wanting different things:

Stakeholder What they want The underlying interest

Shareholders ROI, dividends, EPS, rising share price They risked their money — they want it to
grow

Customers Quality, service, flexibility, fast delivery, low They have a choice — keep them or lose
price them

Suppliers Stability, market share, quality, on-time They want a reliable, paying long-term
payment partner

Employees Good culture, conditions, job security, fair pay They give their labour — they want it
respected

Community Clean environment, taxes, ethics, good The company uses shared resources/space
citizenship

Why it matters: these wants often conflict (paying employees more reduces shareholder profit;
lower prices for customers squeeze suppliers). Good management is largely the art of balancing
these tensions — a theme that returns in Chapter 4 ("the firm as a coalition").

1.5 The three types of work (very common exam item)

1. Management work — plan, organise, lead, control → requires THINKING.

2. Technical work — specialised hands-on work → requires DOING.
3. Operating work — work delegated to others → requires MONITORING & CONTROLLING.

Memory hook: Think → Do → Monitor. A manager thinks about what to do, occasionally does
technical work when no one else can, and monitors the work they've handed off.

1.8–1.9 Efficiency, and strategic vs operational decisions

• Efficiency = doing a task with the least effort/no wasted resources.

• Strategic decisions = the right things to do — set direction (which markets, which products).
Made by managers; the CEO makes strategic decisions only.
• Operational/tactical decisions = how to do things correctly. Made by technical contributors.

Engineering Management (ENGE5201) — Explained Notes | Page 4 of 22

 The clean way to remember this: strategic = WHAT and WHY (direction); operational = HOW
(execution). The higher you rise, the more your work shifts from "how" to "what." This exact
distinction reappears in 1.11 and is a favourite exam contrast.

1.10 Products vs Services — Tidd & Bessant (2013), six

characteristics

Why it creates a management

# Characteristic Product Service
problem

1 Tangibility tangible intangible You can't inspect a service before

buying it

2 Perceptions judged by judged by responsiveness, Service quality is subjective and

function/ empathy, assurance harder to control
reliability

3 Simultaneity made before use made during use You can't fix a service error before
the customer sees it

4 Storage can be stored can't be stored Idle service capacity is lost

forever → pricing/temp staff fixes

5 Customer low high Services need front-line people

contact skills

6 Location shippable local Only ~10% of services are traded

internationally

Intuition: the single idea behind all six is that a service is produced and consumed at the
same moment, in front of the customer, while a product is made first, then sold later.
Every difference flows from that. If you understand that one sentence, you can reconstruct the
whole table.

STEM professionals as technical contributors — five steps to perform

well

1. Show technical competence + innovation, 2. Practise people skills, 3. Show reliability, 4. Be

proactive, 5. Build work skills, 6. Show readiness for advancement.

Why this list exists: it's the career ladder. Early on you're judged on (1) technical skill. To get
promoted you need (2)–(4) people/reliability/initiative, because managers manage through people.
The famous line — "if opportunities do not knock, build a door" — is the spirit of step 4.

1.11–1.13 The effective engineering manager and the four-

dimensional job

Managers decide what (strategic); contributors decide how (tactical). The manager's job is four-
dimensional (Fig 1.1) — they must manage relationships in four directions:
1. Up — with superiors (anticipate their needs)
2. Down — with subordinates
3. Sideways — with peers/staff
4. Inward — with self (own time)

Engineering Management (ENGE5201) — Explained Notes | Page 5 of 22

 Crucial exam point: engineering managers do NOT do the technical work themselves — they work
through people. This trips students up because they assume the "best engineer" should keep
engineering. The course says the opposite: a manager's value is in deciding and assigning, not
doing.

Two product-development philosophies:

- Market-driven — ask customers first, then build (lower risk, may miss breakthroughs).
- Technology-driven — invent first, then find a market (higher risk, bigger payoffs).

Example 1.1 (explained)

A company fears foreign imports will beat it to market. The clever answer is a third option: import
the foreign product under your own brand via a private-label contract.

Why this is smart: it lets the company test the market cheaply instead of gambling millions on
full development. If customers like it, develop your own; if not, you've lost little. It's a "buy time and
information" strategy — a classic engineering-management trade-off between speed, cost, and risk.

Example 1.2 (explained)

John presents staff member Steve's work as his own, then gives Steve a bonus. Verdict: acceptable in
industry because credit was eventually given, but he should formally recognise Steve (progress
reports, staff meeting).

What the examiner wants: recognise the ethics issue (taking credit is wrong) and the practical
resolution (he corrected it). The course rewards balanced, real-world judgment, not just "John was
bad."

Engineering Management (ENGE5201) — Explained Notes | Page 6 of 22

CHAPTER 2 — PRINCIPLES OF MANAGEMENT
PRACTICE
Why study old theory? Because management thought is cumulative — today's practice is built on
past contributions. A theory is just a framework that organises knowledge into a blueprint for action.

2.1 The four schools of management thought

School Core idea Key figures

Classical Find the one best way to organise Taylor, Gilbreths, Gantt (scientific); Weber (bureaucratic);
work Fayol (administrative)

Behavioural People and psychology drive Follett, Mayo, Maslow, McGregor, Argyris
performance

Quantitative Use maths/data to decide (management science, operations, MIS)

Modern See the whole system; it depends Systems theory, Contingency theory, Ouchi (Theory Z)
on context

The story across the table: management thinking evolved from "there's one right way"
(Classical) → "but people aren't machines" (Behavioural) → "let's use numbers" (Quantitative) →
"actually, it depends on the situation" (Modern). Knowing this arc lets you place any theorist
correctly.

2.2 Fayol's 14 Principles (the single most exam-likely list)

French industrialist, 1916, nicknamed the "Universalist" because he believed these apply to every
organisation. Grouped for easier recall:
Group A — Structuring the work
1. Division of work — specialise → more efficient.
2. Authority & Responsibility — they come as a pair; if you give authority, responsibility follows.
3. Discipline — rules + fair penalties + good leadership.
Group B — Lines of authority
4. Unity of Command — one boss per employee (two bosses = conflict).
5. Unity of Direction — one plan per objective.
6. Subordination of individual interest — the organisation comes first.
7. Remuneration — fair pay for both sides.
8. Centralisation — find the right balance of central vs delegated decisions.
9. Scalar Chain — a clear top-to-bottom line of authority.
Group C — People and morale
10. Order — right person/thing, right place.
11. Equity — fairness + kindness.
12. Stability of tenure — keep people long-term.
13. Initiative — let people propose and act.
14. Esprit de Corps — team spirit; "union is strength."

Engineering Management (ENGE5201) — Explained Notes | Page 7 of 22

 In plain terms: Fayol is basically saying — set up the work clearly (A), make authority
unambiguous (B), and treat people fairly so they stay motivated (C). If you blank on the list,
reconstruct it from these three themes.
Distinction students confuse: Unity of Command (one boss) vs Unity of Direction (one plan).
Command = people; Direction = objectives.

2.3 Modern theory: System vs Contingency

System Approach — an organisation is a set of interrelated parts that take inputs → transform →
outputs, and the sale of outputs feeds back as energy. It's an open system (exchanges with its
environment). Eight traits: Dynamic, Multilevel, Multi-motivated, Probabilistic, Multidisciplinary,
Descriptive, Multivariable, Adaptive.

Intuition: think of a living body — change one organ and the rest react. A company is the same:
marketing, production and finance are interconnected, and the firm survives only by adapting to its
environment (feedback). "Open system" just means it isn't sealed off — it imports resources and
exports products.

Contingency Theory (after 1970) — the core slogan: "there is no one best way to manage." The
right approach depends on the situation.
- Limited resources + unskilled labour → work simplification.
- Skilled labour → job enrichment.
Two strengths: (1) it focuses you on the specific situational factors, (2) it builds your situational-
analysis skills. Goal = achieve a "fit" between organisation and environment.

The key contrast to nail in an exam: Classical theory hunts for the one best way; Contingency
theory says it depends. System theory says everything is connected; Contingency theory builds on
that by adding so the best action changes with the context. If a question asks "compare," lead with
these one-line contrasts.

Engineering Management (ENGE5201) — Explained Notes | Page 8 of 22

CHAPTER 3 — MANAGEMENT FUNCTIONS
The four basic functions — Planning, Organizing, Leading, Controlling (POLC):

Function What you actually do Failure if missing

Planning Set goals and decide how to reach them Aimless activity

Organizing Arrange people/resources to fit the plan Chaos, duplication

Leading Motivate and direct people Low effort, no buy-in

Controlling Measure results, correct deviations You never know if you succeeded

Why these four, in this order: you plan what to do, organise who and what will do it, lead people
to actually do it, then control by checking results and adjusting. It's a loop — controlling feeds back
into the next round of planning.

Managers use the Rational Decision method for decisions and Monte Carlo methods for projects
with risk and uncertainty.

Monte Carlo, simply: instead of guessing one outcome, you run thousands of simulated scenarios
with random variations and look at the range of results. It's used precisely when the future is
uncertain. (Review your group presentations for this chapter's detail.)

Engineering Management (ENGE5201) — Explained Notes | Page 9 of 22

CHAPTER 4 — STRUCTURES OF A BUSINESS
(FIRMS)

4.1 The firm as a "coalition"

An organisation is a coalition of individuals (managers, workers, shareholders, suppliers,

customers…) with their own goals.

Why this idea is powerful: if a firm is a coalition of people with different goals, then "the firm's
goal" is not one clean thing — it's a negotiated truce between competing interests. This is the
foundation for the goal-conflict discussion later, and it directly challenges the naive idea that "a firm
just maximises profit."

Separation of ownership and control — in large firms, ownership (shares) is spread among many
people, while salaried managers (who own few shares) actually run things. From the 1930s the
"management school" argued these managers are only loosely pushed to maximise profit.

Intuition: if you own 0.001% of a company but control its daily decisions, your incentive to squeeze
out every last franc of shareholder profit is weak — you might prefer a bigger empire, a nicer office,
or a quiet life. That gap between owners' wishes and managers' behaviour drives much of this
chapter.

Chain: Shareholders → Board of Directors → Top Management. To remove a director,

shareholders must win a costly vote (enforcement costs), so managers often have real freedom.

4.1.2 Market structure — four dimensions

i. Seller concentration, ii. Buyer concentration, iii. Product differentiation, iv. Condition of entry.
Seller concentration → market form:
- 1 seller = monopoly, 2 = duopoly, few = oligopoly, many = competition. (1 buyer =
monopsony.)

Why concentration matters: the fewer the sellers, the more each one can push prices up. This
single fact is the engine of the whole SCP paradigm later — concentrated markets → market power
→ higher prices.

Bain's 3 determinants of entry conditions: economies of scale, product differentiation, absolute

cost advantages.

Read these as "barriers to entry": they're the three things that make it hard for a new firm to
break in, which is what protects existing firms' profits.

Engineering Management (ENGE5201) — Explained Notes | Page 10 of 22

4.2 Goals of the firm — five goals (Cyert & March)

Goal Who pushes it Conflicts with

Production Production dept (stable output) — prefers stockpiling over cutting output

Inventory Sales + production (full stock) Finance (stock ties up cash)

Sales Sales staff (survival) Profit (sales may want lower prices)

Market share Management (best comparison metric) —

Profit Top management (investment, dividends) Sales/inventory goals

The real lesson: these goals clash — sales wants a low price, profit wants a high one; sales/
production want big inventories, finance hates them. The firm doesn't "solve" this cleanly.

Four mechanisms to manage conflict (Cyert & March):

- a. Satisficing — aim for "good enough" aspiration levels, not perfect maximisation; only the failing
goal gets attention.
- b. Sequential attention — deal with goals one at a time, not all at once.
- c. Organisational slack — keep spare resources to draw on when a goal underperforms.
- d. Standard operating procedures — routine rules that avoid re-arguing every decision.

In plain terms: firms cope with conflicting goals not by finding the perfect balance, but by (a)
settling for "good enough," (b) taking turns, (c) keeping a buffer, and (d) following routines. This is
the famous "bounded rationality" view — people can't optimise everything, so they satisfice.

4.2.2 Why firms aren't simple profit-maximisers

"Firms don't have motives — only people do." Managers often want size → growth (bigger empire,
more security) rather than pure profit.

Why examiners love this: it's counter-intuitive. Basic economics says "firms maximise profit," but
this chapter says that's "strictly speaking, absurd" because a firm is just a bundle of people with
mixed motives — and managers frequently chase growth and size instead.

4.3 Legal forms of business

Three sectors: Private, Public, Joint.

Four PRIVATE forms — the trade-off running through all of them is liability vs. control vs. ability
to raise money:

Form Owners Liability Raising capital Control

Sole proprietorship 1 Unlimited Hardest Total

Partnership 2–20 Unlimited Moderate Shared

Joint-stock company many shareholders Limited Easiest (shares) Delegated to directors

Cooperative voluntary members varies member-funded democratic

Engineering Management (ENGE5201) — Explained Notes | Page 11 of 22

 The master trade-off to understand: as you move down the table you gain the ability to raise
money and gain limited liability (your personal assets are safe), but you lose direct control and gain
legal complexity. A sole trader has total control but risks everything personally; a corporation
protects you and raises millions but you answer to a board. Every advantage/disadvantage in the
notes is a consequence of this trade-off.

Sole proprietorship — simplest, one owner. Fast decisions, full control, secrecy — but unlimited
liability (you can lose personal assets) and the business dies with the owner.
Partnership — 2 to ~20, sharing profits (the defining feature). Still unlimited liability, plus you're
liable for a dishonest partner's actions and even after you retire. Partner types: active, sleeping,
secret, nominal, quasi/estoppel.

Why "sharing of profit" is THE definition: the notes stress that partnership is defined by profit-
sharing, not by joint capital or joint management. Partners can contribute unequally and still be
partners.

Joint-stock company / corporation — the dominant modern form; a legal "artificial person." Nine
characteristics, but the three that matter most:
- (g) Limited liability — shareholders risk only what they invested. This is the whole reason
corporations can raise huge capital — investors aren't betting their houses.
- (b) Perpetual succession — the company outlives its members. A shareholder dying doesn't kill
the firm.
- (d) Delegated management — owners (shareholders) elect directors to run it. This is exactly the
"separation of ownership and control" from 4.1.
Numbers to memorise (commonly tested):
- Private Ltd: restricts share transfer, max 50 members, no public share offer, min 2 shareholders.
- Public Ltd: no restrictions, min 7 shareholders, no upper limit.

Memory hook: Private = 2 to 50 and "private" (no public invite); Public = 7 and up, open
to all.

Cooperative — voluntary association for a common economic interest (consumer, producer,

marketing, credit, farming, housing).
PUBLIC sector exists for three non-profit reasons: control the commanding heights of the
economy, drive strategic/social development, generate surplus to fund the nation. Types:
departmental organisations (Post, Rail), statutory corporations (Airlines, Insurance), and government
companies (≥51% state-owned).
JOINT sector — government + private entrepreneur share ownership and put a mutual check on
each other.

4.4 The SCP Paradigm — the chapter's central theory

Structure → Conduct → Performance, introduced late 1930s–1940s.

Read the arrow as a causal chain: the structure of a market (e.g., few firms) shapes how firms
behave/conduct themselves (e.g., they collude or compete), which determines the market's
performance (prices, profits, efficiency). Less competition → more market power → higher prices
and profits → worse outcomes for consumers (allocative inefficiency).

The catch: collusion can't be observed directly, so economists infer it. If they see high
concentration + high profits, they conclude firms are probably colluding.

Engineering Management (ENGE5201) — Explained Notes | Page 12 of 22

4.5 Measuring performance — the Lerner Index and its four proxies

Lerner Index = (P − MC) / P — measures how far price sits above marginal cost.

Intuition: in perfect competition, price = marginal cost, so the Lerner index = 0. The more a firm
marks price up above its cost of making one more unit, the more market power it has, and the
higher the index. It's basically a "how much can they overcharge?" score.

The problem: we rarely know marginal cost (MC). So four proxies stand in for it:

Proxy Formula When/why used Weakness

Excess return (TR − TC)/TR Equals Lerner index under Hard to get true economic
on sales constant returns to scale profit

Profit rate (Π − T)/E Matches what investors Distorted by debt/equity

(equity) maximise ratio

Profit rate (Π − T + I)/A Fixes the debt/equity distortion Numerator & denominator
(assets) move together

Price-cost (TR − VC)/TR Uses plant-level census data → Joint costs prevent true
margin fits structure better return calc

Tobin's q Market value / Avoids estimating MC or returns Ignores intangibles, so q

Replacement cost usually > 1

The thread linking them: none of these is the Lerner index itself — they're all work-arounds
because real MC data doesn't exist. Each fixes a flaw in the previous one (e.g., return-on-assets fixes
return-on-equity's debt problem), and each introduces its own new flaw. The exam may ask you to
define one and state its weakness — that pairing is the point.
Tobin's q, intuitively: if a company is worth more on the stock market than it would cost to
physically rebuild it, investors think it earns excess profits. q > 1 signals market power. If q = 2,
earnings would have to halve to reach a competitive level.

Economic vs accounting profit — economic profit subtracts opportunity cost; accounting profit
doesn't. Accounting data also mismeasures capital (uses historical/book value instead of
replacement cost), depreciation, advertising/R&D timing, and inflation.

Why this distinction is tested: accounting profit can look healthy while economic profit is zero or
negative, because accounting ignores the return you could have earned elsewhere (opportunity
cost). A firm "profitable" on paper may be destroying value economically.

4.5.2 Measuring structure — the exogeneity problem

Concentration ratio CRₙ = sales share of the n biggest firms.

The deep problem (worth a mark): to prove "structure causes profits," structure must be
exogenous (decided before profits, not affected by them). But concentration isn't — high profits
attract new entrants, which changes concentration. So profits and structure influence each other,
muddying cause and effect. A genuine entry barrier (e.g., a government ban) is a better, truly
exogenous measure.

Engineering Management (ENGE5201) — Explained Notes | Page 13 of 22

CHAPTER 5 — ACCOUNTING METHODS

5.0 What accounting is really for

Accounting = collecting, analysing and communicating financial information to help users make
better decisions. Finance = how funds are raised and invested to create wealth.

In plain terms: accounting isn't about producing reports for their own sake — it's a decision-
support tool. If the information doesn't improve a decision, there's no point producing it. Keep this
purpose in mind and the rest of the chapter makes sense.

5.1–5.2 Users and their conflicts

Users: owners, managers, lenders, suppliers, customers, competitors, employees, government,

investment analysts, community.

Why they conflict: the most likely fight is over how business wealth is shared. Example:
managers might pay themselves big salaries and buy fancy cars instead of serving owners.
Accounting is the referee — it reveals who's taking what, so owners can check on managers and
lenders can check that their loan wasn't misused.

5.6 Qualitative characteristics — what makes statements useful

1. Understandability — clear enough to read.

2. Relevance — useful and timely (old data is useless).
3. Reliability — faithful, verifiable, unbiased.
4. Comparability — comparable across companies and over time.

Memory + logic: information has to be clear, relevant, trustworthy, and comparable. Drop
any one and a banker can't safely lend on it — which is exactly the audience the notes keep
mentioning (banks, sureties, investors).

Five financial statements: balance sheet (position now), income statement (performance over
time), retained-earnings statement, cash-flow statement, and notes.

The simplest way to keep them straight: the balance sheet is a photo (one moment); the
income and cash-flow statements are videos (a period of time).

5.7 The assurance ladder — Audit > Review > Compilation

Engagement What the accountant does Assurance level Credibility

Audit Independent, rigorous testing; gives an opinion on fair High (not Highest
presentation absolute)

Review Mainly enquiry + analysis; checks info is plausible Moderate/ Some

limited

Compilation Just compiles client data; adds "notice to reader" Lowest/none Least

Engineering Management (ENGE5201) — Explained Notes | Page 14 of 22

 Why "high" but not "absolute" for an audit: the auditor can't check 100% of transactions and
must rely partly on management's word and judgment. So even a clean audit guarantees
reasonable, not perfect, assurance. Banks trust audited accounts most precisely because of the
independence and rigour involved.

5.9 Book-keeping and the debit/credit logic

• Single-entry = record once (simple, profit/loss only). Double-entry = record twice (accurate,
self-checking — the preferred system).

Why double-entry self-checks: every transaction has two sides (you got something and gave/
owed something). Recording both means the books must always balance — if they don't, you've
made an error. That built-in check is why the whole world uses it.

The book-keeping equation (memorise both forms):

Assets = Liabilities + Net Assets ⟺ Assets − Liabilities = Net Assets

Intuition: everything a business owns (assets) was paid for either by borrowing (liabilities) or by
the owners' own money/earnings (net assets). So owned = owed + owners'. It can never not
balance.

Debit/credit rules (the part everyone forgets):

- Assets: ↑ = debit, ↓ = credit (assets are "debit accounts").
- Liabilities & Net assets: ↑ = credit, ↓ = debit (they're "credit accounts").
- Expenses reduce net worth; revenue increases it.

Why a worked example clarifies it (Business X): start 5,000,000 = 2,000,000 + 3,000,000.
- Borrow 2m: an asset (cash) goes up AND a liability (loan) goes up → 7,000,000 = 4,000,000 +
3,000,000. Both sides rise equally — the equation holds.
- Get a 5m grant: asset up, net assets up → 12,000,000 = 4,000,000 + 8,000,000.
- Repay 1m: asset down, liability down → 11,000,000 = 3,000,000 + 8,000,000.
Notice every transaction changes at least two items and the equation always rebalances. That's
double-entry in action.

Double-entry examples: borrow → debit Cash / credit Notes Payable; wages → debit Wages
Expense / credit Wages Payable; credit sale → debit Accounts Receivable / credit Sales.

Engineering Management (ENGE5201) — Explained Notes | Page 15 of 22

CHAPTER 6 — FEASIBILITY STUDIES OF
ENGINEERING PROJECTS

6.0–6.1 Why feasibility studies exist

A feasibility analysis asks two questions before you commit money: (1) Can we actually finish this?
and (2) Will it deliver real benefits? The output that summarises "do the benefits beat the costs?" is
the business case.

The hard statistic: a PMI survey found over 50% of projects are not successful. Since
megaprojects cost millions, the cheapest mistake is the one you never start. A feasibility study is
insurance — it lets you "kill" a doomed project early and save the money. That's its entire
justification.

6.3 The dimensions of feasibility — each guards against a different

risk

Dimension The question it answers The risk it catches

Market Will anyone buy it? Building something nobody wants

Financial Can we repay debt & earn a return? Running out of money

Technical Can we actually build it (inputs→throughput→output)? Engineering failure

Economic Do benefits exceed costs to society/firm? Cost > value

Ecological Will it harm the environment / fail clearances? Regulatory rejection

Legal & admin Can we get approvals/permits? Being shut down

Operational Can the organisation run it day-to-day? ERP-style failure

Schedule Can we finish on time? Endless delays

Resource Do we have the skilled people? No one to do the work

Why so many dimensions: different projects die for different reasons. An IT project mostly faces
technical risk; a construction project faces financial risk (it's capital-intensive); a vaccine roll-
out may not be financially viable at all but is justified on social/economic grounds. The dimension
list is a checklist so no fatal risk is missed.

6.3 Financial tools — the two calculations you must master

A. Net Present Value (NPV) — the time value of money

PV = Future Value / (1 + r)ⁿ, where r = cost of capital, n = years

NPV = (sum of PV of all inflows) − (sum of PV of all outflows)

Why money today is worth more than money later — two reasons:
1. Inflation — prices rise, so the same 100 frs buys less next year.
2. Opportunity cost — 100 frs today could be invested to earn interest; waiting forfeits that.

Engineering Management (ENGE5201) — Explained Notes | Page 16 of 22

 Intuition for the formula: discounting "shrinks" future money back to today's value. At 10%, 100
frs received in a year is only worth 90.9 today (because 90.9 invested at 10% would grow to 100).
Three years out, it's worth just 75.13. The further away the cash, the more it shrinks.

The worked example, explained line by line (cost of capital = 10%):

| Cash flow | Year | Raw amount | Discounted (PV) | Why |
|---|---|---|---|---|
| Buy raw materials | 0 (now) | −200 | −200.00 | Today's money isn't discounted |
| Milestone payment 1 | 1 | +150 | +136.36 | 150 ÷ 1.10 |
| Milestone payment 2 | 2 | +300 | +247.93 | 300 ÷ 1.21 |
| Pay contractor | 3 | −200 | −150.26 | 200 ÷ 1.331 |
| | | NPV | = 34.03 | sum of the PVs |

The punchline that makes the concept click: in raw terms the project nets +50,000 (450,000
in − 400,000 out). But once you account for when the cash arrives, it's only worth 34,030 today.
The 16,000 difference is the time value of money. A positive NPV (here, +34.03) means the project
earns more than the 10% cost of capital, so it's worth doing.

NPV limitations: hard to operate, cash-flow dates/amounts are guesses, the discount rate is
assumed, and a high-NPV project may still be rejected if it needs a huge upfront investment.

B. Payback Period — how fast you get your money back

Payback = Total investment / Average annual net cash flow

- Project A: 1,000,000 ÷ 250,000 = 4 years
- Project B: 200,000 ÷ 100,000 = 2 years → B wins (faster payback)
Why lower payback is preferred: the sooner you recover your cash, (1) the sooner you're "safe,"
and (2) the less time you're exposed to things going wrong. It's a crude risk measure. Its
weakness (not in the notes but worth knowing): it ignores everything that happens after payback
and ignores the time value of money — which is exactly why NPV exists alongside it.

6.4 Stakeholders — who has a stake in the study

Owner (needed it), Originator (suggested it), Sponsor (funds it), Project champion/director (drives it),
Users (operate it), Customers (pay for output), Project team, Senior management, Functional
managers (lend resources), External parties (neighbours, NGOs, banks, government).

The power-plant example ties it together: the electricity board = owner, the operating staff =
users, the households = customers. Separating these roles matters because each stakeholder
judges the project by a different yardstick.

6.5 Conducting the study — and the risk-vs-issue distinction

Five steps: (1) Examine the problem/opportunity, (2) Identify requirements, (3) Undertake the study
(find solutions → assess via prototypes/surveys → evaluate → identify risks → prioritise issues →
record assumptions), (4) Rank results, (5) Identify the outcome (recommend the top 2–3 options). The
output = the Feasibility Study Report.

Engineering Management (ENGE5201) — Explained Notes | Page 17 of 22

The distinction examiners love — Risk vs Issue:
- A risk is something that might happen (uncertain, probabilistic) → you mitigate it.
- An issue is something that is certain and is already hurting the solution → you resolve it.
Example: "the team might lack a skill" = risk (mitigate by planning to outsource). "The funds are not
budgeted" = issue (resolve by requesting funding now). Risk = future maybe; Issue = present
certainty.
Why prototypes and surveys: you use a prototype when you can't fully describe the solution in
words (build a small version to show stakeholders — the Statue of Unity team built 3). You use a
survey to test demand: internal surveys gauge staff buy-in, market surveys gauge customer
demand. Both reduce the risk of building the wrong thing.

Engineering Management (ENGE5201) — Explained Notes | Page 18 of 22

CHAPTER 7 — CONTRACTS

7.0 What makes an agreement a contract

Contract = Agreement + Enforceability by law. Not every agreement is a contract — agreeing to

meet a friend for a film isn't enforceable; agreeing to buy goods is.

In plain terms: the law won't drag you to court over a casual social promise. It will enforce a
promise where both sides intended legal consequences and exchanged something of value. The
whole chapter is a list of the conditions that flip a mere agreement into a legally binding contract.

7.1 The three parts: Offer → Acceptance → Agreed terms

• Offer/Proposal — one party signals willingness (by words or actions).

• Acceptance — must be (1) absolute, (2) communicated, (3) in the prescribed mode, (4) within
time.

Why acceptance has rules: a vague or silent "maybe" can't bind anyone. Acceptance must be a
clear, communicated "yes" to the exact offer — otherwise it's a counter-offer, not acceptance.

7.3 The ten essential elements — each one explained

# Element Why the law requires it

1 Offer & Acceptance There must be a clear "I offer" met by a clear "I accept"

2 Intention to create legal Social promises (dinner) aren't meant to be enforceable

relations

3 Lawful consideration Each side must give and get something — a one-way gift isn't a
contract

4 Capacity of parties A minor, lunatic, or drunk person can't be held to a deal

5 Free consent A "yes" forced by coercion/fraud/mistake isn't real agreement

6 Lawful object You can't enforce a contract to do something illegal/immoral

7 Certainty If the terms are vague, a court can't enforce them

8 Possibility of performance You can't be bound to do the impossible

9 Not expressly void Some agreements are banned outright (see below)

10 Legal formalities Some deals (land, etc.) must be written/registered

The logic behind the list: a court will only enforce a deal that is genuinely agreed (1,2,5),
fairly exchanged (3), made by capable people (4), legal (6,9), clear (7), doable (8), and
properly recorded (10). Every element removes one way a deal could be unfair or unworkable.

Consideration can be an act, a forbearance (not doing something), or a promise — and can be past,
present, or future — but must be lawful.
Free consent is absent if caused by: coercion, undue influence, fraud, misrepresentation, or
mistake. (If both parties act under a mistake, the agreement is void/avoidable.)

Engineering Management (ENGE5201) — Explained Notes | Page 19 of 22

 Distinction: coercion = threat/force; undue influence = abusing a position of power over someone;
fraud = deliberate lie; misrepresentation = innocent false statement; mistake = both sides wrong
about a fact.

Five expressly void agreements: restraint of (1) marriage, (2) trade, (3) legal proceedings, (4)
uncertain-meaning agreements, (5) wagering (betting).

Why these are banned: the law won't enforce a deal that stops you marrying, stops you earning a
living, blocks your access to courts, makes no clear sense, or is pure gambling. They're void on
public-policy grounds.

Writing/registration is required for land deals (lease, gift, sale, mortgage), negotiable instruments,
and a company's memorandum & articles. An oral contract is otherwise valid — but hard to prove,
which is why serious deals are written down anyway.

Engineering Management (ENGE5201) — Explained Notes | Page 20 of 22

EXAM-DAY ANCHORS — the "why" in one line each
• Engineering management exists because the technology↔business overlap is rare and
valuable.
• Strategic = what/why; operational = how. CEO does strategic only.
• Products vs services all flow from: services are produced as they're consumed.
• Fayol = structure the work (A), make authority clear (B), keep people motivated (C).
• System theory = everything's connected; Contingency = so the best action depends on the
situation.
• POLC is a loop: plan → organise → lead → control → (re-plan).
• The firm is a coalition of people with conflicting goals; it satisfices, it doesn't perfectly maximise.
• Legal forms trade off liability vs control vs ability to raise capital.
• SCP: market structure → firm conduct → performance (prices/profits).
• Lerner index measures overcharging; the four proxies are imperfect stand-ins for missing MC
data.
• Accounting is a decision tool and a referee between conflicting users.
• Double-entry balances because owned = owed + owners'.
• NPV discounts future cash because of inflation + opportunity cost; positive NPV = beats the cost of
capital.
• Payback rewards getting your money back fast = less risk exposure.
• Risk = future maybe (mitigate); Issue = present certainty (resolve).
• A contract = agreement + enforceability; the 10 elements each remove a way a deal could be
unfair or unworkable.

Engineering Management (ENGE5201) — Explained Notes | Page 21 of 22

FORMULA SHEET

Formula Meaning

PV = FV / (1 + r)ⁿ Discount future money to today

NPV = Σ PV(inflows) − Σ PV(outflows) Positive = worth doing

Payback = Investment / Avg net cash flow Lower = better (less risk)

Lerner Index = (P − MC) / P Degree of market power

Excess return on sales = (TR − TC)/TR Proxy for Lerner

Return on equity = (Π − T)/E Profit-rate proxy

Return on assets = (Π − T + I)/A Fixes debt/equity distortion

Price-cost margin = (TR − VC)/TR Plant-level performance proxy

Tobin's q = Market value / Replacement cost q > 1 ⇒ excess profits

Assets = Liabilities + Net Assets The book-keeping equation

Explained and compiled from the ENGE5201 course notes (Dr Mekam / Engr Wetka T., NAHPI,
University of Bamenda).

Engineering Management (ENGE5201) — Explained Notes | Page 22 of 22