NOIS2 PreProposal-Conference-Slides-.pdf

Welcome to the Johnson Space Center NASA Open Innovation Services 2 (NOIS2) Pre-Proposal

Conference

December 10th, 2019 Virtual via Telecom & Skype

2:00 PM Central Time

Agenda

Topic Presenter

Welcome Jessica Miller

Welcome Lynn Buquo

Welcome Richard Slater

Procurement Overview Marta Choma

Current Contract Overview Marta Choma

Technical Overview Lynn Buquo

Overview of NOIS2 RFP Marta Choma

Welcome

Jessica Miller, NASA BH/Projects Procurement Office

Deputy Manager Office of Procurement

Welcome to the NOIS2 Pre-Proposal Conference

Lynn Buquo, NOIS2 Chair

Welcome

Richard Slater, NASA Industry Assistance Office

Industry Assistance Office Contact Information

• Main phone number:

(281) 483-4512

• Richard Slater Small Business Specialist

• Robert Watts Small Business Specialist

• Monica Craft Small Business Specialist

• All emails should be sent to: jsc-industry-assistance@mail.nasa.gov

• Location:

Building 1, Suite 453

• Address:

NASA Johnson Space Center, Industry Assistance Office Mail Code: BA 2101 NASA Parkway Houston, TX 77058-3696

Procurement Overview

Marta Choma Contracts Specialist

Disclaimer

• These slides are not to be interpreted as a comprehensive description of the procurement strategy or requirements in the RFP.

• To the extent there are any inconsistencies between this briefing and the RFP, the RFP will govern.

Purpose of Pre-Proposal Conference

• The purpose of this Pre-Proposal Conference is to help industry understand the Government’s requirements.

• Questions:

• Verbal questions will not be entertained during the conference.

However, written questions can be submitted to the Contracting Officer, Shine Lin, and Contracts Specialist, Marta Choma, before the specified deadline.

• The deadline for submitting questions regarding the RFP is 4:00 PM Eastern Time, Tuesday December 10th 2019 .

• Reminder that proposals are due January 10th 2020 at 1:30 PM Eastern Time.

• Official responses to written questions received by the Contracting Officer will be posted to both beta.sam.gov and the NOIS2 procurement website.

Source Selection Authority and Acquisition Team Members

• Source Selection Authority

• Stephen Janney, Projects Procurement Office Manager

• Acquisition Team

• Lynn Buquo

• Steve Rader

• Ryon Stewart

• Marta Choma

Points of Contact

• Contracting Officer:

Shine Lin shine.lin@nasa.gov

• Contract Specialist:

Marta Choma marta.choma@nasa.gov

• NOIS2 web address:

https://procurement.jsc.nasa.gov/nois2/

Ombudsman

Ombudsman (NFS 1852.215-84): “…before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the Contracting Officer for resolution … If resolution cannot be made by the Contracting Officer, interested parties may contact the installation ombudsman whose name, address, telephone number, and email address may be found at:

http://prod.nais.nasa.gov/pub/pub library/Omb.html

Current Contract Overview

• Contract Number: NNJ15HK30B-39B

• Prime Contractors:

• Appirio, Inc.

• HeroX PBC

• InnoCentive, Inc.

• Kaggle, Inc.

• Luminary Labs, LLC.

• Ninesigma North America, Inc.

• IDEO LP

• Patexia, Inc.

• The Common Pool, LLC.

• Tongal, Inc.

• Contract Type: Multiple-Award, Fixed- Price (FP) Indefinite-Delivery, Indefinite- Quantity (IDIQ) contract

• Period of Performance: June 4th 2015 - June 3rd 2020

Technical Overview

Lynn Buquo, CoECI Manager & NOIS2 PDT Chair

The Center of Excellence for Collaborative Innovation Supporting the NOIS2 Acquisition

Lynn Buquo Manager

Houston, TX

Carolyn Woolverton Interagency Agreements

Houston, TX

Steve Rader Deputy Manager Houston, TX

Ryon Stewart Open Innovation Development Houston, TX

The Organization

For more information, go to: http://www.nasa.gov/offices/COECI/ 15

Colleen King Interagency Agreements Houston, TX

NASA

Tournament

Lab Challenges by the

Numbers 94% Successful

350+ Challenges

83% Result in Cost Savings

NTL Challenge Metrics

NTL Challenge Metrics

*The following charts are used to illustrate COECI workload history. Please note, they are no prediction of the future, and are not intended as such. 18

NASA Open Innovation Services Current Task Order Process/Timeline

Where We Are

With NOIS, the Government has been highly successful at maturing the use of crowdsourcing, primarily in the form of public contests. Those contests have been a sound method to acquire innovative, often novel, solutions to organizational needs.

The Government is aware other crowdsourcing models exist for finding solutions and driving innovation beyond just public contests.

“Skate to where the puck is going to be, not where it has been.”

- Wayne Gretzky

Where We Are Going

• With NOIS2, the Government intends to expand access to a broader set of tools, still focused on the use of crowdsourcing, but not limited to public contests.

• As a result, NASA is seeking to expand the capabilities and expertise it provides to the agency, as well as other federal agencies, in the successful use of crowdsourcing.

• The NOIS2 Statement of Work is focused on the delivery of end products and services through the use of crowdsourcing.

• The SOW does not stipulate the type of crowdsourcing.

Overview of NOIS2 Request For Proposal (RFP)

80JSC020R0030

Marta Choma Contract Specialist

General Information: RFP Structure

• The RFP contains 6 Sections

• The information contained in the RFP and amendments take precedence over the information provided this conference.

• Please continue to monitor beta.sam.gov and the NOIS2 procurement websites for any updates, amendments to the RFP, schedule changes, etc.

SECTION 1 SF 1449, CONTRACT CLAUSES

SECTION 2 CONTRACT TERMS AND CONDITIONS REQUIRED TO

IMPLEMENT STATUTES OR EXECUTIVE ORDERS

SECTION 3 CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION 4 SOLICITATION PROVISIONS

SECTION 5 INSTRUCTIONS TO OFFERORS

SECTION 6 EVALUATION

Amendments to the RFP

• The Contracting Officer may make Amendments to the RFP

• 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.

• Acknowledgment of Solicitation Amendments:

• 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.

General Information: Contract Type

• Competition:

• Full and Open Competition at contract solicitation.

• The CO will have the ability to make small business set aside determinations at the task order (TO) level.

• NAICS Code is 541990 and Size Standard $15M.

• Period of Performance:

• 6/04/2020- 6/03/2025

• Type of Contract:

• Multiple Award contract with the ability to issue Firm-Fixed-Price (FFP) Indefinite

Delivery/ Indefinite Quantity (IDIQ) TOs.

• After the NOIS2 contracts are awarded, work on the contracts will be accomplished through the issuance of IDIQ Task Order solicitations, in accordance with NOIS2 1852.216-80 Task Ordering Procedures.

• Task Order solicitations will be competed among the successful Offerors, unless otherwise stated.

• JSC 52.216-90 IDIQ Minimum and Maximum Ordering Limits

• Each contractor is guaranteed a minimum amount under the contract of $3,000.

• The maximum cumulative contract Not to Exceed (NTE) amount which may be ordered under this contract across all TOs is $24,900,000.00

• The Task Ordering Procedure is described in Clause NFS 1852.216-80, Task Ordering Procedure.

• Only the Contracting Officer may issue Task Orders (TO’s).

• The CO will submit a Request for Task Plan (RFTP) that will contain at minimum:

Description of the work with objectives or desired results Proposed performance standards to be used as criteria to determine whether the work requirements have been met A request from the Contractor to include the technical approach, period of performance, appropriate cost information, etc. to determine the reasonableness of the Contractor’s proposal

• The Contractors will have the ability to select which RFTPs to respond to.

• Task Orders will be competed among the selected NOIS2 Contractors unless otherwise specified.

• Upon receipt of the contractor’s proposals, the CO will review each proposal based on the specific evaluation criteria identified in the RFTP

• TO’s will be issued in accordance with FAR 16.505

• The proposed TO price will always be considered in competitive TO evaluations

General Information: Task Ordering

RFP Section 1: SF 1449 & Contract Clauses

RFP Section 1

Section 1 organization:

• SF 1449

• FAR 52.212-4 Contract Terms and Conditions- Commercial Items

(OCT 2018)

• Addendum to 52.212-4

• Additional clauses incorporated by reference into the contract

SF 1449Please follow specific fill in instructions found in the RFP pg. 63

SF 1449, Cont.

Clauses and Provisions

When reading the RFP, note that:

Important information is contained in the SF1449 and numerous clauses and provisions have been incorporated, via full text and/or by reference, throughout the document

Provisions and clauses are incorporated by reference to the maximum extent practical

Clauses incorporated by reference have the same force and effect as if they were included in their full text

Full text FAR clauses and provisions can be found at https://www.acquisition.gov/browse/index/far

Full text NASA FAR clauses and provisions can be found at https://www.hq.nasa.gov/office/procurement/regs/NFS.pdf

Difference between a clause and provision:

A clause is a term and condition used in both solicitations and contracts A provision is a term and condition used in solicitations, provisions drop off at the transition between the solicitation and contract

• The FAR is divided into subchapters, parts, subparts, sections, and subsections

• The digits to the left of the decimal point represent the part number

• The numbers to the right of the decimal point and to the left of the dash represent, in order, the subpart, and the section

• The numbers to the right of the dash represent the subsection

• Subdivisions below the section or subsection may further be identified by parenthetical alpha numbers of the following sequence:

• (a)(1)(i)(A)(1)(i)

FAR Arrangement of Regulations

RFP Section 2: Contract Terms and Conditions

Contract Terms and Conditions

• FAR 52.212-5 Contract Terms and Conditions Required to Implement Statutes or

Executive Orders- Commercial Items (AUG 2019)

• By signing the SF 1449, the offeror agrees to all the terms and conditions of the solicitation

• Section 2 “Contract Terms and Conditions Required to Implement Statues or Executive Orders” has a list of commercial clauses and the CO has identified by an “X” those that are incorporated into this contract by reference. Those not identified with an “X” do not apply to this solicitation. Example illustrated below:

RFP Section 3: Contract Documents, Exhibits, or Attachments

Statement of Work (SOW)

Lynn Buquo, CoECI Manager & NOIS2 PDT Chair

Section 3.0 Statement of Work (SOW)

• The SOW is composed of 6 sections:

3.1 Introduction

3.2 Scope of Work

The contractors shall use one or more of the following methodologies to meet the requirements of the specific task orders Crowd-Based Challenges and Prize Competitions Crowd-Based Freelance Projects Crowd-Based Micro-Task Projects Other Crowd- Based Methods

3.2.1 End Products and Services

The contractor shall provide one or more of the end products and services below using one or more of the methodologies described above Technical Solutions Multimedia Data Science Software Engineering Design Crowd Program Formulation Public Engagement Campaigns

3.3 Contract Management and Administration

a. Contractors may be requested to support CoECI-sponsored workshops with presentations showcasing their capabilities and highlighting their approach to crowd-based projects

b. The work on this contract shall be performed primarily at the contractor’s facility and/or virtually via the Contractor’s IT infrastructure, unless otherwise specified in the TO

3.4 Work Authorizations

• The CO will issue Request for Task Plans (RFTPs)

3.5 Task Order Execution

3.6 Reporting Requirements

Statement of Work (SOW) Cont.

RFP SECTION 4: SOLICITATION

PROVISIONS

Marta Choma

Section 4- Solicitation Provisions

52.212-3 Offeror Representations and Certifications –Commercial Items (OCT 2018) Alternate I (OCT 2014)

• Offerors only need to complete paragraph (b) of this provision if the offer has completed the annual representations and certifications electronically, via the SAM website located at https://www.sam.gov/SAM/

• Paragraph (b) requires offerors to certify that they completed the annual Representations and Certifications electronically via the SAM website and have been entered in the last 12 months and are current, accurate, and complete, and applicable to this solicitation

• Including business size standard applicable to the NAICS code of this solicitation 541990

• Submission of reps and certs online allows them to be incorporated into the offer by reference

• If the offeror has not completed the annual representations and certifications electronically, the offeror shall only complete paragraphs (c) through (u) of the provision

• Note that there are additional representations and certifications with offeror fill-ins in Section 4 that must be filled out by the offeror:

• FAR 52.204-24

• FAR 52.209-7

• FAR 52.209-12

• FAR 52.204-17

• FAR 52.209-2

Section 4- Solicitation Provisions, Cont.

RFP Section 5: Instructions To Offerors

Anticipated Offeror Proposal Outline

• Volume I – Technical Acceptability Factor Technical Understanding of Requirements Sample Project Plan

• Volume II- Responsibility Considerations Organizational Conflict of Interest (OCI) Information Responsibility Information Past Performance Record

• Volume III- Model Contract Completed and signed SF 1449 Sections 1-4 of the Solicitation in their entirety with required Offeror fill ins completed

System for Award Management (SAM)

• SAM is a Federal Government owned and operated free web site that collects data from suppliers, validates and stores this data, and disseminates it to various government acquisition agencies.

• FAR 4.11.02(a) Offerors are required to be registered in SAM at the time an offer is submitted

• If you already have an account, verify that the information in this database is current.

• Government contracting officials utilize data provided in SAM for entity pre-award information.

• Offerors must be registered in SAM in order to receive federal payments and disbursements against contracts and grants.

• A Commercial and Government Entity Code (CAGE) is a unique identifier assigned to suppliers of government agencies.

• A CAGE Code may be obtained via registration in SAM.

• The CAGE Code supports a variety of procurement and acquisition processes throughout the U.S.

Government.

• The RFP references the Governmentwide Point of Entry (GPE), GPE means the single point where Government business opportunities greater than $25,000, including synopses of proposed contract actions, solicitations, and associated information, can be accessed electronically by the public.

• The GPE transitioned from FBO.gov to beta.sam.gov, please note that the FAR and other regulations have not yet been updated to reflect this change.

An Amendment to the Solicitation will be issued to edit the Proposal Submission Instructions to the following:

• The beta.sam.gov proposal submission feature is currently not operational.

• Proposal submission will be changed from beta.sam.gov to requiring offerors to submit proposals using CD-ROMs.

• Proposal must be in electronic format

• Offerors will submit the proposal using CD-ROMs. The Government requests an original and 1 copy of each CD-ROM to be provided.

Methods of Proposal Delivery

• Packages shall be delivered to the designated receiving office by one of the following methods:

U.S. Postal Service Commercial Delivery Service Delivery by company employee or other individual agent Regardless of the method chosen above, the Offeror is responsible for delivery of the proposal to the designated receiving office no later than the date and time stated in the

RFP.

Proposal Submission Instructions

External Marking of Proposal Package(s)

• All package(s) must be closed, sealed, and marked in large letters “PROPOSAL –

DELIVER UNOPENED”. Package(s) must include the solicitation number, the Contracting Officer’s name, mail code/stop, and the Offeror’s name and address clearly marked on the outside of the package.

• The Offeror shall include a notice on the cover of the package(s) as follows:

“NOTICE: THIS PROPOSAL MUST BE DELIVERED TO THE SPECIFIED ADDRESS NO LATER

THAN (OFFEROR—ENTER DATE AND TIME).”

Delivery Address Proposals must be delivered to:

NASA Johnson Space Center Attention: BH/Marta Choma Central Receiving, Bldg. 420 2101 NASA Parkway Houston, TX 77058-3696

Proposal Submission Instructions Cont.

• JSC Central Receiving can only be accessed through JSC Gate 4, which is located off Space Center Boulevard.

• The Offeror is strongly encouraged to notify the Contracting Officer one day in advance of the proposal submission. Proposals will be considered to be timely if the proposal package arrives* in Building 420 by the due date and time.

* Proposals will be considered to be timely if the proposal package is time stamped in Building 420 by the due date and time. Please allow ample time to process your package at Building 420.

Proposal Submission Instructions Cont.

Proposal Formatting

• Instructions for proposal arrangement, page limitations, copies and the due date are specified in section 5.1 & 5.2.

• Offerors shall submit their proposals in accordance with those instructions.

Pages submitted in excess of the limitations specified in this provision will not be evaluated by the Government and will be returned to the offeror in accordance with NFS 1815.204-70(b).

• Pay close attention to ensure that the number of pages, page margins, font type, font size, and page size are in conformance to Section 5.1, Table 5.1

• Please note page limitations:

Some volumes/sections are subject to a page limitation and others are not.

Volume I Technical Acceptability is limited to 15 pages In Volume II Responsibility Considerations, the Past Performance Record is subject to the page limit of 1 pages, Proposal information must be provided in the correct volume.

Proposal information in a page-limited volume or section should not be moved to another volume/section without such page limitations.

• Having non-conforming pages returned may affect the government’s evaluation of a proposal, and how this proposal is ultimately rated.

Technical Acceptability Factor- Volume I

The offeror is required to demonstrate its understanding of the requirements to successfully perform the requirements of the contract

1. Technical Understanding of Requirements

Detail the technical approaches (methodologies) for providing products and services as defined in the SOW:

a) Provide an overview of the business model and the specific crowdsourcing method or methods used to successfully deliver the products and services outlined in Section 3.2 of the SOW

b) Provide a description of which end products or services listed in Section 3.2.1 of the SOW the contractor can successfully deliver

c) A detailed description of how each of the Offeror’s specific 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

2. Sample Project Plan

Select the single most representative methodology identified in Section 3.2 of the SOW along with the single most representative end product 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.

a) The key stakeholders in the project, or the plan to identify the key stakeholders, and the approach to effective coordination among them

b) Any possible dependencies that are outside of the Offeror’s control and how any impacts would be addressed

c) A milestone based project schedule with associated period of performance. The Offeror shall include, for each milestone, a descriptive title along with a description of the work to be accomplished

Cont.

Responsibility Considerations- Volume II

A. Organizational Conflict of Interest (OCI) Information

• In accordance with FAR 9.5, the offeror’s proposal will be reviewed for existing or potential OCI issues in relation to this procurement

• The contractor shall identify any existing OCI issues, if any, and submit a plan to mitigate each issue B. Responsibility Information

Offerors may provide any additional information, not already addressed under another volume, that is considered to be necessary to demonstrate a status as a responsible offeror under FAR 9.104 Standards

C. Past Performance Record In accordance with FAR 9.104-3(b), offerors shall demonstrate a satisfactory performance record by submitting information on up to 3 past contracts that best demonstrates their ability to perform the NOIS2 work.

The entire Past Performance write-up shall not exceed 1 page in length.

Responsibility Considerations-Volume II

Responsibility Considerations- Volume II, Cont.

• The Contracting Officer makes the determination of responsibility per FAR 9.104.

Responsible means that the contractor has adequate organizational and financial controls, satisfactory business ethics, financial resources, the ability to successfully perform the work, is eligible, etc.

This determination is performed by the CO and is separate from the selection decision.

If an offeror is not responsible, then they are not eligible for award.

• The Contracting Officer will also check the FAPIIS database (includes records of the Contractor’s previous contracts.)

• The Contracting Officer will request an Equal Opportunity clearance, and check to ensure the veteran’s reports are submitted.

Model Contract- Volume III Model Contract- Volume III

• A model contract is a compilation of Sections 1-4 of the RFP in their entirety, inclusive of all clauses, and agreement to the terms and conditions set for in the Government’s solicitation.

• The model contract shall include all pages contained in Sections 1-4, all required offeror fill-ins completed, and completion of and signature on the SF 1449.

• Sections 5 & 6, The Evaluation Criteria and Instructions to Offerors, are used for the solicitation only, and drop off once the solicitation turns into a contract, and are therefore not included in the Model Contract.

• The model contracts is used by the Government to enter into official contracts between the two parties with successful offeror’s

• Offerors must return the entire model contract, not just the pages with the fill-ins.

• The Model Contract must be signed by a person authorized to commit the offeror.

• The Contracting Officer will sign the Model Contract of the Successful Offeror(s) once all issues are resolved and the selection decision is made.

• Errors or inconsistencies in the Model Contract (that cannot be resolved) may result in an offeror being removed from consideration for award.

Model Contract- Volume III, Cont.

Contract Section Areas of the Model Contract Offerors are Required to Complete

Section 1 Offerors shall appropriately complete blocks 17a-b and 30a-c, provide an original signature, and date the SF 1449.

Please attach Section 1 in its entirety (inclusive of all contract clauses found in Section 1)

Section 2 No fill-ins. Please attach Section 2 in its entirety

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

Section 4 Representations and certifications shall be completed and submitted with 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, and 52.209-12.

SECTION 6: EVALUATION

Section 6: Evaluation

• Initial review of proposals:

• Conducted to determine the acceptability of the proposals in accordance with NFS 1815.305-70, Identification of Unacceptable Proposals. All unacceptable proposals will be eliminated from further evaluation.

• Remaining proposals will be evaluated against the Technical Acceptability Factor

• At the completion of the evaluation against Technical Acceptability, the Government may elect to award a contract without discussions to the technically “Acceptable” responsible offeror(s)

• The Government may also establish a competitive range and conduct discussions

• Discussions, if held, will only be held with the most highly rated offeror(s)

Evaluation Ratings

Discussions

• Offeror’s initial proposal should contain the best terms.

• The Government preference is to award without discussions, however, the Government reserves the right to conduct discussions with those Offerors who have made it to competitive range.

• If discussions are held, the Offeror will:

Have the opportunity to address potentially acceptable items and;

Be requested to resubmit the SF1449 with Final Proposal Revisions

(FPR) which will include clearly marked changes.

For the final evaluation, proposal will be rates as either

“Acceptable” or “Unacceptable” and there will be no “Potentially Acceptable” ratings.

• The Government intends to award to multiple offerors

• The Government is utilizing Procurement Class Deviation 18-02; the

Government will not be evaluating price as an evaluation factor

• Price will be considered as one of the factors in the selection decision for each task order under the contract

• 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 requirements of the solicitation, and the contracting officer has no reason to believe would be likely to offer other than fair and reasonable pricing.

• Past Performance will be evaluated under Responsibility

Special Considerations

NOTE TO PROSPECTIVE OFFERORS

Prospective Offerors are reminded not to contact incumbent personnel (either directly or through electronic means) during duty hours or at their place of employment, as such contacts are disruptive to the performance of the current contract.

Technical Reference Library

• “Technical Data” is defined as: “Information, other than software as defined in §120.10(a)(4), which is required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance or modification of defense articles. This includes information in the form of blueprints, drawings, photographs, plans, instructions or documentation.”

• The acquisition team utilizes a technical library to share relevant technical information to help industry in its understanding of the technical details of the government requirement

• The NOIS2 Technical Library currently contains examples of redacted Task Orders from the current NOIS contract to provide as a reference and for example purposes only

Conclusion

Thank you for attending the Johnson Space Center

Preproposal Conference for the NOIS2 Procurement