Sourcing Discipline: RFQs, Contracts, T&Cs, and Vendor Scorecards

🎯 Who this is for: Buyers, contract administrators, and procurement managers who decide who to buy from and on what terms — the people for whom a disciplined RFQ, a well-structured contract, and an honest vendor scorecard are the difference between defensible sourcing and "I picked whoever answered the phone."

Series: Part 8 of 10 — MAS 9 Supply-Chain Playbook | Read time: 28 minutes

🎯 Where Discipline Pays for Itself

Sourcing is the moment a buyer answers the question the whole purchasing process exists to answer: who supplies this, and on what terms? Do it by reflex — call the vendor you always call — and you leave money on the table and an audit question you cannot answer. Do it with discipline and 3-bid RFQs save five to fifteen percent on non-contract spend, contracts lock negotiated prices so nobody re-negotiates per PO, and a scorecard turns "they feel unreliable" into "they were 82% on-time in Q3, and the contract says 95%."

This part is the four instruments of disciplined sourcing in MAS 9: the RFQ done without the pain that made buyers skip it, contract-based purchasing across the nine contract types, the terms-and-conditions library that legal pre-approves once, and vendor scorecarding that feeds every downstream reorder decision. None of it needs custom code.

<aside>
💡 Key insight: Sourcing discipline is not bureaucracy — it is leverage plus defensibility. Every RFQ is negotiating leverage and an audit answer; every contract is a price you don't have to fight for again; every scorecard number is a fact you can put in front of a vendor. Skip the discipline and you trade all three for the illusion of speed.
</aside>

📨 The RFQ Lifecycle

A Request for Quotation gets competitive bids from two to five vendors for a high-value or non-contract buy. Buyers skipped RFQs in 7.6 because they were painful; MAS 9's flow, once templated, is faster than the phone call it replaces.

The happy path

  1. On an approved PR → action menu → Create RFQ. Lines and the vendor list carry over; add more vendors from the Company master, filtered by commodity code.
  2. On the header, set Reply Due Date, Terms, Delivery Date Required, FOB, and attach the spec doc.
  3. Status → INPRG → SENT. Sending fires the RFQ_SEND Comm Template, which emails each vendor's contact with a BIRT-generated RFQ PDF — that vendor's lines and contact, prices blank.
  4. As vendors reply, enter their prices on each RFQ Vendor and RFQ Line sub-tab; attach each reply PDF.
  5. When replies are in (or the reply-due-date passes), status → AWARD.
  6. Award per line or whole-RFQ: set Award Status = AWARD on the winning vendor's lines.
  7. Action menu → Create PO from Award. The PO inherits the awarded vendor and prices; the RFQ auto-closes when all lines are awarded.

A worked award

A buyer has an approved $18,000 PR for a replacement gearbox — non-contract, above the $5,000 RFQ threshold. They Create RFQ from the mechanical template, which pre-loads three approved gearbox vendors and a five-business-day reply window, and send. Two vendors reply: $17,200 and $18,900; the third is silent. The buyer enters both quotes on the RFQ Vendor tabs, attaches the reply PDFs, sets the reply date as passed, and awards the line to the $17,200 vendor. Create PO from Award produces a PO at $17,200 with the award summary attached as sourcing evidence. The org saved $1,700 against the requisition estimate and now has a report-generated answer to "why this vendor" — and the silent third vendor's non-response is logged against its RFQ-responsiveness score.

When to require an RFQ

Enforce a policy so buyers cannot skip it on high-value spend:

TriggerRFQ?BidsExtra
Contract PR (any $)No—Contract price applies
Non-contract < $5,000No—Buyer judgment
Non-contract $5k–$24,999Yes3Award summary attached
Non-contract $25k–$99,999Yes3+ Procurement manager review
Non-contract ≥ $100,000Yes3++ CFO sign-off + legal T&C review
Emergency (priority 1)Waiver—Post-facto justification
Sole sourceWaiver—Signed sole-source form

Enforce it in the workflow: a PR cannot transition WAPPR → APPR at these thresholds without an RFQ reference or an explicit waiver code.

🗂️ Template-Driven RFQ

The single biggest RFQ time saver is refusing to build each one from scratch. Admins define RFQ templates per commodity — mechanical, electrical, janitorial, IT, rentals — each pre-loading:

  • A terms-and-conditions reference (from the library below).
  • Standard delivery terms and a default reply period (say, five business days).
  • A default vendor list of the top three-to-five approved vendors for that commodity.
  • The default BIRT report format.

The buyer runs Create RFQ from Template, picks the template, adjusts, and sends — fifteen minutes instead of two hours. This is what turns "RFQs are painful, I'll just call Bob" into "RFQ is faster than calling Bob."

<aside>
💡 Key insight: The RFQ template is to sourcing what the Start Center is to the desk — a pre-loaded default that removes the setup tax. A buyer who has to build an RFQ from nothing will skip it under pressure; a buyer who picks a commodity template and hits send will run 3-bid discipline as the path of least resistance.
</aside>

📇 Vendor Reply Tracking

An RFQ that vendors ignore is worthless, so track the replies. Comm Templates can nudge a vendor 48 hours before the reply-due-date, alert the buyer's inbox when a reply date passes with no response, and record reply metrics per vendor — on time, late, no reply. Those metrics feed the scorecard below. The most common way an RFQ fails silently is a missing vendor contact email, which is why vendor-master cleanliness (keeping contact emails current) is a prerequisite, not a nicety. And never send RFQs from a personal email — use the Comm Template so the audit trail stays Maximo-side.

📜 Contract-Based Purchasing: The Nine Types

A contract locks vendor, items, prices, and terms so releases against it inherit the negotiated price automatically. MAS 9 supports nine contract types plus a Master umbrella — pick the narrowest fit:

Contract typeUse when
PurchaseSpecific negotiated prices for agreed-rate material buys
Blanket (Volume)A total-dollar ceiling; release POs draw down against it
PricingCatalog pricing without a volume commitment
LaborCraft/skill rates; auto-generates invoices for approved contract labor
LeaseFixed-term equipment lease with a buy-out clause
RentalEquipment rental terminated at will
ServiceService delivery terms with per-incident billing
WarrantyWarranty coverage for purchased assets/parts + claim rules
SoftwareLicensing + maintenance + renewal dates + user counts
MasterAn umbrella for a vendor; sub-contracts of any type cite it

Creating and referencing a contract

Build a contract in the Contract app: set Type, Vendor, and dates; set properties (terms, auto-renew, currency); pull T&Cs from the library; add lines (items, prices); set Authorizing Sites; attach the signed PDF and insurance cert; route for approval. Once APPR, it is active for release. A PR that references it auto-populates contractrefnum, pulls price and vendor from the contract (which you cannot edit without breaking the link), and increments the contract's usage counters on PO receipt.

🔗 Blanket Contract → Release PO

The blanket contract is where contract discipline meets daily buying. It sets a total-dollar ceiling and effective dates; release POs draw down against it:

Blanket Contract ($500,000 ceiling, 2026-01-01 → 2026-12-31)
    └─ "Create Release PO" (any time in the window)
          ├─ pulls the contract price (validated against PO unit cost)
          ├─ decrements the remaining ceiling on each release
          └─ closes when the ceiling is exhausted or the end date passes

The buyer stops re-negotiating and re-approving each order; they release against a pre-approved agreement, and the ceiling and end date do the governance. This is why a contract PR needs only buyer approval (Part 7) — the spend was approved when the contract was.

♻️ Contract Lifecycle Hygiene

Contracts rot quietly. The disciplines that keep them healthy:

  • Expiring in 90 days. The Tier 0 query (Part 6) surfaces upcoming renewals weekly so nothing lapses unnoticed.
  • Auto-renew with notice. For evergreen contracts, set auto-renew and a workflow alert 60 days pre-renewal so the buyer can opt out or renegotiate.
  • Usage tracking. Watch the contract line's remaining amount; near exhaustion, decide to renew, increase, or let expire.

Two behaviors to respect: editing an approved contract requires a revision, not a direct edit (the same controlled-change principle as PO revisions); and a contract approved for Site A cannot be released from Site B unless Site B is on the Authorizing Sites tab — a frequent surprise for buyers migrating from single-site configs.

<aside>
⚠️ Watch out: Price escalation clauses do not apply themselves. If a contract says "3% increase on July 1," MAS 9 will not update the price automatically — you build a revision workflow or a scheduled automation script. A contract running eighteen months on a stale price is how auto-reorder quietly buys at yesterday's rate.
</aside>

📚 The Terms & Conditions Library

Retyping legal language on every PO is slow and risky. The Terms and Conditions app holds a reusable library — payment terms, warranty clauses, liability caps, insurance requirements, delivery terms, confidentiality — organized by category. Legal reviews and approves each clause once; buyers add them to a PR, PO, RFQ, or Contract by reference; the BIRT PO output formats and prints the referenced clauses.

The result: legal pre-approves once, buyers stop re-inventing, language is consistent across vendors, and the printed PO reads professionally. Give the library a single named legal owner who signs changes — without an owner it drifts — and capture any vendor pushback on a clause as a flagged variance, not a silent edit.

📊 Vendor Performance Scorecarding

A scorecard turns supplier performance from anecdote into data. In MAS 9 it is a monthly BIRT report pulling from MATRECTRANS, PO, Invoice, and RFQ, scoring each vendor on seven metrics:

MetricFormula (source)Target
On-Time Delivery% receipts where receiptdate <= requireddate (MATRECTRANS + PO)≥ 95%
Quantity Accuracy% receipts where received = ordered ± tolerance (MATRECTRANS)≥ 98%
Quality (Reject Rate)SUM(rejectqty)/SUM(receivedqty) (MATRECTRANS)≤ 2%
Price Accuracy% lines where invoice price = PO price (INVOICETRANS)≥ 99%
Invoice Accuracy% invoices matched first-pass (INVOICE)≥ 95%
RFQ Responsiveness% RFQs replied before due date (RFQ, RFQLINE)≥ 80%
Lead Time Adherenceactual vs contracted lead time (PO, MATRECTRANS)within ±10%

Schedule the report for the first of the month, emailed to the procurement manager and buyers. Review red and yellow vendors in the monthly ops review; trigger probation or rebid workflows when a vendor drops below threshold for two consecutive months.

How the scorecard feeds reorder confidence

The scorecard is not only a vendor conversation — it is an input to the auto-reorder pipeline (Part 9). An underperforming vendor per the scorecard should cause auto-reorder to skip or downgrade to manual for that vendor. That is how sourcing discipline and replenishment automation reinforce each other: the scorecard the buyer runs monthly becomes a safeguard the pipeline honors nightly.

Two caveats keep scorecards fair: exclude new vendors (under three months of data) and aggregate low-volume vendors (under five POs a year) across quarters, because their monthly metrics are too noisy to act on.

⚠️ Sourcing Edge Cases

A few realities that bite:

  • Split award. When lines go to different vendors, award at the line item, not the whole RFQ — MAS 9 supports split award; use it.
  • RFQ attachment to PO. Confirm your config carries the RFQ PDF and award summary to the resulting PO's attachments — that is the sourcing evidence auditors look for on a high-value PO.
  • Contract vs Master. Master contracts don't carry priced lines; they set T&Cs. For pricing, use Blanket or Pricing — don't confuse the two.
  • Integration-sourced vendors. If vendors are pushed from an ERP, do not merge or disable them Maximo-side without the ERP side agreeing, or the next integration run recreates them.

🔧 Troubleshooting Sourcing

SymptomCauseFix
RFQ sent but vendor never repliedMissing/wrong vendor contact emailFix vendor contact in Company master
Can't edit an approved contractApproved contracts change via revisionUse the revision workflow
Contract price didn't rise on renewalEscalation clause not automatedBuild a revision workflow / script
Site can't release against a contractSite not on Authorizing Sites tabAdd the site
Scorecard flags a new vendor as failingToo little dataExclude vendors under 3 months
Award produced one PO for split linesAwarded whole-RFQ, not per lineAward at the line item level

🎓 The Commandments of Sourcing

  1. Thou shalt run 3-bid RFQs on non-contract spend, and enforce it in workflow.
  2. Thou shalt template RFQs by commodity so discipline is the easy path.
  3. Thou shalt buy on contract wherever you can — negotiated once, released many times.
  4. Thou shalt revise, not edit, approved contracts, and watch escalation clauses.
  5. Thou shalt reference a legal-approved T&C library, never retype clauses.
  6. Thou shalt scorecard vendors monthly, and let the scores guard auto-reorder.

Key Takeaways

  • 3-bid RFQ discipline saves 5–15% on non-contract spend and produces the audit answer to "why this vendor" — templated by commodity, it is faster than a phone call.
  • Contract-based purchasing across nine types locks negotiated prices; blanket releases draw down a ceiling and need only buyer approval.
  • Contracts change through revisions, respect Authorizing Sites, and won't auto-apply escalation clauses — build those explicitly.
  • A legal-approved terms-and-conditions library is referenced once and printed on every PO, with a single named owner.
  • The seven-metric vendor scorecard turns performance into data and feeds reorder confidence by flagging vendors the pipeline should skip.

References

Series Navigation

Previous:Part 7 — PR to PO & Approvals
Next:Part 9 — Expedite & Match-Pay

About TheMaximoGuys: We help Maximo developers and teams navigate the move to MAS 9 with practical, no-hype guidance grounded in how the platform actually behaves.

Published by TheMaximoGuys | July 2026