Particulate and Multiphase Processes (PD 23-1415): NSF Transport Phenomena Cluster Opportunity

Particulate and Multiphase Processes (PD 23-1415): NSF Transport Phenomena Cluster Opportunity

Particulate and Multiphase Processes (PMP) is one of the four NSF programs that sit under the Transport Phenomena cluster, alongside Combustion and Fire Systems, Fluid Dynamics, and Thermal Transport Processes. It is designed for fundamental research on particle- and multiphase-dominated transport behavior where discoveries at the micro, meso, and macro scale can change how industries and systems perform in practice.

If your idea is about how particles, droplets, bubbles, suspensions, or multiphase interfaces behave and how that changes a real engineering system, this is a strong fit. The program is unusually important for teams that want a route between curiosity-driven process understanding and application-ready engineering outcomes. The official NSF page is an “open” program page with sustained rolling acceptance (“full proposal accepted anytime”) and explicit routing guidance through NSF Proposal and Award Policies and Procedures (PAPPG) requirements.

This opportunity is a good target for 2026/2027 planning cycles because it remains open continuously and is explicitly framed as a continuing program track rather than a one-cycle-only deadline event.

What this program actually funds

The PMP program is explicitly focused on the “fundamental research that governs particulate and multiphase systems.” This includes:

• flow of suspensions, drops, and bubbles,
• granular and granular-fluid dynamics,
• behavior of micro/nano-structured fluids,
• active fluids,
• self-assembly and directed assembly involving particulates, and
• interfacial dynamics including adsorption/desorption behavior.

The language is broad enough to apply across many fields, but not so broad that any fluid system problem is automatically in scope. The program emphasizes a clear transformation path from particle-scale mechanisms to larger system behavior.

In practical terms, stronger proposals typically show how an “observable small-scale mechanism” changes a systems outcome you can quantify. For example:

• does improved particle stabilization reduce energy losses?
• does controlled coalescence suppression improve a reactor process window?
• does a microfluidic insight scale to a deployable transport or manufacturing process?

NSF guidance also calls for a project that demonstrates novelty or potentially transformative impact, and expects the proposal to articulate both scientific merit and potential broader industrial or societal value. This is important: the program is not a pure modeling exercise and is not a general-purpose application grant. It is explicitly fundamental with a translational expectation.

Why it is useful now (2026–2027 planning)

Many teams skip this opportunity because “open year-round” sounds casual, but the open cadence can be strategically powerful. If your PI and collaborators are not ready for a narrow hard deadline cycle, PMP provides predictable administrative behavior:

• You can mature data and preliminary results without being forced by a single annual date.
• You can align a submission to internal readiness, while still keeping momentum for 2026 or 2027 funding cycles.
• You can submit proposal variants in parallel planning streams (main grant plus potentially an EAGER or RAPID component) because NSF explicitly notes those tracks can be discussed and submitted outside normal full cycles.

It is particularly relevant for teams in transport-heavy domains: advanced manufacturing, energy harvesting, biological transport systems, biotechnology, and environmental or sustainability-oriented engineering. The NSF description repeatedly ties particle-scale understanding to larger application value. So if your team has a compelling mechanism but needs narrative architecture to link it to use case outcomes, PMP can be a strong match.

The date context also matters: NSF’s Transport Phenomena page and PMP page updates show continued attention to this cluster in 2026 and beyond, with “accepted anytime” framing still listed as the active intake style. This matters for cycle planning because review behavior is tied to standard NSF processing rather than one-off calendar deadlines.

Eligibility and fit check

The page does not publish a short bullet-point equivalent of NIH-style “eligible organizations” text. Instead, it applies NSF-wide proposal rules for CBET and ENG with full compliance to PAPPG. The practical implication is:

1. If your organization can legally submit proposals and satisfy standard NSF compliance controls, you can usually be in play.
2. If your proposal is outside the scope of transport and multiphase science, the NSF program staff may return it or transfer it to another program.
3. If your proposal is too narrow in application only, with weak fundamental basis, it may not align.

So your first eligibility action is actually a fit action:

• Confirm the problem statement is fundamentally particulate or multiphase transport.
• Confirm the project design includes either theoretical, computational, or experimental treatment (or a credible mix).
• Confirm the proposal clearly links microscopic understanding to a larger process-level outcome.
• Confirm novelty is explicit in the summary.

The page also warns that certain subtopics should route elsewhere:

• electrode fluid-structure interaction in energy storage -> Electrochemical Systems,
• drops/bubbles on solid surfaces -> Fluid Dynamics,
• engineered reaction/separation surfaces -> Interfacial Engineering,
• pure particle synthesis routes -> Advanced Manufacturing (CMMI) or MPS.

If your draft sits near these boundaries, pre-submission contact is expected. NSF explicitly suggests speaking with program officers before submitting potentially boundary-crossing work.

If your institution is new to NSF submissions, treat PAPPG compliance as the first screening gate, not the optional technical gate. Non-compliant proposals are returned without review.

What to prepare before writing (a practical checklist)

1) Problem-to-systems map

Create a one-page map with four columns:

• micro mechanism you study,
• measurable intermediate metrics,
• transfer path to scale,
• expected systems benefit.

If the map has weak or missing arrows, reviewers may perceive the proposal as fragmented.

2) Novelty paragraph that is testable

NSF asks for novelty and transformative potential. Write a compact paragraph that answers:

• What is currently known,
• what exact gap you will fill,
• why this is materially different from standard transport studies.

3) Project scale realism

Use realistic timeline and budget assumptions and mirror NSF norms from the page:

• unsolicited program awards are often up to three years,
• single-PI budgets should reflect scale accordingly,
• larger projects should justify cost and effort.

The page’s notes on budget signals are not an invitation to submit generic, underdeveloped budget asks.

4) Cross-skill team design

The program explicitly supports interdisciplinary proposals and even recommends collaboration. Build the team around a coherent set of capabilities:

• one lead PI with transport/physics depth,
• one methods/modeling specialist,
• one application-domain partner when needed.

Avoid adding “nice to have” disciplines just to appear broad. NSF reviewers in transport topics usually penalize thinly integrated interdisciplinary structures.

5) Early program-officer conversation

For any proposal at the boundary of topic (for example, highly application-heavy or strongly chemistry-synthesis oriented), contact one of the listed program officers before submission. This is not formality; NSF has explicit direction that innovation outside core interest may be considered but should be discussed beforehand.

Application route, cadence, and compliance

Standard routing

The program page says proposals can be submitted via:

• Research.gov using NSF 24-1 process under the NSF Directorate for Engineering, CBET, Transport Phenomena cluster context, or
• Grants.gov using the NSF Grants.gov guide path, then checked via Research.gov workflow links.

In both paths, the critical point is: strict PAPPG compliance.

Cadence in a year-round program

PMP full proposals are accepted any time, but that does not mean you should submit immediately at any level of polish. NSF programs are not blind to quality. A strong submission should still:

• have a coherent narrative and completed sections,
• be technically grounded,
• complete institutional registrations and compliance steps.

For teams planning parallel 2026 and 2027 activity, common strategy is to:

1. Submit a hard draft by a fixed internal date,
2. route for internal review,
3. clear PAPPG compliance before final submission,
4. use this cadence for continuous improvement rather than trying to submit ad hoc.

Related mechanisms

The page also references CAREER, EAGER, and RAPID pathways:

• CAREER proposals have their own July deadlines,
• RAPID and EAGER can be submitted outside normal cycles but require pre-consultation,
• Supplements/workshops can be discussed and routed with program director alignment.

That makes PMP a useful parent home for mature ideas that may later branch into faster-response formats.

Review expectations and common mistakes

Reviewers in this cluster typically ask two linked things:

1. Is the work genuinely novel at the phenomenon scale?
2. Does it credibly connect to broader engineering impact?

The official page’s language around transformative nature and broader impact is strong enough to infer these are high-weight dimensions.

Common mistakes

• Treating the proposal as purely applied engineering with no fundamental physics narrative.
• Submitting a technically good experiment that does not explain why it changes the bigger system outcome.
• Missing explicit novelty in the project summary.
• Violating submission format or PAPPG compliance, then expecting technical merit to rescue the application.
• Proposing boundary topics that should live in sister programs without prior check.

How strong proposals differentiate

They do three things well:

• They make micro-to-macro transfer explicit,
• they combine mechanistic explanation with measurable performance deltas,
• they keep the narrative tightly in one coherent thread.

Very important: collaborative proposals should look integrated, not patchwork. If collaboration is used only for credentials, reviewers usually read it as risk not strength.

Typical project profiles that work well

Below are profile types that match PMP language and review logic:

Profile A: Micro-structure meets transport efficiency

Teams studying particle interactions at colloidal or multiphase interfaces and demonstrating measurable improvement in process throughput, control, or stability.

Profile B: Particle-scale process redesign

Projects that combine targeted experiments and models to change how multiphase behavior is predicted and controlled in reactors, transport systems, or advanced manufacturing lines.

Profile C: Biotransport-informed engineering

Work where nanoscale/particulate mechanisms explain physiological transport or diagnostic transport phenomena that can inform translational healthcare technologies.

Profile D: Interfacial control for sustainability

Studies where interfacial transport or particle behavior is tied to energy, environmental mitigation, or reduced emissions via better material or flow control.

All of these benefit from explicit outcome pathways and quantified impact hypotheses.

Preparation pitfalls unique to rolling deadlines

Because PMP is “accepted anytime,” teams often assume they can submit incrementally. In NSF context, rolling does not mean low bar. It means your first real gate is likely self-organization:

• Have your institution’s submission authority and forms ready,
• have your PI effort and budget structured to the requested project duration,
• align your narrative so each section builds toward a measurable set of transport outcomes.

If your institution has a strict internal proposal calendar, build a target date that gives at least two full review cycles before your preferred submission route.

Also, because submissions outside full cycles are easier to time, proposals with unresolved compliance risks frequently slip into avoidable technical errors. Treat compliance review as mandatory.

FAQ

Is this open for 2026/2027?

Yes. The program has no closed annual cycle requirement for full proposals and is explicitly listed as accepting proposals throughout the year. That makes it suitable for applications prepared during 2026 or early 2027 cycles.

Is the amount specified?

The program page does not provide a fixed dollar amount in the public summary. It references NSF CBET norms and standard award processing. For current budget expectations and award examples, check the program page’s “What Has Been Funded” and NSF award records.

Can I apply from industry?

The page primarily frames this as a CBET research program and indicates routes via NSF proposal systems under PAPPG. Industrial collaboration is often welcome in collaborations, especially where fundamental findings connect to practical outcomes, but applicant-type details follow NSF standard institutional eligibility.

Are CAREER and other NSF route-specific opportunities integrated?

Yes, with separate deadlines where relevant. CAREER follows its own schedule; PMP full unsolicited tracks remain ongoing.

Can I submit work on combustion or fire dynamics?

Only if the science is aligned with the PMP scope and the intended program review fit. The page notes this is part of a cluster and includes explicit boundary direction for some topics. If your project overlaps adjacent programs, contact program staff first.

Recommended next steps before submitting

1. Read the official PMP page and save a stable snapshot of the “full text sections” relevant to eligibility and proposal guidance.
2. Draft a one-page novelty-impact statement and map micro-scale mechanism to macro outcome.
3. Verify your PI and collaborators can complete PAPPG compliance and submission system requirements before polishing results.
4. If there is a topic boundary issue, schedule program-officer contact before final routing.
5. Decide early if this is full unsolicited, CAREER, or a related mechanism (RAPID/EAGER/GOALI/supplement) so you submit with correct deadline logic.

Official links

• Official program page: https://www.nsf.gov/funding/opportunities/particulate-multiphase-processes
• Program guidelines (PD 23-1415): same page indicates routing via NSF 24-1 and Research.gov/Grants.gov processes.
• PAPPG (NSF proposal rules): https://www.nsf.gov/funding/opportunities/particulate-multiphase-processes
• Grant policy links and NSF awards/terms referenced on the page via program-provided links.

If your project can clearly state a novel mechanism, a translational route, and a compliant, review-ready submission package, PMP can be an efficient route in the 2026/2027 cycle.