 Some links will work for NIAID staff only.
|
Standard Operating Procedure Table of Contents
|
|
Purpose
To enable NIAID to solicit proposals for contracts through which
the Institute purchases products or services.
Procedure
NIAID solicits proposals for contracts to procure products or services
it requires. These solicitations are called request
for proposals (RFPs). Like request
for applications (RFAs) and program
announcements (PAs) for grants, RFPs are initiatives,
which are developed and approved within the Institute and with its
advisory Council.
See the Concept Development SOP.
RFPs contain the information offerors need
to prepare proposals:
a due date, description of the work to be performed, required reports,
and a delivery schedule for products or services. NIAID advertises
its RFPs online and requires offerors to submit both electronic and
paper proposals. Contract
specialists perform most of the functions for creating and publishing
RFPs.
Publication dates are based on a phasing
plan approved by heads of NIAID's Office of Acquisitions (OA), Scientific
Review Program (SRP), the relevant program division, and the
DEA phasing
coordinator before the creation of an acquisition plan.
RFPs remain on our RFP
page until the closing date, after which we move them to the RFP
archives. For information on how offerors send in their proposals,
see the Proposal
Submission SOP.
Offerors
-
Go to FedBizOpps to check for new proposals and amendments to existing
proposals. We do not directly notify offerors of amendments. We index on our RFP page as a convenience, but RFPs and amendments may appear on FedBizOpps first.
- Follow the instructions in the RFP to submit electronic and paper proposals.
Contract Specialists
- Prepare RFP solicitation packages, using the information
from an approved RFC: statement
of work, reporting requirements, and technical
evaluation criteria. Contract specialists create RFPs based
on RFCs prepared by program staff.
-
All RFP contract files must undergo a presolicitation file review by either the NIH Board of Awards or the NIAID BOA before release.
- Get final approval of RFPs from an OA branch chief.
- Before posting send RFP documents to the Office of Initiative Development
and copy Theresa Shrader and Laura Lawton for final OID, DEA, and program review.
- After receiving proposals, notify SRP, so review staff can begin
preparing for technical evaluation.
Project Officers
- Review RFPs before approval by OA branch chief.
OA Branch Chiefs
- Give final approval of RFPs before they are published.
OA Procurement Technicians
Scientific Review Officers
- Oversee the peer
review of proposals responding to NIAID RFPs.
Contacts
See the OA
staff listing for contract specialists.
Contact for NIAID Staff
See the SRP staff
directory for peer review contacts.
If you have knowledge to share or want more information on this topic, email deaweb@niaid.nih.gov with the title of this page or its URL and your question or comment. Thanks for helping us clarify and expand our knowledge base.
Links
Contract
Deliverables and Reporting Requirements SOP
Contract Funding
and End-of-Year Timelines and Processes SOP
Mandatory Qualification Criteria for Offerors SOP
FAR
Part 15.2, Solicitation and Receipt of Proposals
Independent
Government Cost Estimate SOP
NIH
Directory of RFPs Listed by Institute
NIH
Manual 6315-1, Initiation, Review, Evaluation, and Award of Research & Development (R&D) Contracts
Scientific
Initiative Management System (SIMS) SOP
Specification Package -- Template with Instructions for Broad Agency Announcement
Withdrawal of a Nonresponsive Application SOP |
