RFA-OD-25-012: Informatics, Coordination and Service Center for the Mutant Mouse Resource and Research Centers (U42)

Captured cycle: This page is retained for historical guidance. Confirm whether the program has reopened before planning an application.

RFA-OD-25-012: Informatics, Coordination and Service Center for the Mutant Mouse Resource and Research Centers (U42)

If your lab depends on mouse models, mutant strains, or cross-institutional resource networks, this is one of the most operationally important NIH opportunities to understand. The RFA is not a classical project grant for a single experimental question. It is a U42 multi-component cooperative agreement that funds infrastructure operations for the Mutant Mouse Resource and Research Centers (MMRRC) ecosystem through an Informatics, Coordination and Service Center (ICSC). This is strategic, not ad hoc science.

The opportunity is technical and organizational rather than hypothesis-only. The ICSC is expected to run the services that make the MMRRC consortium usable by the wider biomedical community: secure informatics, user support, data coordination, strain acquisition workflows, and regular reporting to NIH and consortium members. In practical terms, you are applying to host a center-level infrastructure operation with national reach and explicit accountability.

A few important words for fit before you read further: this is a cooperative agreement style award, clinical trials are not allowed, and it is intended for institutions that can run a real operating center, not a short pilot study.

At a glance

What this opportunity is (and is not)

This call is best understood as infrastructure governance for a shared mouse resource network.

The NOFO says the ICSC should support MMRRCs by coordinating:

• informatics services and data systems,
• centralized access and catalog functions,
• customer service and ordering support,
• web portal and public-facing communications,
• strain processing workflows,
• metrics reporting and consortium communications,
• active coordination with new approach methodologies (NAMs), and
• links to broader disease-model ecosystems.

This means the award is awarded to a lead center institution, not to individual investigators only. Your proposal needs to include a full center management architecture with clear coordination and service outcomes.

This is therefore:

• not a clinical trial funding mechanism,
• not an individual lab travel or salary-only opportunity,
• not a simple one-page equipment grant,
• not a mechanism to test a single mouse model hypothesis in a narrow experiment.

It is a multi-layered operational grant requiring enterprise planning.

The page also makes this explicit: the recipient must maintain nonclinical trial restrictions and show how the ICSC improves and coordinates resource sharing for broader biomedical use.

Who this is built for

The strongest candidates are institutions and teams that can credibly run a center-like operation with distributed components. The most suitable profiles usually include:

• a lead research-intensive organization with administrative support for large NIH applications,
• a PI team with established project management and coordination capacity,
• informatics leadership (curation, integration, database operations),
• existing involvement or strong relationships with national research resources,
• realistic plans for user support, reporting and evaluation.

The NOFO is explicit that the project is intended to support the MMRRC mission. A successful application should show:

• evidence of capacity to coordinate across institutions,
• realistic staffing and workload design,
• clear policies for handling strain submissions and user requests,
• transparent data practices,
• a practical pathway to make resources findable and useful.

Eligibility and who can apply

This is an opportunity for organizations with specific institutional forms and clear restrictions.

The NOFO lists eligible organizations as:

• higher education institutions,
• nonprofits (including 501(c)(3) and non-501(c)(3) non-educational orgs),
• for-profit entities (including small business and others),
• local governments (state, county, city, township, special district).

Foreign entities are not eligible, and foreign components of U.S. organizations are not eligible either. The text repeatedly states non-domestic entities cannot apply.

For individuals, the NOFO is less restrictive in the PI profile language than typical fellowship rounds: any individual with appropriate expertise and resources can be invited to work through their organization on a PD(s)/PI role. Multi-PD/PI setups are allowed where eligible under NIH instructions.

This is an NIH submission where the following compliance conditions are mandatory:

• SAM, UEI/CAGE (if applicable), Grants.gov, eRA Commons registrations in place,
• organization and PI registrations complete before submission,
• registration delays are not accepted as reasons for late submission,
• applicant-level organizational registration complete and current,
• multiple applications possible only if scientifically distinct.

Notably, NIH also states overlapping applications cannot be simultaneously active under certain conditions. If you submit a renewal, resubmission, and overlap conflicts are possible and will be rejected unless criteria are clearly separated.

If a PI has already submitted a substantially overlapping application that has not received a summary statement, the NOFO says NIH does not accept conflicting re-submits.

Funding mechanics, budget shape, and practical implications

The NOFO does not announce a single total opportunity pool headline in the snippet that is easiest to state. It does explicitly set a hard application budget limit: no more than $650,000 in direct costs per year. The project period can be up to four years.

It is described as a continuing support structure for an existing consortium center, so applications are not for isolated, one-time research tasks. The scale expected is operational: staffing, systems, support, reporting, and quality-management activities.

A practical implication: your budget narrative must reflect sustained operations, not only scientific aspiration. If you ask for too-large speculative software development without implementation and staffing realism, reviewers are likely to flag implementation risk.

Because this is a cooperative agreement, NIH anticipates substantial programmatic involvement.

The NOFO says there will be close collaboration between the PD/PI and ORIP/DPCPSI project scientists after award and that the NIH role is partnership and coordination, not simply passive stewardship. That can be useful to applicants who need help with policy alignment, but it also means your plans should be administratively solid before submission.

Review structure and what reviewers look for

This NOFO is assessed through full NIH scientific and technical review channels (SRG review then further NIH-level review). That has several consequences:

1. You need competitive science and operations quality, not only administrative completeness.
2. The multi-component design will be reviewed by section with explicit descriptors.
3. Budget and project period must be defensible.
4. A good response must show not just concept but operating capacity.

The review criteria include classic NIH items:

• Significance: does this center address real community need and add capability,
• Investigator: do leadership and team capacity match the coordination work,
• Innovation: are tools, workflows, and management approaches materially advancing service quality,
• Approach: is implementation feasible, secure, and integrated,
• Environment: does institution support the center operations,
• plus section-specific descriptors for each component.

Each major component has specific review expectations:

• Coordination
• Customer service and public relations
• Informatics
• Applied research project (minor component, up to 10% of direct costs)

The Applied Research Project is explicitly capped at up to 10% of direct costs in the NOFO and meant to be high-value and tightly connected to Center goals.

Additional review areas are also considered for human subjects, vertebrate animals, biohazards, and resource sharing plans when relevant. Even if your center is primarily operational, your project still needs risk/compliance clarity in all applicable areas.

Application mechanics you must plan around

This NOFO requires NIH format discipline from the start. It is a multi-component SF424(R&R) package and follows Multi-Project (M) instructions.

In practice, applicants usually underestimate how much structure this introduces. The NOFO details required fields and section-specific constraints, including:

• multi-component assembly and component type handling,
• consistent page limits,
• specific component structures (Overall, Coordination, Informatics, Customer Service/Public Relations, Applied Research Project),
• single submission account management across components,
• required evidence and attachments such as letters of support in the Overall Research Plan,
• consolidated resource sharing plans.

Because this is a multi-component NOFO, a common failure mode is building three good sections that do not assemble cleanly. You should build from the required template and map each piece to the required section structure from day one.

Submission routes are standard NIH electronic routes:

• NIH ASSIST,
• or institutional system-to-system to Grants.gov/eRA Commons.

And all registrations must be active before submission.

The NOFO also sets strict submission timing and internal deadlines in the local time zone of applicant organization (5:00 PM local).

What to include to maximize competitiveness

1) Show real center operations, not only good intentions

A proposal that says “we will improve informatics access” but has no concrete system architecture or staffing model will be weak.

You need to show:

• who owns every required workflow,
• what infrastructure handles strain intake, curation, access, and communication,
• how you prevent delays in ordering and user support,
• how your site maps to consortium-wide processes.

2) Make data flow explicit

The ICSC function depends on interoperability and transparency. Mention concrete methods for:

• secure catalog and strain data standards,
• searchable fields with complete provenance,
• update traceability (who updated what and when),
• monthly and annual reporting outputs.

The page references FAIR principles and strong curation standards. That should appear in your plan, not as marketing language.

3) Link applied work to center priorities

The Applied Research Project is limited to 10% of direct costs and should not become a disconnected side project. It should be tightly coupled to Center capacity and user impact.

4) Build governance and communication routines

The NOFO is explicit about monthly teleconferences, annual consortium meetings, and active reporting to members. Strong applications include:

• clear governance map,
• internal and consortium reporting cadence,
• escalation path for policy/program staff interactions,
• documented user feedback loops.

5) Define integration with NAMs without overpromising

The ICSC should coordinate with new approach methodologies (cell culture, organoids, computational models, microphysiological systems). Reviewers are looking for credible integration planning, not overbroad claims of broad model replacement.

Frequently asked practical questions

Is this only for mouse genetics groups?

The NOFO is in the mouse resource domain but expects broad relevance across categories of biomedical work that draw on MMRRC and related resources. It is strongest when proposals connect mouse resources to broader human-disease model relevance and reproducible translational utility.

Can foreign collaborators participate?

Foreign entities cannot be applicants, but international collaboration can be relevant to the science if managed in compliant ways through U.S. host channels. The key rule is that the applicant and its direct organizational structure must be U.S.-based and domestic.

Can we apply if we are applying for other MMRRC-related opportunities?

The NOFO supports continued center work and is part of an ecosystem, but NIH overlap rules matter. You must avoid duplicate/highly overlapping active submissions without review sequencing resolution.

Is this useful for small organizations?

Potentially, if they can marshal the required operational capacity. But practically, this is a center-scale structure, so reviewers expect depth in management, infrastructure, and administration.

Does this accept only renewals of existing centers?

No, it allows new, renewal, and resubmission categories, but not every institution is equally positioned for each route.

Common mistakes we see in center-type NOFOs

Missing integration between sections

If Coordination, Informatics, and Customer Service sections are each strong alone but disconnected in implementation plan, review committees can penalize coherence.

Underestimating registrations

SAM / grants.gov / eRA delays commonly derail strong teams. The NOFO clearly says registration should be complete early and is not a late-submission excuse.

Vague customer service model

A large number of applications overpromise support volume without process design. You should name service workflows, response channels, tracking expectations, and quality monitoring.

Weak data strategy language

This is a data-centric infrastructure grant. A generic “we will build a database” statement without data standards, traceability, and user access architecture is not enough.

Ignoring section-specific constraints

The multi-component format has different content rules per section. Teams who apply a single narrative format uniformly often lose scoring due to missing required items or page-rule mismatches.

Treating clinical-trial language as optional

Clinical trials are not allowed. Even if only a small subcomponent touches clinical pathways, it must stay out of prohibited scope.

Preparation checklist (in practical order)

1. Confirm institutional registration status first (SAM, UEI/CAGE, eRA, Grants.gov).
2. Choose lead organization and secure internal commitments before drafting narrative.
3. Draft governance model showing authority, reporting lines, and center roles.
4. Define section-by-section content outline tied to NOFO-required page limits.
5. Build integrated budget by section and by center activity line item.
6. Write resource sharing and user access sections with explicit metrics.
7. Attach all letters of support required by the section plan.
8. Run an internal compliance check against NIH Multi-Project guidance before opening the final submission route.

Official links and direct actions

For official details, always use the NOFO page, not secondary summaries. Recommended order:

• Opportunity page: https://files.simpler.grants.gov/opportunities/0722ef53-909e-498a-b773-56ce1ca45d1e/attachments/28b9425b-f40e-4c63-a7d6-6422e1a141b7/RFA-OD-25-012-Revised-Full-Announcement.html
• NIH ASSIST / how-to-apply references linked on the NOFO,
• eRA Commons and Grants.gov submission systems,
• ORIP office guidance and contact points.

Who to contact

From the official agency contact section:

• Application system support: eRA Service Desk,
• Grants.gov support center,
• Scientific/Research questions: ORIP, [email protected],
• Peer review questions: [email protected],
• Financial/grants management: [email protected].

Given the complexity, most teams should include a project-level coordinator who follows the NOFO sections line by line while drafting and another internal reviewer who checks NIH form instructions.

Is this likely to fit your organization?

Choose this only if you can operate at infrastructure scale. If your goal is a single high-quality scientific question, you should probably apply to a regular R01/U mechanisms. This RFA is for center-level systems work with real national reach and ongoing service obligations.

If you do qualify, you are applying for a partnership with a national model-resource ecosystem. Your strongest application shows measurable systems, disciplined governance, operational maturity, and practical plans to sustain the MMRRC mission through informed coordination and open, searchable resources.