← Back to list
Project & Org Management
#조달관리#계약 유형#Make-or-Buy#고정가#원가정산
Last updated · 2026-11-15

Project Procurement Management and Contract Types

1. Overview

A. Definition

Project Procurement Management is the knowledge area that plans, conducts and controls the purchasing and contracting activities required to acquire products, services and results from outside the organization, converting requirements into contract documents and selecting and managing suppliers so that the project objectives and procurement performance stay aligned. The PMBOK treats it as the flow of plan procurement, conduct procurement and control procurement, whose core deliverable is the contract.

What fundamentally distinguishes procurement management from other knowledge areas is that its object of management is not 'internal resources' but 'external parties bound by law'. Internal work is controlled through direction and coordination, but an external supplier can only be controlled through the document called a contract. The quality of procurement management therefore converges on 'how well the contract was designed'. If requirements are ambiguous the contract becomes ambiguous, and an ambiguous contract comes back as disputes, additional cost and schedule delay. In other words, procurement is not a simple act of purchasing but a strategic act of design that decides to whom, and how, risk is allocated.

The choice of contract type in particular is the heart of procurement management. For the very same work, whether it is signed as fixed price or cost reimbursable determines whether responsibility for a cost overrun falls on the supplier or returns to the buyer. From a professional engineer's perspective, understanding procurement management means being able to explain 'in which situations which contract type allocates risk most reasonably'.

B. Background and Necessity

In the past IT projects were centered on in-house development, but as technology specialized and divided, the outsourcing / SI (System Integration) model — entrusting areas outside core competencies to external specialist suppliers — became widespread. The spread of cloud, SaaS, open source and commercial packages made the question "make or buy" a premise of every project, and with it grew the need to systematically manage external acquisition activities through procurement management.

Public informatization projects in particular are governed by laws and institutions such as the National Contract Act and the Software Promotion Act, and complex constraints — separate ordering, software cost estimation, subcontracting fairness — are reflected directly in the contract. In a reality where a single payment method can decide a project's success or failure, it is dangerous to see procurement management merely as 'administrative procedure'. Buyers suffer from scope changes and cost disputes caused by unclear requirements, and suppliers fall into loss-making operation after winning a bid at a low price — a vicious cycle that has repeated itself. Procurement management demands 'explicit risk allocation' and 'performance-based control' to break this cycle.

C. The Three Core Axes of Procurement Management

Procurement management consists of three axes: ① plan procurement (make-or-buy), which decides what to procure externally; ② conduct procurement (bidding, negotiation, award), which selects a supplier and concludes a contract; and ③ control procurement, which supervises contract performance and handles change, dispute and closure. From the principle-based view of the PMBOK 7th edition, procurement extends beyond a 'management activity' into the realm of stakeholder and systems thinking that integrates the supplier as a partner in project value creation. These three axes are sequential yet form a feedback loop. A requirement change discovered during control leads to a contract change (change order), which in turn affects payment and schedule. The structure diagram below shows this overall flow and the key deliverable of each stage.

flowchart TD
  subgraph PLAN["Plan"]
    MOB["Make-or-Buy analysis"]
    SOW["Statement of Work (SOW)"]
    CTYPE["Contract type selection"]
  end
  subgraph CONDUCT["Conduct"]
    BID["Bid documents (RFP/IFB)"]
    EVAL["Proposal evaluation / supplier selection"]
    AWARD["Contract award"]
  end
  subgraph CONTROL["Control"]
    PERF["Performance supervision / acceptance"]
    CHG["Change order"]
    CLOSE["Contract closure"]
  end
  MOB --> SOW --> CTYPE --> BID
  BID --> EVAL --> AWARD --> PERF
  PERF --> CHG --> PERF
  PERF --> CLOSE

2. Procurement Planning and Key Deliverables

A. Make-or-Buy Analysis

The starting point of procurement is the decision "shall we do this work ourselves, or buy it from outside". This is a strategic judgment that goes beyond a simple cost comparison to consider the protection of core competency, control over risk and long-term maintenance cost. For example, a financial firm internalizes the transaction engine of its core banking system for control and security, while buying a specialist SaaS for a chatbot or marketing analytics — a mixed strategy.

Break-even analysis serves as the quantitative criterion of the decision. If, say, developing a certain function internally costs a fixed 200 million won with almost no variable cost per transaction, while an external SaaS costs 5 million won a month (60 million won a year), then using it for about 3.3 years or more makes internalization advantageous. Yet the decision is not made by numbers alone. In a fast-changing technology area, internalization can instead degenerate into technical debt, so a buy is chosen for the sake of flexibility.

B. The SOW and Turning Requirements into a Contract

In procurement, requirements are converted into a contract document through the Statement of Work (SOW). The more detailed the SOW, the more a fixed-price contract becomes possible; the more ambiguous it is, the more the contract inevitably leans toward cost-reimbursable or time-and-materials. In other words, the clarity level of the requirements virtually determines the choice of contract type. In public software projects, most scope-change disputes originate in the ambiguity of the SOW (request for proposal, scope statement), which is why a scope deliberation committee is now institutionalized to fix the scope of work explicitly.

C. Bidding Methods and Supplier Selection

Supplier selection varies by the character of the bid document. The representatives are the IFB (Invitation for Bid, lowest price), which competes on price alone; the RFP (Request for Proposal, contract by negotiation), which evaluates technology and price together; and the RFI (Request for Information), used to gather information in advance. Public software projects operate a negotiated contract (RFP) with a higher weight on technical evaluation and a price-ceiling system to prevent the harm of low-price bidding. Selection criteria reflect technical suitability, track record, price, financial soundness and security level as weights.

The selection method and the contract type must be consistent with each other. If requirements are unclear yet selection is by lowest price (IFB), a structure in which a supplier who won at a low price raises disputes on the pretext of scope change is almost inevitable. Conversely, if a clear repetitive task is selected through a complex technical negotiation (RFP), only unnecessary procurement cost increases. That is, 'bidding method → contract type → risk allocation' must be a single consistent design, and if the three fall out of step the whole procurement falters.

3. Classification and Characteristics of Contract Types

Contract types are broadly divided into the three categories of fixed price (FP), cost reimbursable (CR) and time and materials (T&M), and within each category they are subdivided according to incentive and adjustment clauses. The key distinguishing point is who bears the cost risk. The classification diagram below shows the three categories, the subtypes, and the shift of the party bearing the risk together.

flowchart LR
  ROOT["Contract Type"]
  ROOT --> FP["Fixed Price (FP)"]
  ROOT --> CR["Cost Reimbursable (CR)"]
  ROOT --> TM["Time and Materials (T&M)"]
  FP --> FFP["Firm Fixed Price (FFP)"]
  FP --> FPIF["Fixed Price Incentive Fee (FPIF)"]
  FP --> FPEPA["Fixed Price with EPA (FP-EPA)"]
  CR --> CPFF["Cost Plus Fixed Fee (CPFF)"]
  CR --> CPIF["Cost Plus Incentive Fee (CPIF)"]
  CR --> CPAF["Cost Plus Award Fee (CPAF)"]
  FFP -.->|"supplier risk maximal"| RISK["Risk-bearing axis"]
  CPFF -.->|"buyer risk maximal"| RISK
  TM -.->|"middle / hybrid"| RISK

A. Fixed Price (FP) — the supplier bears the risk

A fixed-price contract fixes the total amount in advance and has the supplier deliver the output for that amount. Firm Fixed Price (FFP) is the simplest and most widely used; whatever the actual cost turns out to be, the supplier is responsible. The cost-overrun risk therefore lies entirely with the supplier, and the buyer gains the great benefit of budget predictability. The precondition is that requirements are clear and change little. If requirements are unclear yet a contract is signed as FFP, the supplier either adds a risk premium to the price or, after winning, demands additional cost on the pretext of scope change, and the dispute grows.

There are variants that add flexibility to fixed price. Fixed Price Incentive Fee (FPIF) sets a target cost, target profit, share ratio and ceiling price, and lets the supplier share the saving with the buyer when it reduces cost, thereby providing an incentive to cut cost. For example, in a contract with target cost 10 billion, target profit 1 billion, share ratio 80:20 (buyer:supplier) and ceiling price 12 billion, if the supplier completes at 9 billion it takes 200 million of the 1-billion saving as additional profit. Fixed Price with Economic Price Adjustment (FP-EPA) places, in a multi-year contract, a clause that adjusts for raw-material, exchange-rate and price movements indexed to an indicator, easing the inflation risk of a long-term contract.

B. Cost Reimbursable (CR) — the buyer bears the risk

A cost-reimbursable contract has the buyer reimburse the actual cost incurred and pay a fee on top. Because the cost-overrun risk lies with the buyer, it suits innovative projects where requirements are unclear or results are hard to predict, such as research and development. Cost Plus Fixed Fee (CPFF) adds a fixed-amount fee to the cost, but because the fee is fixed it has the weakness that the supplier has a weak incentive to reduce cost — even if the cost grows, the supplier suffers no loss.

The incentive forms complement this weakness. Cost Plus Incentive Fee (CPIF) adds or subtracts the fee according to the saving or overrun against the target cost, giving an incentive to save; Cost Plus Award Fee (CPAF) has the buyer subjectively evaluate qualitative performance such as quality and schedule to determine the fee. The formerly used Cost Plus Percentage of Cost (CPPC) had the paradoxical structure of a larger fee for a larger cost, encouraging cost inflation, and is now mostly prohibited. This prohibition shows the core lesson of procurement management: 'if the incentive is designed wrongly, the contract induces exactly the opposite behavior'.

C. Time and Materials (T&M) — the risk is shared

A time-and-materials contract settles on the basis of the hourly rate of the labor input and the actual cost of materials, a hybrid form. It suits small-scale or urgent work whose scope is not fixed, staff augmentation, and iterative development in an agile manner. Because the scope is open and the buyer's risk is large, in practice a Not-to-Exceed (NTE) ceiling and a cap on the labor input are placed together to prevent cost runaway. In agile SI, 'sprint-based T&M + backlog priority adjustment' is a typical use.

The reason T&M sits between fixed price and cost reimbursable is that it fixes the rate but leaves the quantity (input hours) open. Because the rate is fixed, the supplier has a weak incentive to raise efficiency; because the quantity is open, the buyer must continuously monitor the appropriateness of the effort estimate. The success of T&M therefore rests on transparent management of the input effort, and making daily work logs, burndown and weekly burn-rate reporting a contractual obligation is the key to preventing disputes. For example, in a contract with a ceiling of 1 billion and an input cap of 20 man-months, tracking the weekly burn rate lets the scope be renegotiated early if, in week 12, 70% of the budget is consumed while progress stays at 50%.

4. Comparison of Contract Types and the Principle of Risk Allocation

The choice among the three types is ultimately a function of the clarity of requirements and the intent of risk allocation. The clearer the requirements, the more the choice moves to fixed price; the less clear, the more to cost reimbursable. What matters is that 'risk does not disappear, it only shifts'. If the buyer passes the risk to the supplier through fixed price, the supplier passes that risk on as price (a risk premium) or, when it cannot bear it, returns it as degraded quality and dispute. The common belief that 'fixed price is always advantageous' is therefore wrong. If fixed price is forced where uncertainty is high, the worst combination results — paying only the risk premium and bearing the dispute as well.

Category Firm Fixed Price (FFP) Cost Plus Fixed Fee (CPFF) Time and Materials (T&M)
Cost risk borne by Supplier maximal Buyer maximal Shared (limited by ceiling)
Suitable situation Requirements clear, little change Requirements unclear, R&D, innovation Scope undetermined, urgent, agile
Buyer budget predictability High Low Medium
Supplier cost-saving incentive Very high Low Low
Management burden (audit/acceptance) Low High (cost evidence required) Medium

The 'management burden' column of this table is a frequently overlooked trade-off. A cost-reimbursable contract obliges the buyer to verify and audit the appropriateness of every cost, so the administrative cost is large. Conversely, fixed price only requires acceptance of the output, so management is simple. That is, the choice of contract type is a decision that weighs 'risk' and 'management cost' at the same time.

5. Application Cases

In a public next-generation system project, requirements change greatly and the period is long, so binding the whole as FFP causes scope-change disputes to explode. For this reason a staged, separated contract is recommended — the analysis and design stages, acknowledging that scope is fluid, as a flexible contract, and the implementation stage, based on a confirmed design, as FFP. In fact, a large share of large public-project failures originated in forcing unclear requirements into FFP.

Defense weapon-system acquisition is the typical arena of incentive-type cost reimbursement such as CPIF and CPAF. Because new development is hard to estimate, cost is reimbursed, but the fee is added or subtracted according to achievement of performance and schedule targets to induce the supplier's performance. Meanwhile, in global IT outsourcing, a portfolio strategy is common that runs repetitive and predictable work such as operation and maintenance under an SLA-linked fixed price, and new development under T&M or a performance-based contract.

The common lesson these cases tell is that one does not insist on a single contract type for one project. Even in the same project, uncertainty differs by work package (WBS element), so the confirmed parts are bound under fixed price to control the budget while the uncertain parts are buffered with a flexible contract. In other words, mature procurement management is the work of designing a 'portfolio of contract types', and this is tightly interlocked with EVM, risk management and scope management.

6. Deep Dive: Latest Trends — Performance-Based Contracts, Agile and Cloud Procurement

Whereas traditional contracts were based on 'input' or 'output', performance-based contracts (PBC) have recently spread. A PBC takes as its contractual basis not 'what to make and how' but 'what performance or outcome to achieve'. For example, it places SLAs such as system availability of 99.9% and fault recovery within 30 minutes at the body of the contract and adds or subtracts the price according to the degree of achievement. This is a paradigm shift in which the buyer purchases the 'result', not the 'method', and it raises the supplier's autonomy and responsibility at once.

Agile procurement is in tension with traditional contract theory. Agile presumes the progressive elaboration of requirements, whereas FFP must fix the scope at the outset. To resolve this contradiction, contracts of fixed budget, flexible scope, sprint-based T&M, and methods that adjust scope by backlog priority while controlling the total budget have appeared. In domestic public projects too, contract and cost-estimation guides for applying agile to software projects are being discussed.

Cloud procurement has changed the payment structure itself from asset purchase (CapEx) to usage-based subscription (OpEx). The choice of a charging model — pay-as-you-go, reserved instances, savings plans — becomes the procurement strategy itself, and in a multi-cloud environment an exit clause to avoid vendor lock-in and the conditions of data migration have emerged as key issues of the contract. Around 2024, as cloud-transition cost and data sovereignty became major agendas of public procurement, the trend of specifying in the contract the obligation to prove data return and deletion has strengthened.

7. Considerations and Implications (Professional Engineer's View)

  • Application strategy — match the contract type to requirement maturity: The contract type should be chosen not by the organization's preference but by 'how far the requirements are confirmed'. Forcing FFP on an early stage of high uncertainty means bearing the risk premium and the dispute at the same time. A separated, staged contract that varies the contract type by stage is the realistic solution.
  • Trade-off — risk transfer and management cost are exchanged: The more risk is passed to the supplier through fixed price, the simpler management becomes but the more a risk premium is loaded onto the price; securing flexibility through cost reimbursement increases the burden of cost verification and audit. A view that optimizes 'risk allocation' and 'management cost' together is needed.
  • Outlook — a move toward outcome-based: The axis of procurement is shifting from input/output criteria to performance (SLA, business value) criteria. In the AI and cloud era, 'what outcome was produced' rather than 'what was made' becomes the basis of pricing, so building an objective measurement system for performance indicators becomes the core of procurement capability.
  • Institution and fairness — improving low-price bidding and the subcontracting structure: In public procurement, a low-price award breeds a vicious cycle of quality degradation and supplier loss. Appropriate cost estimation (the software cost standard), a price-ceiling system, subcontracting fairness, and scope confirmation through a scope deliberation committee are the premise of a healthy procurement ecosystem.
  • Related technology — integration with governance, security and supply chain: Procurement management does not stop at contract management but connects to supply-chain security (SBOM, third-party risk management), data sovereignty, and ESG / supply-chain due diligence. As external procurement grows, a supplier's security level and sustainability translate directly into project risk, so security and governance requirements must be internalized into the contract from the procurement stage.

References


In one line: Project procurement management is the activity of controlling external acquisition through contracts, and its core is to choose the fixed-price (FP), cost-reimbursable (CR) or time-and-materials (T&M) contract type according to requirement clarity so as to allocate cost risk reasonably; recently the axis has moved toward performance-based (PBC), agile and cloud procurement.