Its PROJECT ENGINEERED capability state, PROJECT-SPECIFIC evidence state and Blower / Process-Air Engineer review boundary remain untouched.
A performance guarantee is only as strong as its defined duty, measurement boundary and acceptance method
It protects the accepted duty, performance evidence, interfaces, documentation, commissioning obligations and acceptance criteria from being diluted between award and final handover.
This page addresses technical contract governance rather than legal advice. Commercial and legal terms require the buyer's authorised contractual review; technical clauses require project-specific engineering verification.
1 — Freeze the Accepted Technical Basis
Preserve the final specification, data sheet, accepted bid, deviations and clarifications as the contract technical baseline.
2 — Contract Technical Attachment
Use one controlled attachment or referenced document set that clearly identifies the accepted technical scope.
3 — Requirements Traceability
Map each critical requirement from specification to supplier response, final contract, submittal and acceptance test.
4 — No Post-Award Scope Drift
A requirement accepted during evaluation should not disappear through later informal correspondence.
5 — Battery Limits
Freeze physical and functional boundaries for air, power, cooling, drainage, controls, network and civil interfaces.
6 — Owner-Supplied Scope
List owner responsibilities explicitly so supplier performance assumptions remain valid.
7 — Supplier-Supplied Scope
List package, accessories, controls, documents, spares, commissioning and training obligations.
8 — Contractor Scope
Where installation is separate, define piping, electrical, civil, ventilation, rigging and commissioning interfaces.
9 — Exclusions
Preserve accepted exclusions and evaluate any new exclusion as a controlled change.
10 — Deviation Register
Carry all accepted deviations into the contract baseline rather than relying on bid-stage memory.
11 — Clarification Register
Preserve material clarifications that changed technical interpretation.
12 — Precedence of Documents
Contract/legal teams should define precedence; engineering should ensure conflicting technical documents are identified before execution.
13 — Duty Point
Freeze required airflow, pressure, reference conditions and site conditions.
14 — Load Profile
Preserve expected low/normal/peak/part-load operation where energy or controls depend on it.
15 — Air Quality
Freeze the required quality boundary and sampling/acceptance location.
16 — Reliability Requirement
Freeze N+1/standby/critical-load requirement in measurable terms.
17 — Environmental Conditions
Preserve ambient, altitude, dust/humidity or other relevant site conditions.
18 — Utilities
Freeze electrical, cooling-water, ventilation and drainage assumptions.
19 — Future Growth
Identify whether committed future duty is included in the contracted scope.
20 — Performance Guarantee Boundary
Define exactly what the supplier guarantees: package airflow, package power, dew point, pressure drop, controls or another measurable result.
21 — Guarantee Reference Conditions
State the agreed inlet/reference conditions and correction basis.
22 — Guarantee Pressure
State the discharge/operating pressure at which airflow/power performance applies.
23 — Included Auxiliaries
Define whether fans, pumps, dryers, heaters or other auxiliaries are inside the power boundary.
24 — Airflow Guarantee
Define measurement/reference basis and test method before equipment is manufactured.
25 — Power Guarantee
Define electrical measurement boundary, operating state and included auxiliaries.
26 — Specific-Power Guarantee
Only meaningful when airflow, power and pressure boundaries are aligned.
27 — Part-Load Guarantee
Where lifecycle economics depend on variable demand, define accepted performance points/range.
28 — Unloaded-Power Boundary
For fixed-speed packages, define unloaded test condition where material.
29 — VSD Turndown Boundary
Define stable supported range and test points without relying on a headline turndown ratio alone.
30 — Dryer Dew-Point Guarantee
Define inlet conditions, flow, pressure, sampling location and measurement method.
31 — Dryer Pressure-Drop Guarantee
Define flow and operating conditions for the differential-pressure test.
32 — Dryer Energy / Purge Boundary
Define what is measured/calculated for purge, heater, blower or vacuum regeneration.
33 — Filter Pressure Drop
Define clean/accepted condition and flow for comparison.
34 — Control Performance
Define pressure stability, staging/fallback or other measurable control outcomes where contractually required.
35 — Standby Performance
Define expected start/load/support response where standby capability is part of acceptance.
36 — Thermal Performance
Define room/package temperature evidence where supplier responsibility includes cooling/ventilation interfaces.
37 — Noise Performance
Where required, define measurement standard/boundary through project-specific specialist review.
38 — Heat-Recovery Performance
Define useful delivered thermal output and operating conditions if guaranteed.
39 — Metering Performance
Define required instrumentation functionality/data availability where supplied.
40 — Availability Guarantee Caution
Availability requires precise definitions of service boundary, planned downtime, exclusions and data period; do not use undefined percentages.
41 — Warranty Is Not Performance Guarantee
Warranty addresses defined defects/terms; a performance guarantee addresses agreed measured outcomes.
42 — Performance Guarantee Is Not System Guarantee by Default
A package supplier cannot automatically guarantee owner piping, production demand or utilities outside its battery limits.
43 — System Guarantee Requires Integrated Boundary
Where one party guarantees system performance, interfaces and owner conditions must be explicit.
44 — Measurement Method
Specify instrument type/class/range and test method appropriate to the acceptance requirement.
45 — Measurement Uncertainty
Acceptance should recognise test uncertainty rather than pretend measurements are exact.
46 — Instrument Verification
Confirm acceptance instruments are suitable and appropriately verified/calibrated under project requirements.
47 — Data Synchronisation
Align airflow, power, pressure, temperature and machine-state data.
48 — Stabilisation Period
Define stable test conditions where steady-state performance is being evaluated.
49 — Test Duration
Choose duration appropriate to the performance question rather than one universal interval.
50 — Test Repetition
Where results are near a limit or variable, repeat/extend testing according to agreed methodology.
51 — Correction to Reference Conditions
Use the agreed supported correction method when site conditions differ from reference.
52 — Raw Test Data
Preserve original test data and instrument records unchanged.
53 — Calculation File
Version all corrections, averaging, unit conversions and derived KPIs.
54 — Witness Points
Define tests requiring buyer, consultant, supplier or specialist witness.
55 — Hold Points
Define project stages that cannot proceed until specified evidence/review is complete.
56 — FAT Boundary
Factory tests can prove package/control functions but not the complete site system.
57 — FAT Procedure
Agree test setup, duty, instruments, acceptance criteria, data and witness requirements before testing.
58 — FAT Deviation
Record any inability to test the specified condition and how site verification will close the gap.
59 — FAT Failure
Preserve failed results, cause/correction and retest rather than replacing them with only the final pass.
60 — FAT Release
Shipment approval should consider unresolved technical items and preservation/logistics readiness.
61 — Site Acceptance Boundary
SAT tests the installed equipment through actual owner/project interfaces.
62 — SAT Preconditions
Mechanical/electrical/pressure-system completion, utilities, instruments, controls and safe readiness should be established.
63 — Site Capacity Test
Verify delivered airflow at agreed pressure/reference conditions where required.
64 — Site Power Test
Verify electrical input on the agreed boundary.
65 — Site Part-Load Test
Use representative demand or controlled points where required by the contract.
66 — Site Dryer Test
Verify quality, pressure drop and energy/purge boundary as specified.
67 — Site Pressure Test
Verify source/critical-user dynamic performance where system acceptance includes distribution.
68 — Site Controls Test
Verify sequencing, transitions, fallback and communication behaviour.
69 — Site Reliability Test
Verify standby/common-mode response within the contracted boundary.
70 — Site Thermal Test
Verify cooling/ventilation interface under representative active load.
72 — Production Conditions
Document production state during site testing so results remain interpretable.
73 — Owner Conditions
Record owner-supplied power, cooling, ventilation, pressure and demand conditions relevant to guarantee validity.
74 — Supplier Conditions
Record package settings/configuration and supplied-system state.
75 — Test Exception
If required conditions cannot be achieved, document the exception and agreed resolution rather than declaring an unsupported pass.
76 — Conditional Acceptance
Where governance permits, identify exactly what is accepted, what remains open and what interim controls apply.
78 — Corrective Action
Supplier/contractor/owner actions should be tied to the verified cause of the failed criterion.
79 — Retest
Repeat the affected test after correction under comparable agreed conditions.
80 — Repeated Failure
Escalate engineering/root-cause review rather than repeatedly adjusting acceptance criteria.
81 — Acceptance Criteria Change
Any change requires controlled technical and contractual approval; do not alter a criterion merely to create a pass.
82 — Punch List
Record incomplete/defective/unverified items with consequence, owner and closure evidence.
83 — Critical Punch Item
Items affecting safe operation, required performance, quality or reliability can prevent full technical acceptance.
84 — Minor Punch Item
Cosmetic/non-critical items can be tracked separately under project governance.
85 — Technical Completion
Define when technical requirements, tests, documents and critical punch items satisfy the agreed gate.
86 — Mechanical Completion
Distinguish installation completeness from performance acceptance.
87 — Commissioning Completion
Distinguish successful startup from complete acceptance testing.
88 — Handover Completion
Distinguish equipment operation from delivery of documents, training, backups, spares and final configuration.
89 — Warranty Start Boundary
Exact commencement belongs to contract terms and should be explicit.
90 — Performance-Test Window
Define when tests can occur relative to commissioning, production readiness and stabilisation.
91 — Defects / Warranty Period
Technical tracking should preserve faults, evidence and corrective actions during the applicable contractual period.
92 — Warranty Claim Evidence
Preserve operating conditions, service records, alarms, photos/logs and failed components where relevant.
93 — Service Compliance
Where warranty depends on maintenance, use current supplier requirements and controlled records.
94 — Approved Consumables
Use exact current supplier/equipment requirements where warranty or performance depends on them.
95 — Unauthorised Modification Risk
Undocumented control or mechanical changes can complicate warranty/performance attribution.
96 — Configuration Freeze
Preserve final accepted controller, VSD, sequencer and dryer settings.
97 — Software / Firmware Record
Preserve accepted versions where behaviour/support depends on them.
98 — Final Data Book
Compile approved supplier drawings, manuals, test evidence, certificates, settings and open/closed items.
99 — As-Built Reconciliation
Ensure field changes are reflected in final drawings and registers.
100 — Training Completion
Verify contracted operator/maintenance/controls training deliverables.
101 — Spares Completion
Verify contracted commissioning/critical/consumable spares have been handed over.
102 — Special Tools Completion
Verify contracted tools/software/adapters required for lifecycle support.
103 — Documentation Completion
Use a deliverable register rather than relying on a folder count.
104 — Missing Document
Track missing supplier data as an open technical item where it affects operation/maintenance.
105 — Document Revision
Ensure final documents correspond to delivered equipment, not earlier proposal models.
107 — Contract Change Request
Any technical scope change should identify requirement, reason, impact and approval.
108 — Variation Technical Review
Evaluate effect on duty, energy, reliability, safety, interfaces and acceptance.
109 — Substitution
Require evidence of technical equivalence and project approval before accepting alternate equipment/components.
110 — Value Engineering
Savings proposals should show what technical/lifecycle requirement changes, if any.
111 — Schedule-Driven Change
Do not silently weaken technical acceptance because of delivery pressure.
112 — Cost-Driven Change
Do not remove critical metering, controls, commissioning or documentation without evaluating lifecycle impact.
113 — Owner Change
Production or utility changes after award can alter guarantee conditions; record and re-evaluate.
114 — Supplier Change
Supplier design/configuration changes should be evaluated against accepted requirements.
115 — Interface Change
Piping, electrical, ventilation or controls changes can invalidate performance assumptions.
116 — Change Closure
Update contract technical baseline, drawings, tests and handover records after approved change.
117 — Technical Query Register
Preserve questions, responses, affected requirement and disposition.
118 — Decision Register
Record significant technical decisions and evidence basis.
119 — Assumption Register
Keep unresolved assumptions visible until verified or formally accepted.
120 — Risk Register
Track performance, integration, schedule, supplier-data and acceptance risks.
121 — Technical Contract Review Meeting
Use controlled reviews to resolve requirements, deviations, interfaces, evidence and acceptance planning before manufacture/installation.
122 — Interface Ownership
Assign named responsibility for each boundary so gaps do not become disputes during commissioning.
123 — Supplier Data Dependency
Track which owner design decisions depend on supplier drawings/data and required dates.
124 — Late Data Risk
Late dimensions, loads or control information can create field rework even when equipment delivery is on time.
125 — Approved-for-Construction Dependency
Do not construct critical interfaces from unapproved proposal data.
126 — Technical Compliance After Award
Recheck final supplier data against the accepted compliance matrix, not only the purchase order title.
127 — Guarantee Assumption Register
List assumptions that must remain true for a performance guarantee to be meaningful.
128 — Guarantee Exclusion Review
Technical teams should understand exclusions that can materially limit performance accountability.
129 — Test Readiness Review
Before FAT/SAT, confirm procedure, instruments, conditions, data sheets, witnesses and acceptance limits.
130 — Test Deviation Log
Record deviations from the agreed procedure and whether they invalidate or qualify the result.
131 — Data Ownership / Access
Ensure the buyer receives agreed test evidence and lifecycle data subject to contractual rights.
132 — Independent Verification
Where consequence/value justifies it, an independent reviewer can witness or validate methodology without changing contractual responsibility.
133 — Dispute Prevention Through Measurement
Clear boundaries and agreed tests reduce arguments about whether a shortfall belongs to equipment, utilities or system design.
134 — Performance Drift After Acceptance
Later deterioration belongs to maintenance/operation analysis unless evidence shows an unresolved original defect.
141 — Technical Contract KPI: Open Deviations
Track unresolved deviations that can affect design, commissioning or acceptance.
142 — Technical Contract KPI: Late Submittals
Track critical supplier data whose delay affects project interfaces.
143 — Technical Contract KPI: First-Pass Test Success
Useful for project learning when test conditions and definitions are consistent.
144 — Technical Contract KPI: Retest Closure
Track failed acceptance tests through cause, correction and verified retest.
145 — AI-Assisted Contract Technical Review
AI can compare clauses, bids and submittals or flag mismatches, but it must not invent guarantee language, performance data or legal interpretation.
146 — AI Traceability
Every AI-flagged technical conflict should point to exact controlled source documents/revisions for competent review.
147 — Confidentiality
Contract prices, supplier documents, customer data and proprietary information remain within approved controls.