Quick answer: A useful RTO RFQ describes the complete exhaust envelope, not only a nominal airflow. Include minimum, normal, maximum, and upset flow; inlet temperature; VOC species and concentration range; oxygen and moisture; particulate, aerosol, and condensables; production schedule; safety and bypass philosophy; utilities; site layout; controls interface; and acceptance requirements.
An RTO quotation can only be as useful as the process data behind it. “We have VOC exhaust and need an RTO” identifies the equipment family, but it does not tell an engineer how much gas must be treated, how hot it is, what organic compounds are present, how concentration changes, whether dust or mist is carried over, how the line starts and stops, or what the site expects during an upset. Those missing facts become assumptions, and assumptions make quotations hard to compare.
A strong RFQ does not need to be a perfect process design. It needs to separate known data from unknown data and make the operating envelope visible. Buyers can usually collect production schedule, connected sources, available airflow measurements, temperatures, material lists, utilities, space constraints, and permit requirements. Engineering can then identify where sampling, hazard review, or further design work is still required.
Rotary equipment gives buyers one architecture to consider during RFQ preparation.
Exhaust flow by operating case and the wider decision
Exhaust flow by operating case is a data field, not a marketing adjective. Nominal flow is only one point. The RTO also needs a credible minimum, peak, startup, shutdown, and any short upset flow that could affect fan capacity, residence time, pressure drop, heat balance, or safety logic. An RFQ becomes more useful when the buyer can attach a small operating-case table instead of one design airflow.
Inlet gas temperature is a data field, not a marketing adjective. Temperature influences heat balance, material selection, condensation risk, and upstream process integration. It may change by season, dryer setting, line speed, or which branches are operating. An RFQ becomes more useful when the buyer can report a range and identify where the measurement is taken.
VOC species is a data field, not a marketing adjective. Different compounds have different physical and combustion behavior and may interact differently with catalysts, materials, or pretreatment. Total VOC concentration without a compound list leaves important questions unanswered. An RFQ becomes more useful when the buyer can include representative material or solvent information and flag uncertain compounds for later sampling.
Bed RTO equipment provides the second major architecture reference.
VOC concentration range is a data field, not a marketing adjective. A monthly average can hide low-load operation and short peaks. The RTO control and heat balance should be reviewed against representative variability. An RFQ becomes more useful when the buyer can give minimum, normal, maximum, and credible short-duration peaks with the measurement or estimation basis.
Oxygen and moisture is a data field, not a marketing adjective. Oxygen belongs in both the oxidation and safety review, while moisture can affect gas properties, corrosion, condensation, and some treatment choices. An RFQ becomes more useful when the buyer can provide expected ranges when they differ materially from ordinary ambient air.
Particulate, aerosol, and condensables is a data field, not a marketing adjective. Dust, mist, sticky organics, salts, silicon-bearing material, corrosion products, or other non-VOC contaminants can foul media, ducts, catalysts, fans, and instruments. An RFQ becomes more useful when the buyer can describe the physical condition of the exhaust and any upstream filtration or separation.
Structural imagery helps buyers think about equipment boundaries, access, and internal sections.
Production schedule is a data field, not a marketing adjective. Continuous lines, batch plants, and short campaigns create different startup energy, turndown, maintenance, and heat-reuse patterns. An RFQ becomes more useful when the buyer can state shifts, weekly hours, planned shutdowns, job changes, cleaning cycles, and seasonal changes.
Safety and upset philosophy is a data field, not a marketing adjective. The RFQ should identify known combustible-gas monitoring, dilution, purge, bypass, emergency shutdown, area classification, and site-code requirements without inventing final setpoints. An RFQ becomes more useful when the buyer can provide the plant safety standards and define the credible upset cases for engineering review.
Utilities and site constraints is a data field, not a marketing adjective. Fuel type, electrical supply, compressed air, controls network, drainage where applicable, stack route, foundation, crane access, and available plot space can change the equipment scope. An RFQ becomes more useful when the buyer can include a site plan and utility summary early enough to influence the proposal.
Acceptance and documentation is a data field, not a marketing adjective. A quotation is easier to compare when it states what must be demonstrated, what documents are required, and which assumptions remain open. The final basis may include emission testing, operating ranges, drawings, manuals, training, and commissioning records. An RFQ becomes more useful when the buyer can separate contractual acceptance criteria from preliminary engineering estimates.
A five-stage RFQ workflow for procurement and engineering
1. Collect what the plant already knows
Gather process flow diagrams, exhaust fan data, production schedule, material lists, temperatures, permits, utility information, and site layout before asking vendors to fill the gaps.
2. Mark measured, calculated, and unknown values
Do not mix a recent instrument reading with a rough estimate without labeling them. Uncertainty is manageable when it is visible.
An application image reminds RFQ writers to describe the connected production process, not only the oxidizer.
3. Ask every bidder to use the same basis
Issue one controlled data sheet and require deviations or alternative assumptions to be stated explicitly. That prevents a low price from winning simply because it was based on an easier duty.
4. Resolve high-impact unknowns first
Prioritize sampling, airflow measurement, contaminant identification, or safety review where the uncertainty could change technology, size, pretreatment, fan duty, or operating cost.
5. Freeze the design basis before final comparison
Once major unknowns are resolved, update the RFQ so commercial and technical comparisons use the same operating envelope and project boundary.
Copyable RTO RFQ data checklist
Connected process sources and which sources can operate simultaneously.
Minimum, normal, maximum, startup, shutdown, and upset exhaust flow.
Inlet temperature range and measurement location.
VOC species, concentration range, and basis of the data.
Oxygen, humidity, particulate, aerosol, condensable, corrosive, and other relevant constituents.
Production schedule, turndown, line changes, cleaning cycles, and future expansion.
Required control objective, permit basis, and performance-test expectations.
Fuel, power, compressed air, controls interface, and other site utilities.
Available footprint, height limits, stack route, access, lifting, and foundation constraints.
Existing pretreatment, collection fans, ducts, dampers, and instrumentation.
Safety standards, combustible-gas monitoring, dilution, bypass, and shutdown philosophy.
Documentation, training, commissioning, spares, and maintenance-access requirements.
Media imagery reinforces the need to describe contaminants, pressure drop, and maintenance expectations.
Questions buyers commonly ask
What if some VOC data is unknown when the RFQ is issued?
Label it as unknown and ask what sampling or analysis is needed before final design. A clearly marked data gap is better than an invented value because every bidder can treat the uncertainty consistently.
Should buyers specify the exact RTO size themselves?
Usually the buyer should define the process duty and project constraints, then require the supplier to size and explain the proposed configuration. If the plant already has an engineering specification, include it, but keep assumptions and measured inputs traceable.
How can quotations be compared fairly?
Use one controlled process-data sheet, require each supplier to list deviations and exclusions, compare complete system boundaries, and normalize utilities, pretreatment, controls, stack, installation scope, testing, and maintenance access.
Which site pages should an RFQ reference?
Use the general RTO page for the core process, review bed and rotary RTO pages if architecture is still open, then use the contact page to send the process envelope and project constraints for engineering discussion.
Add a data-quality column to the RFQ
One simple improvement is to label every important input as measured, calculated, supplier data, operator estimate, or unknown. Add the date and operating condition when a measurement is available. This prevents a number copied from an old drawing from carrying the same authority as a recent field measurement. It also tells bidders where uncertainty is concentrated. If peak VOC concentration is an estimate while airflow has been measured carefully, the next engineering action is obvious. A data-quality column makes clarification meetings shorter, reduces silent assumptions, and gives the project team a clean record of which values were later updated. That traceability is especially useful when the final design basis must be reviewed months after the first budget quotation.
A practical next step
A better RFQ does not have to know every answer. It has to show which answers are known, which are estimated, and which still require engineering work. Put the operating cases, contaminants, schedule, safety basis, utilities, and site constraints in one controlled package. Then require every proposal to state its assumptions against that same package. Procurement gets a cleaner comparison, and engineering gets fewer surprises after the purchase order.
Prepare the process facts before asking for a final configuration.
Use the site resources above to compare equipment concepts, then send the operating envelope and project constraints through the verified contact page.