Date Open: 
07/05/2023
Sponsor: 
National Science Foundation
ORD Notice of Intent Deadline: 
07/17/2023
Agency Deadline: 
09/06/2023
Limit per Institution: 
1
Source: 
External
Cyberinfrastructure Technology Acceleration Pathway (CITAP)

This CITAP solicitation is focused on the translation of innovative research CI software such as system software, libraries, application codes, and software enabling data services. NSF seeks proposals that aim to design, test, and subsequently operate a pathway service within the ACCESS program that manages and accelerates the translation of promising research CI software to production-quality services across the NSF advanced CI ecosystem in support of the NSF S&E research community. CITAP proposals are expected to create a new workflow process (represented notionally in Figure 1 below) within the ACCESS program that: (1) identifies novel CI software from diverse sources in a strongly community-informed way; (2) establishes an open and merit-based process for selecting and prioritizing/sequencing which of the identified innovations are of highest and most immediate value to users of the advanced CI ecosystem and can be feasibly translated to production level and made available for use by researchers using ACCESS resources; and (3) establishes an operational process that translates innovations into production services, including creation of partnerships where necessary to address each of the technical challenges and intellectual property (IP) considerations faced when integrating novel CI software within the advanced CI ecosystem.

Limit on number of proposals per organization:

  • Internal Notice of Intent Deadline: July 17, 2023
  •  Agency deadline: September 6, 2023
Guidance for the preparation of the Notice of Intent to Research Advancement:

Prepare the following information to enter in the InfoReady here:

  • PI name, title, and contact information
  • Descriptive Proposal Title
  • Project Summary: 3 or 4 sentences or bullet points that provide an overview of the objective(s) of your proposed project, how you plan to do it, and the expected outcome.
  • Team: 5 or 6 sentences or bullet points that highlight team expertise as it relates to the project.
  • Budget: Example: The total cost of the project is anticipated to be $ X, with $ Y being requested from the Agency. Agency funds will be used for: $ A for personnel; $ B for operations, and $ C for broader impacts/subcontracts etc.
  • Submission history

PROJECT DESCRIPTION (1 page pdf) - please use an 11 point or higher font with one-inch margins.

  • Vision/Intellectual Merit. Describe your vision for the project.  Address scalability and the ability for the pathway to address long-term sustainability of the technology.
  • Engagement.  How will you engage appropriate constituents including ACCESS program awardees, S&E research communities, technology development partners, and host systems.
  • Activities. What steps will you take to close the knowledge gaps and technical barriers so that the proof-of-concept, prototype, or novel technology can be efficiently translated into a production-quality solution?
  • Team. Describe your team’s expertise including experience with technology development partnerships.
  • Broadening Participation.  Describe your plans to foster participation of the full spectrum of diverse talent in STEM including wider geographic participation in the CI ecosystem.
  • Evaluation. Describe your plans to demonstrate progression and support corrective actions, for each technology along the acceleration pathway.
  • Abbreviated CV or biographical sketch of the principal investigator – separate page
  • Optional - Suggest one or two names to serve on the internal review committee.

Problems with the InfoReady platform - or questions.  Email  research.development@oregonstate.edu

Notes:  First time InfoReady users will need to create an account following the directions on the InfoReady Home page for Oregon State University users at first use and then will have SSO login.  InfoReady does not save automatically, so data must be saved while applications are in process.