RFI - ATTACHMENT 3 - SAMP INST TO OFFER - TECH APPCH (02122024).pdf

ATTACHMENT 3

INSTRUCTIONS TO OFFERORS (ABBR SECTION)

General Instructions

**As stated, all information within is for RFI purposes. No contract will be awarded pursuant to this RFI. Read all information within for additional information. **

As part of the RFI, the Government is seeking to obtain concerns or questions related to the PWS, the instructions to offerors (technical approach), and evaluation criteria. Following is an abbreviated section of the Instructions to Offerors. The instructions are related only to the Technical Approach, as related back to the PWS. Reminder that this is not a solicitation and proposals are not being accepted.

All sections of an Offeror’s proposal would need to make direct reference to the PWS specification paragraph numbers. A proposed technical approach (and methods) must be presented in a clear and logical order based on the offerors understanding of the instructions (technical approach). Statements such as “will comply”, “meets the intent of”, or “we intend to meet the requirements” and the like, would not suffice for evaluation purposes.

ESTIMATED LEVEL OF SUPPORT

Below is a list of estimated figures to assist Offerors with assessing their ability to execute the magnitude of the requirements for the resulting contract. The actual numbers would fluctuate each fiscal year based on appropriations, number of research programs to be managed, number of Funding Opportunity Announcements (FOAs), Program Announcements (PAs), and Broad Agency Announcements (BAAs) released, and complexity of the funding mechanism.

Estimates (each fiscal year):

- Anticipated number of FOAs: 120-150

- Anticipated number of pre-applications to extramural/intramural PAs: 15,000-20,000 Anticipated number of full research applications to extramural/intramural PAs: 8,000-12,000

- Anticipated number of pre-applications to intramural solicitations: 650-800 Anticipated number of research applications to intramural solicitations: 300-500 Anticipated number of BAA’s: 5-10

- Anticipated number of pre-applications submitted to BAA’s: 2,400-3,000 Anticipated number of full applications submitted to BAA’s: 550-750

**TECHNICAL APPROACH**

Any Offeror would be required to submit a technical approach that demonstrates techniques, methods, and processes that would successfully accomplish the objectives specified in the above referenced PWS (specifically “how” the objectives will be accomplished), namely:

(a) Providing helpdesk support (refer to PWS section(s) 4.9.2.5)

(b) Conducting application/proposal compliance (refer to PWS section(s) 4.2 - 4.2.8.3)

(c) Recruiting appropriate subject matter experts (refer to PWS section(s) 4.5.5.10, 4.5.5.11)

(d) Conducting in person peer review panels (refer to PWS section(s) 4.5.5, 4.5.5.1)

(e) Conducting virtual peer review panels (refer to PWS section(s) 4.5.5, 4.5.5.2)

(f) Conducting online-only peer review panels (refer to PWS section(s) 4.5.5, 4.5.5.3)

(g) Conducting online individual peer reviews (refer to PWS section(s) 4.5.5., 4.5.5.4)

(h) Evaluating scientific research applications (refer to PWS section(s) 4.5.6)

(i) Completing and delivering summary statements (refer to PWS section(s) 4.5.6.8, 4.6.1 - 4.6.3)

(j) Delivering data and files and meeting the highest level of data integrity, consistency, and accuracy (refer to PWS section(s) 4.6.4- 4.6.4.3, 4.9.2.7)

(k) Providing training to peer reviewers (refer to PWS section(s) 4.7.1 – 4.7.3)

ATTACHMENT 3

INSTRUCTIONS TO OFFERORS (ABBR SECTION)

(l) Completing all peer review logistical requirements (refer to PWS section(s) 4.8.1 - 4.8.6.6)

(m) Providing program support in the area of funding opportunity setup and application receipt/processing in eBRAP (refer to PWS section(s) 4.9.2.1, 4.9.2.3, 4.9.2.4, 4.9.3.10 -4.9.3.12)

(n) Providing a contractor-owned, contractor-operated electronic system as evidenced by a demonstration video (see additional submission instructions below). (refer to PWS section(s) 4.4)

VIDEO SUBMISSION

Video submission shall address the following areas:

• Individual reviewer views and functionality

• Panel review scoring process and views

• Program staff access and functionality

• Demonstrations of any differences in review modality (in person, virtual, teleconference)

• Reviewer demographics and panel makeup views

• Reporting/Import/export capabilities

• Access control by user role

• Conflict of interest identification/restrictions functionality

• Data protections and Security functionality

Offerors shall submit a Transition-In Plan for 90 days of incoming transition support from contract to contract.

The Offeror shall submit this plan within Volume II. The transition-in plan is not subject to the page limitations.

The Offeror shall submit a Transition-In Plan that demonstrates full performance (as outlined by the tasks in the PWS) on the day after the end of the transition-in period. The Transition-In Plan shall address the following tasks:

- Obtaining Ft. Detrick ID and Common Access Card (CAC) for appropriate personnel, scheduling and completing Government required training and certification in accordance with the training requirements listed in PWS Section 3.2;

- Orientation phase and program to introduce Government personnel, programs, and users to the Contractor's team, tools, methodologies, and business processes;

- Coordination with Government representatives, Review, evaluation, and transition of incumbent support services;

- Transition of historic data to new Contractor system;

- Transfer of hardware warranties and software licenses (if applicable);

- Transfer of all necessary business and/or technical documentation;

- Distribution of Contractor purchased Government owned assets, including facilities, equipment, furniture, phone lines, computer equipment, etc.;

- Transfer of Government Furnished Equipment (GFE) and Government Furnished Information (GFI), and GFE inventory management assistance.

(End of Instructions to Offerors)