Seed Instrumentation Support (SIS) Program (S10 Clinical Trial Not Allowed): 2027-FY Biomedical Instrumentation Seeding for US Institutions

Seed Instrumentation Support (SIS) Program (S10 Clinical Trial Not Allowed): 2027-FY Biomedical Instrumentation Seeding for US Institutions

The Seed Instrumentation Support (SIS) program is a narrow federal research infrastructure opportunity for institutions that need one significant new biomedical research instrument or integrated system to move into a stronger shared-use capacity baseline. The opportunity appears in NIH-linked grant forecasting as a FY 2027 instrument support mechanism with an expected application due date of 2026-07-01 and anticipated award in 2027-05-01. It is a grant (not a loan), with no required cost sharing reported in the listing, and an award ceiling of $400,000 against a minimum of $50,000 and a minimum budget per project that can support one strong equipment-based intervention.

At a glance

What this program actually funds and why it is different

This is not an unrestricted research grant. It is not for salaries, travel, training stipends, operating consumables over years, or broad lab startup support with no instrument outcome. It is narrowly aimed at equipment infrastructure. SIS is intended to “seed” research capability by providing support to institutions for a single item or integrated commercially available system that can then be used by multiple research teams.

The listing description is explicit: NIH is supporting institutions so they can purchase one missing, high-impact tool and then use it to broaden reproducible research activity across multiple projects and users. The official language emphasizes a shared-use expectation, collaboration, and longer-term research capability. In practice, this is a strategic capacity award: if your institution is currently constrained by a missing technology bottleneck, SIS can be one of the fastest ways to unlock a new class of projects.

The key distinction from many equipment opportunities is that this is framed as a seed-like intervention, not a complete capital refresh program. If your institution already has the instrument class in question and is asking for a simple upgrade path, SIS may be a poor fit. The program is more defensible when the instrument type does not currently exist institutionally.

Who this is for (and who should skip it)

The eligible applicant profile from the public listing includes:

• Nonprofit organizations, including both 501(c)(3) and non-501(c)(3)
• Public and private institutions of higher education

What often surprises applicants is that this is not limited to only major research universities. The intent is to support capability growth where missing. The program’s supporting guidance from NIH’s S10 page also clarifies that SIS is especially designed for institutions needing new shared-infrastructure entry points, whereas SIG-style pathways can better fit well-established facilities looking to strengthen existing high-end instrument ecosystems.

Eligibility logic: your pre-check before writing anything

Before drafting, run this gate sequence:

1) Are you trying to fund the right outcome?

A valid SIS concept must be materially a shared infrastructure intervention. A proposed instrument should:

• Be commercially available
• Be state-of-the-art enough to change what your institution can do next
• Support a group of NIH-funded projects, not just one isolated internal use case

The ORIP S10 FAQ adds that the instrument should not be a simple existing replacement and should meaningfully add research capability. It also says institutions should explain training and usage plans rather than presenting the purchase as a pure procurement exercise.

2) Is this truly absent capacity?

For SIS specifically, the stronger positioning is that the instrument type is missing in your organization. That is a practical threshold. If you already have a near-equivalent system, SIS is vulnerable on eligibility logic.

3) Can you justify shared use and at least two NIH-funded users?

The S10 guidance states that SIS applications should show at least two NIH-funded users, and at least one must be based at the applicant organization. This is a technical issue many teams fail to satisfy because they build a good instrument argument but weak user architecture.

4) Are your users eligible in this context?

NIH-funded users from the same or neighboring institutions can be part of the user base. NIH training, fellowship, or non-research award mechanisms are typically not the right user base substitute for this requirement. Your plan should prioritize active NIH-supported research users with clear project intent.

5) Are clinical-use claims avoided?

The SIS listing is explicitly marked “Clinical Trial Not Allowed.” The equipment cannot be framed as a clinical treatment pathway program. If your institution is planning clinical billing or direct care service operations around the tool, this is misaligned.

6) Are you ready for institutional obligations beyond purchase?

This is critical: SIS funding can cover purchase support, but operating costs, service contracts, personnel, maintenance planning, and ongoing support are generally expected to be covered through the institution’s own planning. If your full plan relies on the grant carrying all downstream costs, it will read weak at the budget and sustainability review stage.

Application strategy: what reviewers reward in practice

The listing itself is high-level, so your strongest edge is an application that is operationally credible, not just technically exciting. Reviewers tend to reward five things:

1. Clear absence-to-capability narrative

Spell out why current research activities are constrained. Avoid generic claims such as “we need this to improve science.” Name specific blocked projects, delayed experiments, and current turnaround bottlenecks.

2. Specific user plan

List intended users, their NIH-funded projects, and how each project benefits from access. The user plan should not be aspirational, e.g., “many projects will use this.” Provide 2–6 near-term users and concrete study types.

3. Demonstrated shared model

Show governance and access policy: scheduling, training, usage tracking, user charging (if any), and conflict resolution. A tool that sits unused after award is common failure mode. Mention policies for prioritization, access transparency, and onboarding.

4. Domestic procurement realism

NIH S10 guidance says domestic preference should be made where possible and justified if foreign options are proposed. Even if your final vendor choice is not domestic, provide a practical justification tied to capability, support quality, and total value.

5. Implementation readiness

Institutional letters should clearly commit to service contracts, maintenance responsibility, facilities support, data management of usage, and administrative ownership. Weak letters are one of the main reasons shared-infrastructure grants are downgraded.

6. Timeline realism and readiness to execute

The due date may move; the program is forecasted. Build your internal timeline backward from the posted estimated date anyway. Keep enough lead time for PI alignment, compliance documentation, procurement checks, and eRA/Gov registration continuity.

Recommended timeline (for planning against the forecast)

Because the opportunity is currently listed in a forecasted state, think of this as an operations run-up schedule:

• Now (immediate): Confirm instrument absence, define required capabilities, and map users with NIH awards.
• Within 2 weeks: Draft instrument justification with procurement options and user access model.
• Within 4 weeks: Collect institutional support letters and service plan commitments from facilities/administration.
• Within 6 weeks: Finalize budget and user justification, cross-check NIH user eligibility.
• Before July 1, 2026: Submit through the NIH/Grants portal path referenced from Grants.gov (as directed in the listing).

If your institution has prior experience with NIH application systems, parallel internal readiness should be your advantage. If not, prioritize process setup early: eRA Commons, compliance checks, and institutional assurance can consume time.

Budget and financial structure

The program listing identifies:

• Program funding: $5,000,000 (forecasted)
• Expected number of awards: 15
• Funding minimum: $50,000
• Funding maximum: $400,000
• No cost sharing requirement listed at the program level

In the S10 FAQ context, cost sharing is generally not required for SIS baseline support, but institutions should still document if complementary institutional resources are needed for service and sustainability. The practical challenge is that an excellent instrument purchase can fail if the post-award operating model is not fully budgeted internally.

A good budget section should show:

• Clear instrument cost ceiling relative to requested funding
• Institutional commitments for staff support and maintenance
• Facility and training commitments (in-house if possible)
• A user-access model that converts one-off purchase into measurable utilization

Avoid a one-line budget narrative. Even if this is an equipment-first mechanism, reviewers still need to see post-award viability.

Compliance and submission details

The official listing indicates that applications should proceed via grants.gov for this opportunity, and it provides contact details for NIH program office (Xiang-Ning Li, MD, PhD at the time of posting). For planning, the current official source gives:

• Publication date and updates: listing posted/updated in 2026
• Estimated post date: February 28, 2026
• Estimated application due date: July 1, 2026
• Estimated award date: May 1, 2027
• NIH award number format: PAR-26-074

Because this is a forecasted listing in this cycle, assume that exact mechanics can change before final NOFO release, including additional attachments and formatting requirements. The safe approach is to align all narrative content now, then synchronize final forms once the NOFO/attachments are posted.

Common mistakes that hurt SIS applications

Mistake 1: Treating SIS like a general infrastructure grant

This program is specific: one instrument or integrated system with shared-use intent. If your concept is diffuse and equipment-light, it does not fit.

Mistake 2: Proposing an instrument already present

SIS targets missing capacity. If the instrument class exists in your own institution, even in older form, your request needs a compelling demonstration of a significant capability gap that a prior similar instrument cannot fill.

Mistake 3: Weakly defined user base

Saying “many labs will use it” is not enough. Give user names, projects, and expected usage pattern. Tie each user to active NIH-funded relevance.

Mistake 4: Ignoring shared governance

A shared infrastructure award without shared governance is contradictory. Include governance, scheduling, training requirements, and access policy.

Mistake 5: Not planning sustainability

The tool should remain used and maintained. Institutions that do not explain support for service contracts, staffing, and software tracking are scored as high effort but low execution.

Mistake 6: Forgetting SIS-specific constraints in wording

The program is explicitly “Clinical Trial Not Allowed” and supports seeding capability, not clinical care service expansion. Overreaching into ineligible uses can trigger preventable review issues.

FAQ

Is this a limited competition?

The listing is currently published as part of NIH forecasted opportunity pages, not as a limited competition announcement. It appears to be a competitive grant mechanism with fixed overall funding and forecasted award slots. The specific review/triage design will be finalized in NOFO materials and workflow.

Can nonprofit organizations without 501(c)(3) status apply?

Yes, the official listing includes nonprofit education and nonprofit categories broadly, including 501(c)(3) and non-501(c)(3) nonprofits.

Can we apply if we are a small institution with limited instrumentation footprint?

This can be an ideal use case for SIS if you can show concrete scientific projects that require one missing capability and produce shared, multi-user impact.

Can we request a used instrument?

The guidance emphasizes commercially available instruments and state-of-the-art value. Best practice is to propose commercially supported, current-generation options with maintenance and training viability.

Can cost sharing be used?

The listing indicates no required match at the program level, but institutions may still provide cost-sharing internally for infrastructure support. If requesting cost-share is expected by your procurement model, define it explicitly in support documentation.

Practical checklist before submission

Use this sequence to reduce avoidable errors:

1. Verify the institution has no equivalent instrument class that weakens “new capacity” claims.
2. Confirm at least two NIH-funded users and readiness to share.
3. Draft one-page summary of scientific use cases tied to NIH-funded projects.
4. Obtain signed institutional support for facilities, maintenance, and utilization policy.
5. Align instrument technical specs to anticipated outputs and user volume.
6. Confirm procurement route and domestic preference justification if applicable.
7. Build a usage and training rollout plan for year one.
8. Map risks: delayed procurement, installation schedule, maintenance support gaps.
9. Track notice updates because forecasted postings can change before final submission.

Official links

• Opportunity listing: https://simpler.grants.gov/opportunity/fd0c942d-4760-41c1-b7c2-57c63b3c0a62
• Grants.gov reference record: https://www.grants.gov/search-results-detail/360882
• NIH S10 program FAQ and guidance: https://www.orip.nih.gov/division-construction-instruments/s10-instrumentation-programs/pre-application/frequently-asked-questions

The most important readiness point is this: SIS is strongest when your proposal is written as an institutional growth program for shared research tools, not just as a “buy this machine” request. Keep your narrative grounded in concrete users, shared access, and institutional capacity to run the instrument sustainably after award.