NOIS2 RFP Document Change Log.pdf

Enclosure 1

NOIS2 Request for Proposal (RFP) Document Change Log

Section DRFP Page

From Final

RFP

Page

To

Section 1 Addendum to 52.212- 4 Contract Terms and Conditions

11 52.227-11 PATENT RIGHTS- OWNERSHIP BY

THE CONTRACTOR (MAY 2014) as modified by 1852.227-11 (APR 2015)

N/A Deleted

Section 1 Addendum to 52.212- 4 Contract Terms and Conditions

11 52.227-14 RIGHTS IN DATA--GENERAL (MAY

2014) ALTERNATE II (DEC 2007)

8 Deleted: Alternate II (DEV 2007) Added “as modified by 1852.227-14”

Section 1 Addendum to 52.212- 4 Contract Terms and Conditions

N/A 9 Added: 52.227-16 ADDITIONAL DATA

REQUIREMENTS (JUN 1987)

Section 1 Addendum to 52.212- 4 Contract Terms and Conditions

12 1852.227-70 New Technology-Other than a Small Business Firm or Nonprofit Organization

9 Deleted

Section 1

FAR 52.216-22

Indefinite Quantity Paragraph (d)

15 The contract shall govern the Contractor’s and Government’s rights and obligations with respect to that order to the same extent as if the order were completed during the contract’s effective period; provided, that the Contractor shall not be required to make any deliveries under this contract after 12 months.

12 The contract shall govern the Contractor’s and Government’s rights and obligations with respect to that order to the same extent as if the order were completed during the contract’s effective period; provided, that the Contractor shall not be required to make any deliveries under this contract- outside of the bona fide need rules and principles of federal appropriations law.

Section 1 Addendum to 52.212- 4 Contract Terms and Conditions

N/A 14 Added: SUPPLEMENTAL TASK ORDERING

PROCEDURES

Task Orders will be competed unless otherwise specified.

One or more Task Orders may be issued during the ordering period of this contract. Task Orders will be issued in accordance with FAR

16.505. Upon receipt of the contractors’

proposals, the Government will review each proposal based on the specific evaluation criteria identified in the RFTP. The evaluation criteria, additional evaluation details, may vary by RFTP, based on the specific requirements.

The proposed task order price will always be considered in competitive task order evaluations.

Section 2 Contract Terms and Conditions Required to Implement Statutes or Executive Orders

20 52.212-5 CONTRACT TERMS AND

CONDITIONS REQUIRED TO IMPLEMENT

STATUTES OR EXECUTIVE ORDERS—

COMMERCIAL ITEMS (AUG 2019)

17 52.212-5 CONTRACT TERMS AND CONDITIONS

REQUIRED TO IMPLEMENT STATUTES OR

EXECUTIVE ORDERS—COMMERCIAL ITEMS

(OCT 2019)

Section 2 Contract Terms and Conditions Required to Implement Statutes or Executive Orders

24 __ (48) 52.225-5, Trade Agreements (Aug 2018) (19 U.S.C. 2501, et seq., 19 U.S.C. 3301 note).

21 _X_ (48) 52.225-5, Trade Agreements (Oct 2019) (19 U.S.C. 2501, et seq., 19 U.S.C. 3301 note).

Section 3 Statement of Work

3.1 Introduction

29 Since 2011, NASA’s Center of Excellence for Collaborative Innovation (CoECI) has been working to mature its experience primarily focused on using Federal procurement authority to work with companies who conduct competitions to deliver solutions or stimulate innovation. Across the agency, however, interest continues to grow in the broader use of crowdsourcing as a tool to help NASA meet its mission. As a result, CoECI is seeking to expand the capabilities and expertise it provides to NASA, as well as other federal agencies, in the successful use of crowdsourcing.

26 Since 2011, NASA’s Center of Excellence for Collaborative Innovation (CoECI) has been maturing its experience with using Federal procurement authority to work with companies who conduct competitions and rely on other crowdsourcing approaches to deliver solutions or stimulate innovation. Across the agency, interest continues to grow in the broader use of crowdsourcing as a tool to help NASA meet its mission. NASA defines crowdsourcing as a method to obtain needed services, ideas, or content by soliciting voluntary contributions from a group of individuals or organizations, especially from an online community. As a result, CoECI is seeking to expand the capabilities and expertise it provides to NASA, as well as other federal agencies, in the successful use of crowdsourcing.

3.2 Scope of Work

Paragraph (b)

29 b. Crowd-Based Freelance Projects:

Freelance is the process to identify and manage individuals (members of the crowd/community) best equipped to work on and deliver solutions and/or stimulate innovation.

26 b. Crowd-Based Freelance Projects: Freelance is the process to select and manage individuals, teams, and/or talent pools (members of the crowd/community) best equipped to work on and deliver solutions and/or stimulate innovation.

3.2.1 End Products

and Services Paragraph (g)

30 g. Public Engagement Campaign - This includes, but is not limited to, executed campaigns, programs, or events that engage the public in various technical aspects of NASA’s programs to provide task support, promote STEM education, and/or public interest/support.

27 g. Public Engagement Campaign - This includes, but is not limited to, executed campaigns, programs, or events that engage the public in various technical aspects of Government programs to provide task support, promote STEM education, and/or public interest/support.

Section 3 Statement of Work

3.2.1 End Products

and Services

30 The Contractor shall perform all management functions, including technical and business management, necessary to plan, implement, track, report and deliver the required products and services described

27 The Contractor shall perform all management functions, including technical and business management, necessary to plan, implement, track, report and deliver the required products and services described in the SOW and more specifically in each Request for Task Plan.

https://acquisition.gov/content/part-52-solicitation-provisions-and-contract-clauses#i1053648 http://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title19-section2501&num=0&edition=prelim http://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title19-section3301&num=0&edition=prelim in the SOW and more specifically in each task order.

3.5 Task Order

Execution

31 e. Coordinate with the Government on the specific Intellectual Property (IP) rights/licensing for any delivered product/solutions required by the task order.

28 e. Comply with the specific Intellectual Property (IP) rights/licensing for any delivered product/solutions identified in the task order.

3.6 Reporting

Requirements

32 Typical task order reporting includes program reviews, periodic status reports, and a project close-out report.

29 Typical task order reporting includes specified metrics, program reviews, periodic status reports, and a project close-out report.

Section 4 Solicitation Provisions

55 52.204-17 OWNERSHIP OR CONTROL OF

OFFEROR (JUL 2016)

50-

Changed from IBR to Full Text

Section 4 Solicitation Provisions

55 52.209-2 PROHIBITION ON CONTRACTING

WITH INVERTED DOMESTIC CORPORATIONS-

-REPRESENTATION (NOV 2015)

52 Changed from IBR to Full Text

Section 5 Instructions to Offerors 5.1

59 The entire proposal is due by TBD at 1:30 p.m. Eastern Time. Late proposals will not be accepted.

56 The entire proposal is due by January 10th at 1:30 p.m. Eastern Time. Late proposals will not be accepted.

Section 5 Instructions to Offerors 5.1

66-

All offerors shall follow FBO.gov usage requirements as defined in the Vendor User Guide posted on the home page of FBO.gov.

The Government is not responsible for any failure attributable to the transmission or receipt of documents submitted using electronic means, including the missing of any established deadlines. It is the Offeror’s responsibility to submit correct proposal package(s) and to verify correct submission by using the instructions provided in Federal Business Opportunities Vendor User Guide.

Although FBO.gov sends an email upon submission, the email receipt from FBO.gov shall not constitute record of proper bid submission. It is the Offeror’s responsibility to confirm the Government’s receipt of transmitted information matches the information submitted by the Offeror per the instructions in the FBO Vendor User Guide.

NASA Open Innovation Services 2 (NOIS2)

80JSC020R0030

(ii) Offerors are advised that, as stated in the FBO Vendor User Guide, file sizes over 100MB may experience system difficulties.

All the proposal files may be compressed (zipped) into one file titled “SOLICITATION#_VENDORNAME.zip” or uploaded individually. The electronic proposal shall contain all information

56 Proposals are to be submitted using the Governmentwide Point of Entry (GPE), as defined in FAR 2.101. Failure to submit a complete electronic proposal by the due date and time specified for this RFP shall result in the proposal being considered late, and shall be handled in accordance with FAR 15.208(b).

All Offerors shall follow usage requirements as outlined in the GPE. The Government is not responsible for any failure attributable to the transmission or receipt of documents submitted using electronic means, including the missing of any established deadlines. It is the Oferor’s responsibility to submit correct proposal package(s) and to verify correct submission by using the instructions provided at the GPE. Any notification received from the GPE does not constitute record of proper submission. It is the Offeror’s responsibility to confirm the Government’s receipt of transmitted information matches the information submitted by the Offerors per the instructions at the GPE.

Offerors are advised to take note of any stated file size limitations, or other warnings, that may result in system difficulties. All the proposal files may be compressed (zipped) into one file titled “SOLICITATION#_VENDORNAME.zip” or uploaded individually. The electronic proposal shall contain all information required by the required by the solicitation to be determined responsive. Files shall not have password protection, encryption, or any access or viewing restrictions.

solicitation to be determined responsive. Files shall not have password protection, encryption, or any access or viewing restrictions.

Offerors

65 (8) Acknowledgment of Solicitation Amendments;

Acknowledgment of Solicitation Amendments;

Amendments to the solicitation will be posted on beta.sam.gov and the NOIS2 acquisition website, via Standard Form 30 (SF30) Amendment of Solicitation/Modification of Contract. Block 11 of the SF30 requires offeror acknowledgement of receipt of the amendment by one of the following methods:

(a) by completing items 8 and 15 of the SF30 and returning a copy of the amendment to the Contracting Officer; (b) by acknowledging receipt of the amendment on each copy of the offer submitted; or (c) by separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. Failure to acknowledge solicitation amendments may result in rejection of offer.

67 The Offeror shall enter, in the block with its name and address on the cover page of its offer, the annotation “Unique Entity Identifier” followed by the unique entity identifier that identifies the Offeror's name and address.

The Offeror shall enter, in the block with its name and address on the SF1449 of its offer, the annotation “Unique Entity Identifier” followed by the unique entity identifier that identifies the Offeror's name and address.

Section 5

68 (b) All non-copyrighted technical documentation which is incorporated directly by reference in this solicitation may be obtained from the NOIS2 Technical Reference Library which is available online at FedBizOpps.Gov (FBO.Gov). In order to access the FBO.Gov Technical Library, refer to the FBO.Gov Vendor Guide at:

https://www.fbo.gov/. The NOIS2 acquisition website at:

https://procurement.jsc.nasa.gov/nois2/ includes a link to the technical library.

58 (b) All non-copyrighted technical documentation which is incorporated directly by reference in this solicitation may be obtained from the NOIS2 Technical Reference Library which is available online at beta.sam.gov The NOIS2 acquisition website at: https://procurement.jsc.nasa.gov/nois2/ includes a link to the technical library.

Offerors

60 Text in diagrams, charts, tables, artwork, and photographs shall be no smaller than 12 point text size.

59 Text in diagrams, charts, tables, artwork, and photographs shall be no smaller than 10 point text size.

Section 5

60 The electronic proposal shall be prepared and submitted in Microsoft Office® 2016 applications (Word and Excel). Further, the Microsoft Excel spreadsheets shall be

59 The electronic proposal shall be prepared and submitted in a Microsoft Office® Word application.

https://procurement.jsc.nasa.gov/nois2/ https://procurement.jsc.nasa.gov/nois2/ submitted in Microsoft Excel format, not in a scanned Microsoft Word or Adobe PDF file.

Section 5

61 Be sure to apply all appropriate markings, including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-5, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

60 Be sure to apply all appropriate markings, including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-5, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. The electronic cover sheet will not count toward the page limitations.

Section 5

61 A Cross Reference List shall be submitted in each Volume for that particular volume.

60 A Cross Reference List shall be submitted in each Volume for that particular volume. The Cross Reference List will not count toward the page limitations.

59 QUESTIONS REGARDING THIS SOLICITATION

MUST BE PRESENTED IN WRITING and shall be submitted electronically to the above e-mail address by October 25th , 4:00PM Central Time, in order that answers may be obtained and disseminated in a timely manner, since it is not expected that the proposal submission date will be extended.

60 13. QUESTIONS REGARDING THIS

SOLICITATION MUST BE PRESENTED IN

WRITING and shall be submitted electronically to the above e-mail address by December 10th , 4:00PM Eastern Time, in order that answers may be obtained and disseminated in a timely manner, since it is not expected that the proposal submission date will be extended.

Section 5

59 A technical description of the items being offered in sufficient detail to evaluate compliance with the requirements in the solicitation. This may include product literature, or other documents, if necessary.

This procurement will be conducted using technically acceptable baseline requirements (Acceptable/Unacceptable). Technical acceptability is discussed in detail below.

60 A technical description of the items being offered in sufficient detail to evaluate compliance with the requirements in the solicitation. This procurement will be conducted using technically acceptable baseline requirements (Acceptable/Unacceptable/Potentially Acceptable). Technical acceptability is discussed in detail below.

60 Specific Technical Understanding and Resources - The Offeror is required to demonstrate its understanding of the requirements and propose the specific resources needed to successfully perform the requirements of this Contract. The offeror’s response to this section should be consistent with other portions of the offeror’s proposal.

61 Specific Technical Understanding and Resources - The Offeror is required to demonstrate its understanding of the requirements to successfully perform the requirements of this Contract. The offeror’s response to this section should be consistent with other portions of the offeror’s proposal.

Section 5

64 7. Period of performance

63 g. Period of performance: Provide performance information on current contracts or contracts that ended within 3 years from the date of the NOIS2 original solicitation. The three year period is based on the past performance contract’s period of performance end date.

Section 5 60 a. An overview of the business model and the specific crowdsourcing method or

61 a. An overview of the business model and the specific crowdsourcing method or methods methods used to successfully deliver the products and services outlined in the SOW.

used to successfully deliver the products and services outlined in Section 3.2 of the SOW.

Offerors 5.3 Technical Understanding of Requirements

63 c. A detailed description of how each of the offeror’s specific method and/or methods described meets each of the elements listed in the SOW under Section 3.0.

61 c. A detailed description of how each of the Offeror’s specific crowdsourcing method and/or methods required by Section 3.2 of the SOW meets each of the elements listed in the SOW under Section 3.5 Task Order Execution.

60 Select the single most representative end product or service listed in Section 3.2.1 of the SOW that the Offeror can successfully deliver and provide a detailed project plan that demonstrates the Offeror’s standard delivery approach.

61 Select the single most representative methodology identified in Section 3.2 of the SOW along with the single most representative end product or service listed in Section 3.2.1 of the SOW that the Offeror can successfully deliver and provide a detailed project plan that demonstrates the Offeror’s standard delivery approach.

Section 5

d. A full lifecycle firm-fixed price to conduct the project. This shall include, but not be limited to, the following:

Individual and total compensation of crowd participants Management and execution fees External entity expenses (e.g., data hosting or computational services, etc.)

Any other resources required to complete the project

N/A Removed entire paragraph

Section 5 Instructions to Offerors Responsibility Considerations- Volume II C. Past Performance Record

64-

Submit information on contracts that you consider relevant in demonstrating your ability to perform the proposed effort. The submission shall include rationale supporting your assertion of relevance. This submission shall clearly detail what portions of the Statement of Work, the prime, major/minor subcontractors, teaming partner, and/or joint venture partner are responsible for and the specific resources (workforce, management, facilities, or other resources) to be employed and relied upon to perform the proposed effort. If the Past Performance information includes data on any affiliated company, division(s), business units, segments, or other organizations of your company, then provide a narrative to address what they will be responsible for and/or proposing to do and the specific resources (workforce, management, facilities, or other resources) to be employed and relied upon, such that said parent et al will have meaningful involvement in contract performance.

N/A Removed entire paragraph:

Submit information on contracts that you consider relevant in demonstrating your ability to perform the proposed effort. The submission shall include rationale supporting your assertion of relevance. This submission shall clearly detail what portions of the Statement of Work, the prime, major/minor subcontractors, teaming partner, and/or joint venture partner are responsible for and the specific resources (workforce, management, facilities, or other resources) to be employed and relied upon to perform the proposed effort. If the Past Performance information includes data on any affiliated company, division(s), business units, segments, or other organizations of your company, then provide a narrative to address what they will be responsible for and/or proposing to do and the specific resources (workforce, management, facilities, or other resources) to be employed and relied upon, such that said parent et al will have meaningful involvement in contract performance.

Section 5 Instructions to Offerors

(6) Model Contract- Volume III

65 Contract Section 3: Representations and certifications shall be completed and submitted with this volume in accordance with provisions Offeror Representations and Certifications Commercial Items (FAR 52.212- 3)

63 Contract Section 3: No fill-ins. Please attach Section 3 in its entirety.

Section 5 Instructions to Offerors

(6) Model Contract- Volume III

65 Fill in Reps and Certs

63 Representations and certifications shall be completed and submitted in this volume in accordance with provisions found in Section 4 Solicitation Provisions: Offeror Representations and Certifications Commercial Items (FAR 52.212-3), also provide fill-ins for 52.204-17, 52.209-2, 52.204-24, 52.209-7, 52.209-12

Section 5

65 (7) A completed copy of the representations and certifications at FAR 52.212-3 (see FAR52.212-3(b) for those representations and certifications that the offeror shall complete electronically);

N/A Removed entire paragraph:

(7) A completed copy of the representations and certifications at FAR 52.212-3 (see FAR52.212-3(b) for those representations and certifications that the offeror shall complete electronically);-

65 (9) Past performance information; [Addenda] In accordance with FAR 15.304(c)(iii) Past Performance will not be included as an Evaluation Factor, but rather be requested and evaluated under Responsibility Requirements in accordance with FAR 9.104- 3.

N/A Removed entire paragraph:

(9) Past performance information; [Addenda] In accordance with FAR 15.304(c)(iii) Past Performance will not be included as an Evaluation Factor, but rather be requested and evaluated under Responsibility Requirements in accordance with FAR 9.104-3.

Section 5

65 (10) If the offer is not submitted on the SF 1449, include a statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation. Offers that fail to furnish required representations or information, or reject the terms and conditions of the solicitation may be excluded from consideration.

N/A Removed entire paragraph:

(10) If the offer is not submitted on the SF 1449, include a statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation.

Offers that fail to furnish required representations or information, or reject the terms and conditions of the solicitation may be excluded from consideration.

Section 5

66 (ii) [Addenda] Modifications will not be

N/A Removed entire paragraph:

(ii) [Addenda] Modifications will not be

Section 6 Evaluation Streamlined Procurement

69 (b) The remaining proposals will be evaluated against the Technical Acceptability Factor. All “Acceptable” proposals will be further evaluated against Responsibility. At

64 The remaining proposals will be evaluated against the Technical Acceptability Factor. At the completion of the evaluation against Technical Acceptability, the Government may

Evaluation Factors for Award Paragraph (b) the completion of the evaluation against the Responsibility, the Government may elect to award a contract without discussions to the technically “Acceptable” responsible offeror(s), who represents the best value as described below.

elect to award a contract without discussions to the technically “Acceptable” responsible Offeror(s).

Procurement Evaluation Factors for Award Paragraph (c)

69 (c) The Government may also elect to establish a competitive range and conduct discussions.

64 The Government may also elect to establish a competitive range and conduct discussions.

Although an Offeror may receive a rating of “Acceptable” or “Potentially Acceptable”, it does not guarantee that discussions will be held, or that the offeror will be automatically included in the competitive range, if discussions are held. Discussion, if held, will only be held with the most highly rated Offerors(s).

Procurement Evaluation Factors for Award Paragraph (d)

69 Ratings of “Acceptable” and “Unacceptable are defined below:

64 Ratings of “Acceptable”, “Unacceptable, and “Potentially Acceptable” are defined below:

Procurement

69 64 “Potentially Acceptable” Rating – A proposal will be rated “Potentially Acceptable” under the Technical Acceptability Factor and Model Contract Volume, when after the initial evaluation, the proposal does not fully meet the definition for an “Acceptable” or “Unacceptable” rating and the Government anticipates that additional information obtained during discussions could result in a proposal rating of “Acceptable”.

Procurement

69-

In accordance with Procurement Class Deviation 18-02, the Government will not be evaluating price as an evaluation for contract award. Procurement Class Deviation 18-02 amends 10 U.S.C. 2305(a)(3) to change the requirement regarding the consideration of price or cost to the Government as a factor in the evaluation of proposals for multiple-award task order contracts. The Government will be evaluating the labor and non-labor resources proposed in the Technical Acceptability Volume for reasonableness and consistency with the Technical content. The Government intends to make an award to each and all qualifying offerors. A qualifying offeror is an offeror that is determined to be a responsible source, submits a technically acceptable proposal that conforms to the

65 In accordance with Procurement Class Deviation 18-02, the Government will not be evaluating price as an evaluation factor.

Procurement Class Deviation 18-02 implements section 825 of the National Defense Authorization Act (NDAA) for Fiscal Year (FY) 2017 (Pub. L. 114-328) that amends 10 U.S.C. 2305(a)(3) to change the requirement regarding the consideration of price or cost to the Government as a factor in the evaluation of proposals for multiple-award task order contracts. Price will be considered as one of the factors in the selection decision for each task order under the contract, in accordance with FAR 16.505(b)(1)(ii)(E). The Government intends to make an award to each and all qualifying Offerors.

requirements of the solicitation, and the contracting officer has no reason to believe would be likely to offer other than fair and reasonable pricing.

Section 6 Evaluation Streamlined Procurement

70 (e) If discussions are held, offeror(s) will be provided an opportunity to submit a Final Proposal Revision (FPR) for the Government’s final evaluation.

65 5. If discussions are held, offeror(s) will be provided an opportunity to submit a Final Proposal Revision (FPR) for the Government’s final evaluation. For the final evaluation, proposals will be rated as “Acceptable” or “Unacceptable”, and there will be no “Potentially Acceptable” ratings.

Section 6 Evaluation Streamlined Procurement

70 The Government will carry out the evaluation activities and report to the Source Selection Authority (SSA), who is responsible for making the source selection decision. For those Offeror(s) who are determined to be “Acceptable” under the Technical Acceptability Factor, and whose proposal conforms to the requirements of the solicitation, an evaluation will be made of the contractor’s Responsibility. The Government intends to make an award to each and all qualifying offerors.

65 6. The Government will carry out the evaluation activities and report to the Source Selection Authority (SSA), who is responsible for making the source selection decision. A qualifying Offerors is one who is determined to be a responsible source, submits a technically “Acceptable” proposal under the Technical Acceptability Factor, whose proposal conforms to the requirements of the solicitation, and provides the Contracting Officer with no reason to believe it would be likely to offer other than fair and reasonable pricing. The Government intends to make an award to each and all qualifying Offerors.

Section 6 Evaluation Streamlined Procurement

70 (g) The Government will award to the offeror(s) whose proposal offers the best overall value to the Government that meets all solicitation requirements and is determined responsible in accordance with FAR 9.104, Standards. Past Performance will be evaluated under Responsibility. Further, the OCI information will also be used to determine eligibility for award.

N/A Removed entire paragraph

Section 6 Evaluation Streamlined Procurement Evaluation Factors

70 6.3 Responsibility Factor (Volume II) 65 6.2 Responsibility Considerations (Volume II)

Procurement Evaluation Factors for Award

71 B. Responsibility Information The Contracting Officer will evaluate this information for the offerors as a part of the proposal evaluation process.

66 2. Responsibility Information The Contracting Officer will evaluate this information for the Offerors as a part of the CO’s affirmative determination of responsibility.