Attachment 06 - Additional Technical Proposal Instructions.pdf

Attachment 06: Additional Technical Proposal Instructions RFP: 75N91020R00035 Page 1 of 6

Attachment 06 Additional Technical Proposal Instructions

CISNET Consortium For Cancer Surveillance Modeling Support

Refer to SECTION L.2.b Technical Proposal Instructions of the Solicitation for a complete list of instructions. The following Additional Technical Proposal Instructions reflect additional requirements of this Request for Proposal (RFP) and are meant to provide additional instructions as well as a uniform format for Technical Proposals. The information provided and requested in these instructions should be used as a guide for formatting and preparing the Technical Proposal. This information is provided in addition to instructions provided in Section L of the Solicitation.

Offerors are required to organize and submit the Technical Proposal in the following order and as noted below, separating the sections with a page that indicates the section number. If an Item or Section is not applicable, retain the section and item number and write ‘Not Applicable’ or ‘No Response’ after the Item’s Part Name or Section’s Title.

Organization of Technical Proposal

SECTION 1 – INTRODUCTION

No Page Limitation

ITEM PART INSTRUCTIONS

1.1 Technical Proposal Cover Page See below for specific information required

1.2 Proposal Summary and Data Record

(NIH-2043)

Refer to Solicitation Section J - Attachment 10. Do not include SSN numbers on the form

1.3 Table of Contents (TOC) Include the PDF page number or working link for each Section, Part, Attachment, and Appendix

SECTION 2 – CORE INFRASTRUCTURE

Limited to 25 Pages

ITEM PART INSTRUCTIONS

2.1 Technical Approach Refer to Solicitation Sections L and M and see 2.1 below

2.2 Organizational Experience, Capabilities, Resources, and Facilities Refer to Solicitation Sections L and M and see 2.2 below

2.3 Personnel Refer to Solicitation Sections L and M and see 2.3 below

2.4 Section 508 Requirements See 2.4 below

2.5 Other Considerations Refer to Solicitation Section L and see 2.5 below

ATTACHMENTS AND APPENDICES

Limited to 50 Pages

2.6 Technical Proposal Cost Summary Refer to Solicitation Section J and see 2.6 below

2.7 Summary of Related Activites See 2.7 below

2.8 Resumes, CVs, NIH Biosketchs Scored as part of Personnel; Refer to Solicitation

Section M and see 2.8 below

2.9 Subcontractor Technical Proposal See 2.9 below

2.10 Subcontractor/Consultant

Commitment Letters See 2.10 below

2.11 Information Security

Refer to Solicitaiton Section L and see 2.11 below.

RFP: 75N91020R00035 Page 2 of 6

SUBMISSION, FORMATTING, AND PAGE LIMITATIONS

1. The Technical Proposal shall be submitted electronically to Angela Moore, Contracts Specialist, at angela.moore2@nih.gov and John Turner, Contracting Officer, at john.turner@nih.gov. No hardcopies are to be submitted.

2. Submit one Technical Proposal divided into the sections in the chart above.

3. The Technical Proposal shall be a ‘searchable’ PDF to the maximum extent practicable vs. a scanned/unreadable PDF.

4. Proposals must adhere to the page limits specified in the chart above. Pages that exceed the specified limitations will be removed prior to evaluation.

5. All proposal information and documentation required as specified in the Solicitation should be included and listed in the Table of Contents with a PDF page number or working link.

6. Proposals shall not include links to internet web site addresses (URLs) or otherwise direct readers to alternate sources of information.

7. Font size must be 12 points.

8. Margins must be at least one inch on all sides.

9. Failure to adhere to the formatting requirements above may impact whether your proposal is reviewed in its entirety.

GENERAL INSTRUCTIONS:

1. The Offeror is responsible for ensuring that all required information and documentation is included in their Technical Proposal in accordance with the Solicitation. Refer to the Statements of Work and Solicitation Section L and Section M. The following is additional information and does not include all required information and documentation for the technical proposal.

2. Offerors are apprised that for the evaluation under each technical evaluation factor, the Government shall confine its consideration to the section of an Offeror’s proposal that corresponds to that technical evaluation factor. Therefore, in the technical proposal, the Offeror should clearly mark each section to correspond with each technical evaluation factor and ensure that all information which the Offeror wants the Government to consider for that technical evaluation factor is within the designated section, or, in the case of any attachments, is clearly referenced as incorporated into the correct section. Failure to do so means that the inappropriately placed information may not be considered under the technical evaluation factor.

3. Except for Section 2.6 –Technical Proposal Cost Summary, no cost or price information shall be included within your Technical Proposal. Inclusion of cost or price information in your Technical Proposal may result in your proposal being removed from consideration.

SPECIFIC INSTRUCTIONS:

SECTION 1 – INTRODUCTION (No Page Limitation)

1.1 TECHNICAL PROPOSAL COVER PAGE. The following must be provided on the first page of the

Technical Proposal:

a. Identification of the Proposal Part (Technical Proposal);

mailto:angela.moore2@nih.gov mailto:john.turner@nih.gov

RFP: 75N91020R00035 Page 3 of 6

b. Solicitation number (75N91020R00035) and title (CISNET Consortium For Cancer Surveillance Modeling Support);

c. Name and address of Offeror;

d. Offeror’s DUNS number;

e. Date of submission;

f. Name, title, telephone number, email, and signature of person authorized to sign the proposal.

Proposals signed by an agent shall be accompanied by evidence of that agent's authority; and

g. Name, title, telephone number, email, and signature of the Principal Investigator.

1.2 PROPOSAL SUMMARY AND DATA RECORD (NIH-2043); Do not include any Social Security

Numbers (SSNs) on the form. Refer to Solicitation Section J - Attachment 10.

1.3 TABLE OF CONTENTS. Include a Table of Contents (TOC) that provides the PDF page number or working link of each proposal Section or Part that at a minimum uses the headings and subheadings that appear in the chart above. Additional subheadings may be entered at the Offeror’s discretion.

Refer to Other Considerations within Section L of the Solicitation.

SECTION 2 – TECHNICAL PROPOSAL

(Limited to 25 Pages)

Technical Proposal Section 2 shall address all requirements of Solicitation Section J – Attachment 02- Task Order 1 –Statement of Work (SOW).

For each Offeror whose proposal represents the best value to the Government after evaluation, the Government anticipates awarding an Indefinite Delivery-Indefinite Quantity (IDIQ) Base Contract and simultaneously awarding Task Order 1 – Core Infrastructure. Therefore, Section 2 of the Offeror’s Technical Proposal must include sufficient detail to allow the Government to conduct a thorough evaluation and make a Task Order award decision.

Offerors are advised to consider the Task Order 1 – Core Infrastructure Statement of Work and all reference material, attachments, the technical evaluation factors, and the Solicitation as a whole in the development of their Technical Approach. Proposals which merely restate the requirements of the Government's Statement of Work will not be eligible for award.

2.1 TECHNICAL APPROACH. Refer to Solicitation Sections L - Technical Proposal Instructions and

M - Technical Evaluation Factors.

a. Transition:

The incumbent Offeror shall propose costs for the support and maintenance of the systems for the relevant portions of the year for existing systems, proposed new systems, including overlap during the transition between older and new systems to make sure all existing content and functionality are in place before retiring the older systems. Systems that are not retired would be supported and maintained for the entire 12 months. For budgeting purposes assume that retiring systems is completed at 9 months, and new systems are in place at 6-8 months, providing several months of overlap.

Non-incumbent Offerors shall propose costs for the support and maintenance of the systems for approximately the last 6 months of the year. This will allow some overlap between the time that the systems are turned over to successor contractor and are operational at approximately 6-8 months, and the incumbent stops maintaining the old system.

RFP: 75N91020R00035 Page 4 of 6

NOTE: Knowledge Management System Development and Transfer of Historical Content must be completed prior to Sept. 1, 2021 to allow for the onboarding of new CISNET Incubator Program members.

b. Subcontracts: Offerors who propose subcontracts to perform portions of the SOW should clearly identify the specific task areas for which they plan to utilize subcontractors, as well as the method and level of integration between the prime and subcontractor(s), and the expected advantages of such an approach. The Prime Offeror’s Technical Proposal should refer to the Subcontractor’s Technical Proposal for detailed discussion. The Subcontractor’s Technical Proposal should be included under Section 3 - Attachments and Appendices. The Subcontractor’s Technical Proposal must describe each item listed above. Subcontractor Commitment Letters shall also be provided under Section 3 - Attachments and Appendices.

2.2 ORGANIZATIONAL EXPERIENCE, CAPABILITIES, RESOURCES, AND FACILITIES. Refer to Solicitation Sections L - Technical Proposal Instructions and M - Technical Evaluation Factors.

a. If Subcontractors are proposed, the Prime Offeror’s Technical Proposal should briefly discuss the Subcontractor’s organizational experience, capabilities, resources and facilities and refer to the Subcontractor’s Technical Proposal for detailed discussion. The Subcontractor’s Technical Proposal should describe and discuss each item listed above.

2.3 PERSONNEL. Refer to Solicitation Sections L - Technical Proposal Instructions and M - Technical Evaluation Factors. Describe and document the education, training, experience and expertise of the proposed personnel required to carry out the tasks of the SOW. If Subcontractors are proposed, the Subcontractor’s Technical Proposals must also include the information below and include all required documentation.

a. Key Personnel (Principal Investigator (PI)/Program Director): Describe and document evidence of education, training, expertise, and experience of the Principal Investigator/ Program Director. Include Resume, CV or NIH Biosketch for each named key personnel in Section 2 - Attachments and Appendices. Refer to Solicitation Article G Key Personnel.

b. Other (Non-Key) Personnel: Describe and document evidence of education, training, expertise and experience of proposed personnel to carry out the tasks of the SOW, including specific area of expertise to be contributed to the project. Include:

1. proposed contractor personnel

2. proposed subcontractor personnel

3. proposed consultants

4. Submit one resume, CV or NIH Biosketch for each named personnel including proposed subcontractor personnel and proposed consultants.

5. If To Be Named (TBN) or To Be Determined (TBD) positions are proposed, include a discussion of the qualifications and requirements of the position, a description of the “ideal” candidate, the plan for recruitment, and an estimate of the time required to fill the position

2.4 SECTION 508 OF THE REHABILITATION ACT OF 1973, AS AMENDED: IT

ACCESSIBILITY REQUIREMENTS. SECTION 508 CONFORMANT ELECTRONIC REPORTS

AND DELIVERABLES DISCUSSION. All Electronic Reports and Deliverables listed in Article C.2.

RFP: 75N91020R00035 Page 5 of 6 and Article F.2. Deliveries must be Section 508 conformant. Discuss Offeror’s plan to verify Section 508 Conformance and submission of Section 508 Checklist.

1. Provide an Accessibility Conformance Report (ACR) for each commercially available Information and Communication Technology (ICT) item offered through this contract. Create the ACR using the Voluntary Product Accessibility Template Version 2.1 or later, located at https://www.itic.org/policy/accessibility/vpat. Complete each ACR in accordance with the instructions provided in the VPAT template. Each ACR must address the applicable Section 508 requirements referenced in the Work Statement. Each ACR shall state exactly how the ICT meets the applicable standards in the remarks/explanations column, or through additional narrative. All "Not Applicable" (N/A) responses must be explained in the remarks/explanations column or through additional narrative. Address each standard individually and with specificity and clarify whether conformance is achieved throughout the entire ICT Item (for example - user functionality, administrator functionality, and reporting), or only in limited areas of the ICT Item.

Provide a description of the evaluation methods used to support Section 508 conformance claims.

The agency reserves the right, prior to making an award decision, to perform testing on some or all of the Offeror’s proposed ICT items to validate Section 508 conformance claims made in the

ACR.

2. Describe your approach to incorporating universal design principles to ensure ICT products or services are designed to support disabled users.

3. Describe plans for features that do not fully conform to the Section 508 Standards.

4. Describe "typical" user scenarios and tasks, including individuals with disabilities, to ensure fair and accurate accessibility testing of the ICT product or service being offered.

2.5 OTHER CONSIDERATIONS. Refer to Solicitation Section L - Technical Proposal Instructions – Other Considerations. Include as needed. Information provided will be scored under the appropriate evaluation factor.

SECTION 2 - ATTACHMENTS AND APPENDICES (Limited to 50 Pages)

2.6 TECHNICAL PROPOSAL COST SUMMARY – TASK ORDER 1 – CORE

INFRASTRUCTURE. Provide the completed form found at Solicitation Section J Attachment 07.

Include total hours and amounts.

2.7 SUMMARY OF RELATED ACTIVITIES FORMS. Refer to Solicitation Section J. Submit one completed form for each of the Key Personnel proposed. Under item “c” of the form specify the amount of effort he or she is being proposed for Task Order 1 – Core Infrastructure.

2.8 RESUMES, CVS, NIH BIOSKETCHS. Provide the Resumes, CVs, NIH Biosketchs referenced as part of your Technical Approach. Resumes, CVs, NIH Biosketchs will be scored as part of Personnel. Refer to Solicitation Section M – Evaluation Factors for Award.

2.9 SUBCONTRACTOR TECHNICAL PROPOSAL. Provide a Subcontractor Technical Proposal from each proposed Subcontractor or state “No Subcontracts Proposed”. The Subcontractor’s Technical Proposal shall be in the same level of detail and basic format as the Prime Offeror’s Technical Proposal.

https://www.itic.org/policy/accessibility/vpat

RFP: 75N91020R00035 Page 6 of 6

2.10 SUBCONTRACTOR COMMITMENT LETTERS. Provide a Signed Letter of Commitment from each proposed Subcontractor or state “No Subcontracts Proposed”. The letter must be signed by the Subcontractor’s Business Official and include all the following:

a. A statement regarding willingness to perform as a subcontractor for specific services to be provided during the period of performance;

b. What priority the work will be given and how it will relate to other work.

c. The amount of time and facilities available to this project.

d. Information on their cognizant field audit offices.

e. How rights to publications and patents are to be handled.

f. A list the Government Property (equipment) proposed or include a statement that none is proposed

2.11 INFORMATION SECURITY. Refer to Solicitation Sections L - Technical Proposal Instructions.

HHS SECURITY AND PRIVACY LANGUGAGE FOR INFORMATION AND IT PROCUREMENTS

13. HHS Security and Privacy Language for Information and Information Technology Procurements is applicable to this solicitation and the following information is provided to assist in proposal preparation.

IMPORTANT NOTE TO OFFERORS: The following information shall be addressed in a separate section of the Technical Proposal entitled "Information Security."

The Homeland Security Presidential Directive (HSPD)-12 and the Federal Information Security Management Act of 2002 (P.L. 107-347) (FISMA) requires each agency to develop, document, and implement an agency-wide information security program to safeguard information and information systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor (including subcontractor), or other source.