NSF Intelligent and Interactive Dynamic Systems (IIDS)

NSF Intelligent and Interactive Dynamic Systems (IIDS)

The Intelligent and Interactive Dynamic Systems (IIDS) page on NSF.gov is a stable program landing page for the engineering research portfolio focused on systems that evolve, adapt, and interact with people and environments. It is a flagship example of a program page that is structurally active, but not always one-line-simple in terms of proposal logistics. In other words: this page confirms the program intent and the official contact path, but you still need the active solicitation and NSF’s current submission rules for precise proposal windows.

For people scouting 2026/2027 opportunities, this one still matters because NSF has it as an active engineering program page with a 2026 publication date. That gives you a credible planning target: prepare your team, gather your systems model, and keep your proposal architecture ready while you watch for the exact submission windows that map to the current IIDS solicitation branch.

Key details

At first glance it looks concise. At proposal level, IIDS is not concise: if your research team has a hard systems problem and a human-system interaction component, this is where you can frame a technically serious, high-value submission.

Why this is a 2026/2027-relevant opportunity

NSF lists IIDS as a current program, and the official publication stamp is April 17, 2026. Even if there isn’t a single universal due date on the public landing page, that publication signal still matters for two reasons:

1. NSF is treating this as an active topical research channel, not an archived historical notice.
2. Programs in this category commonly post and refresh active due dates through linked solicitation pages that map into regular NSF workflow windows.

In practice, you should think of IIDS as a “monitor + prepare” opportunity:

• Monitor: check NSF program and solicitation pages regularly for open/active deadlines and solicitation IDs.
• Prepare: keep proposal architecture ready to adapt to the current solicitation envelope.

Because your target cycle is 2026 and 2027, this is still actionable if you can satisfy two conditions quickly: your project must align with IIDS’ explicit mission language, and your proposal team must be ready to switch into the active template as soon as deadlines and format guidance are posted.

What IIDS is actually funding

The program page is very explicit about what the effort is about:

• Fundamental research into intelligent dynamic systems where behavior changes over time.
• Research that supports engineered systems interacting with people.
• Emphasis on modeling, simulation, inference, control, and resilience.
• Support for cross-disciplinary methods that are more than one-discipline science, as long as they produce transformative systems-level value.

This is broader than robotics alone and broader than AI software alone. The language includes humans, systems science, infrastructure-style complexity, and applications that need reliability and safety under uncertainty. If your proposal is in this sweet spot, IIDS is not trying to fund generic “interesting idea” work. It is trying to fund work that helps systems behave better under real constraints.

To avoid misalignment, test your idea against this question set:

• Does your research define a dynamic system with observable and evolving behavior?
• Is there a clear mechanism showing why your intervention improves performance, resilience, or human-system interaction?
• Are your methods theoretical/computational/experimental in a way that NSF can review through standard research criteria?
• Can you show why this is more than incremental optimization and why this specific approach is high-leverage?

If your answer to most of these is “yes,” you are in the right framing for IIDS.

Eligibility and readiness criteria

The IIDS landing page does not publish a long-form eligibility checklist in the same way that some RFA pages do. It does publish the governing frame:

• proposals must follow the NSF funding opportunity and the NSF Proposal and Award Policies & Procedures Guide (PAPPG);
• NSF grants and cooperative agreements are subject to NSF award terms;
• the program aligns with NSF’s statutory mission and is administered under the ENG/CMMI portfolio.

Use that frame as your first compliance baseline. When the active solicitation is open, it will define more specific program boundaries.

For readiness, your team should prepare:

1. Institution-level readiness: confirm your institution’s authority to accept and manage NSF funding under current rules.
2. Financial and budget readiness: even if no amount is visible on the landing page, you need a credible budget schema that maps to normal NSF cost principles.
3. Technical scope readiness: if your proposal has strong systems science but weak engineering context, reframe it around measurable engineered outcomes.
4. Human-system integration readiness: IIDS explicitly includes systems interacting with people; if people are not truly in the technical loop, the proposal can look misfit.

It is safer to treat this as a must-be-eligible by process + fit-by-substance opportunity.

Application process (how to act now)

Because this page does not expose the full submission sequence by itself, treat application steps as a two-stage workflow:

Stage 1: Build proposal-ready scaffolding

While deadlines are not fixed on this page, most NSF programs still require the same core proposal architecture:

• problem definition in engineering terms;
• technical approach and methodology;
• expected outcomes and measurable success indicators;
• a work plan with risk acknowledgment;
• budget and justification aligned with institutional templates;
• references and prior work context.

For IIDS, your section on technical approach is where most teams fail: they overstate novelty and under-explain system-level effect. NSF reviewers read for mechanism, not adjectives. Include how your methods improve prediction, control, adaptive behavior, safety, or resilience in a dynamic context.

Stage 2: Move to solicitation-specific format

Once NSF publishes or updates active submission details, map your draft into its form and requirements. The page itself signals that current opportunities are found through NSF ENG partnerships and standard NSF submission channels. Use those entry points and submit according to current NSF systems requirements for that deadline.

A practical workflow:

• keep a short project one-pager for internal alignment,
• build a full technical narrative in a template versioned by deadline,
• route to institutional grants office before internal deadline,
• run a final compliance pass for PAPPG and award-terms alignment,
• submit through the official system early enough to survive technical problems.

What reviewers usually care about on programs like IIDS

The page language points to a high bar on conceptual clarity and practical relevance. Expect reviewers to score you on:

• whether the problem is clearly a dynamic systems problem,
• whether methods are credible at the model level,
• whether human interaction components are principled,
• whether the work can scale from concept to real-world impact in measurable terms,
• whether your team demonstrates interdisciplinary execution capability.

The phrase “fundamental research” is central. This is a warning and an opportunity: you can propose foundational models and methods, but they must still be framed around plausible engineering outcomes in real systems.

Proposal architecture that matches the program intent

For a stronger IIDS package, use this structure:

1) System statement

Define your dynamic system in one paragraph: state variables, boundary conditions, uncertainty sources, and intervention points.

2) Mechanism and control hypothesis

Explain the mechanism your method changes. Show the pathway from model assumptions to expected system response.

3) Human-system interface

If your system touches people, define interaction channels, safety boundaries, and evaluation metrics for human outcomes.

4) Validation strategy

Describe experiments, simulations, or field validation with clear comparators and data collection logic.

5) Failure plan

Include what changes if your first control approach underperforms, and what your fallback experiment is.

6) Delivery and impact

Show implementation feasibility and relevance to national priorities at a systems scale.

This structure is not just style. It is a way to prove the proposal is both fundamental and engineering-relevant.

Common mistakes that cost teams in technical NSF opportunities

1. Treating IIDS as a generic AI grant.

If your work is simply AI method development without dynamic-system framing, it reads weak. The framing must remain dynamic systems + interaction + resilience.

2. Ignoring human interaction language.

The program explicitly includes systems that interact with people. If users are only a paragraph-level mention, reviewers will discount the relevance.

3. Submitting without program-specific compliance readiness.

If you wait until the last minute, you’ll miss the “format-first” nature of NSF workflows.

4. Over-indexing on technical elegance and under-indexing on outcomes.

NSF can reward depth, but it still wants to see why the work improves reliability, safety, or functionality.

5. Assuming a fixed funding amount and fixed windows from the landing page.

This page currently does not publish a universal award size or deadline. Do not invent them in a proposal.

Frequently asked questions

Is IIDS definitely open right now?

The program page is published and active as of the stated date. But for active submission windows, you should confirm the currently live solicitation and due date path in NSF systems.

Is this a postdoc fellowship, student fellowship, or grant?

It is listed as an NSF program area for research projects, governed by grant/cooperative agreement structures under NSF rules.

Is the amount known?

The IIDS program page does not publish a universal award amount. Amounts are usually solicitation- or project-specific and can change by year.

Is there a specific publication and deadline pair?

Publication date is visible (17 April 2026). A universal deadline is not shown on that landing page.

What is the official way to contact them?

IIDS lists the program team contact directly: [email protected], phone (703) 292-8360.

Where should I start this week?

1. Build your project-to-program fit narrative.
2. Prepare a concise systems model and evaluation design.
3. Confirm if your institution is ready to submit with current NSF systems status.
4. Watch for solicitation-specific instructions and submit with a full compliance pass.

Practical preparation timeline for 2026/2027 planning

If you are planning for 2026/2027 funding, do this on fixed cadence:

• Week 1–2: define system problem and evidence map.
• Week 3–5: write technical core with dynamic model, uncertainty framing, and interaction logic.
• Week 6–7: build budget and cost logic; align with partner commitments.
• Week 8: run internal review for NSF formatting and compliance language.
• Submission window: align final draft with the current solicitation and submit through official channels.

The goal is simple: don’t use the public page as your only work product. Use it as your compliance anchor and planning baseline.

What to do if your idea is borderline

Many ideas look close to IIDS but miss the target by being too general. If your project is not clearly dynamic-system-centric, shift one of these dimensions:

• Add explicit dynamics: show time-varying behavior.
• Add explicit adaptation: show why the system changes in response to context.
• Add explicit interaction: show how people or external ecosystems are part of system behavior.
• Add explicit metrics: show measurable improvement claims.

Do not oversell. The best IIDS applications are rarely the loudest. They are the most technically coherent and most clearly linked to system behavior.

Official links and next actions

• Official NSF program page: https://www.nsf.gov/funding/opportunities/iids-intelligent-interactive-dynamic-systems
• Program contacts: [email protected], (703) 292-8360
• NSF award and submission standards: Program & Award Policies & Procedures Guide (PAPPG), Research.gov and Grants.gov

If you need a reliable internal planning baseline, use this page as a program-intent anchor and then align every section to the exact solicitation version when active. For 2026/2027, that is the difference between a good draft and a submit-ready proposal.