NOIS3 PreProposal-Conference-Slides-(Clean).pdf

Welcome to the Johnson Space Center (JSC) NASA Open Innovation Services 3 (NOIS3)

Pre-Proposal Conference

October 9, 2024 Virtual via Teams

2:30 PM Central Time

Topic Presenter

Welcome and Opening Remarks

Brad Niese, Ryon Stewart, and Monica Craft

Procurement Overview Damian Gillette

Current Contract Overview Damian Gillette

Technical Requirements Ryon Stewart

Overview of NOIS3 RFP Damian Gillette

Welcome

Brad Niese, Director NASA JSC Office of Procurement

Ryon Stewart, Deputy Program Manager, NASA Center of Excellence for Collaborative Innovation

(CoECI) & NOIS3 SLPT Chair

Monica Craft, Small Business Specialist NASA JSC Office of Procurement

Main phone number: (281) 483-4512 All emails should be sent to: jsc-smallbusiness@mail.nasa.gov

Monica Craft, Small Business Specialist Location: Building 1, Suite 453

Address:

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

Industry Assistance Office Contact Information

Procurement Overview

Damian Gillette Contracting Officer

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 be answered during the conference, however, responses to verbal questions will not be considered official.

• The Government expects that verbal questions received from Industry will be followed up in writing.

• Questions submitted electronically and in writing will be answered and posted to GPE and will be considered official responses.

• If a difference exists between verbal and written responses to questions, the written responses shall govern.

• The deadline for submitting questions regarding the RFP is 1:00 PM Central Time, Monday, October 17, 2024 .

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

Reminder that proposals are due November 1, 2024 at 1:00 PM, Central Time.

Source Selection Authority and Streamlined Procurement Team (SLPT) Members

Source Selection Authority

• Donna Shafer, JSC Associate Director

SLPT Team

• Ryon Stewart

• Valerie Daniel

• Angela Herblet

Point of Contact & Updates

Contracting Officer: Damian Gillette

• damian.p.gillette@nasa.gov

NOIS3 web address: https://www.nasa.gov/johnson/jsc-procurement/nois3/ mailto:damian.p.gillette@nasa.gov https://www.nasa.gov/johnson/jsc-procurement/nois3/

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:

https://www.hq.nasa.gov/office/procurement/regs/Procurement-Ombuds- Comp-Advocate-Listing.pdf https://www.hq.nasa.gov/office/procurement/regs/Procurement-Ombuds-Comp-Advocate-Listing.pdf https://www.hq.nasa.gov/office/procurement/regs/Procurement-Ombuds-Comp-Advocate-Listing.pdf

Current Contract Overview (NOIS2)

• Contract Numbers: 80JSC020D0035-80JSC020D0053; 80JSC022DA009-

80JSC022DA021

• Prime Contractor: Multiple Contractors

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

• Period of Performance: 6/4/2020 to 6/3/2025

Technical Overview

Ryon Stewart, CoECI Deputy Manager & NOIS3 SLPT Chair

NASA defines crowdsourcing (for the purposes of this Statement of Work) as a method to obtain needed support, services and/or products such as ideas, hardware or content by soliciting contributions from a group of individuals or organizations (external to NASA), especially from an online community.

Crowdsourcing Definition

Mission: To provide maximum value to NASA and Federal Agency programs and projects by formulating and executing crowd-powered projects with excellence and efficiency.

Vision: The entire NASA workforce understands and uses crowd-based methods and resources to help execute NASA’s bold mission. The public is actively engaged with us in supporting that mission in increasingly effective ways. The entire federal government can leverage NASA’s successes in crowdsourcing for the good of the country.

https://www.nasa.gov/coeci/

Mission & Vision https://www.nasa.gov/coeci/

NASA’s Center of Excellence for Collaborative Innovation

HQ

ARC

GRC

GSFC

KSC

LaRC

MSFC

JPL

JSC

SSC

AFRC

Across NASA Centers & Programs Public Facing - Worldwide Across US Federal Agencies

Supports NASA’s Space Technology Mission Directorate (STMD) Prizes and Challenges Program Provides services across NASA & other Federal Agencies Virtual Office hosted within Johnson Space Center Director’s Business Development and Technical Integration Office

Provides Access to Open Innovation (OI) Platforms Worldwide Contracts/Mechanisms Processes/Support Education/Outreach Research 17

NASA’s Center of Excellence for Collaborative Innovation

Valerie Daniel

COR

Lynn Van Deventer OI Advisor

Sarah Douglas Strategic Communications

Steve Rader Program Manager

Ryon Stewart Deputy Program Manager

Erin Ortiz Agreements Manager

Shanel Smith OI Advisor

Vance Benton Alt COR/OI Advisor

Kellie MacLeod OI Advisor

Regina Shoykhet OI Advisor

Brad Martinez Contract Specialist

Kevin Kempton OI Advisor (Rotation - GCD)

Bronta Miller Resource Analyst

Institutional Support

Laura Stelling OI Advisor (PT Rotation - JPL)

Rotations/Shared

Kellie Castaño OI Academy Coordinator

(PT - JSC

Partnerships)

Flex/Freelance

Sandro Gisler OI Advisor (PT – Flex)

Jerlin Hurtado OI Advisor (PT – Flex)

Mike Todaro OI Advisor (PT – Flex)

COMM Support

Intent of NOIS3 is to create a diverse pool of contractors who can perform the Statement of Work requirements. They are then eligible to propose on task orders’ Request for Task Plans as they come up.

To get $ you must:

1. Get on the contract (guaranteed min.)

2. Be awarded and complete task orders

What is this thing?

Technically acceptable, responsible offerors

NASA Open Innovation PortfolioCenter of Excellence for Collaborative

Innovation

Trade names, trademarks, and logos are used in this report for identification only. Their usage does not constitute an official endorsement, either expressed or implied, by the National Aeronautics and Space Administration.

NOIS2 is our

$175,000,000 Multi-

Vendor Contract with 32 Crowds

Access to 50+

Open Innovation

Firms &

Communities

Representing over

200 Million People

Worldwide

NOIS2 Contractor Resources Website

Google and Salesforce sites are used to provide the:

• Project Pipeline

• Request for Task Plan (RFTP) Question Submission Form

• RFTP Q&A List

• RFTP Proposal Submission Form

• Site Tutorial, FAQ, Feedback, NOIS2 Files, Contact Us

Submission Forms

NOIS2 Task Order Award Process

Schedule is provided in each RFTP and will vary depending on owner needs, complexity, etc.

Typical schedule:

Business Day 01: Release RFTP Business Day 03: Questions due noon CT Business Day 04: Answers to questions by close of business Business Day 10: Proposals due, up to 5 pages (more if proposing alternative method(s)) + form info Business Day 15: Proposal evaluation and task order award

Fill out project intake form and/or email us general info

Meet to Discuss Options

Provide Project Rqmts & Constraints (1-3 pages)

CoECI creates

NOIS2 RFTP

CoECI provides overview

Support Q&A via Web (1-2 hrs)

Review & Approve

CoECI sets up forum with contractor as needed

NOIS2

contractors

Submit Proposals

Support Proposal Evaluation

Take 30 Min Evaluation Training

CoECI provides evaluator training

CoECI facilitates evaluation

CoECI awards

Task Order

Provide survey feedback

(15-30 min)

CoECI reviews results & collects feedback

Project Formulation

NOIS2 Contractor Selection

Funds Obligated

CoECI Works to set goals & expectations

Support kickoff and formulation efforts

Contractor begins TO execution

Support challenge development with details & feedback

Contractor develops challenge

Coordinate publicity with

PAO

Contractor markets challenge

Contractor launches challenge

Support any Webinars or Q&A

Contractor coordinates webinar/responses

Contractor collects submissions

Support submission Evaluation

Contractor facilitates evaluation

Contractor awards winners & delivers solutions

CoECI Provides RFTP to Contractors

Provide any funds required

NOIS2 Challenge Task Order Execution

Project owners normally spend 1-3 hours in this phase over 1-2 weeks.

Project owners normally spend 4-6 hours in this phase over 1.5

- 3 weeks.

Project owners normally spend anywhere from 8- 40+ hours in this phase over 2-12 months depending on challenge.

CoECI facilitates getting started.

CoECI facilitates getting the right contractor for the challenge.

CoECI monitors project owner/ contractor to ensure best practices.

NOIS2 Challenge Project Process

CoECI History in the Data

Since 2010

• 860+ projects (~80 in progress)

• 560+ public projects

• 95% success rate

• $122M+ budgeted

• $172M+ saved

• 86 NOIS projects

• ~280 NOIS2 projects so far

NOIS3

• NOIS and NOIS2 have been extremely successful contracts

• NOIS utilized public challenges while NOIS2 expanded the available methodologies

• NOIS3 builds on NOIS2 successes with minor modifications in the statement of work, continuing to focus on end products and services that can be delivered via a proposed crowdsourcing methodology.

Overview of NOIS3 Request For Proposal (RFP)

80JSC024R0004

Contracting Officer

The RFP contains 6 Sections:

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

• Please continue to monitor SAM.gov and the NOIS3 procurement website (https://www.nasa.gov/johnson/jsc-procurement/nois3/) for any updates, amendments to the RFP, schedule changes, etc.

General Information: RFP Structure https://www.nasa.gov/johnson/jsc-procurement/nois3/

The Contracting Officer may make amendments to the RFP which will be posted on SAM.gov and the NOIS3 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.

Amendments to the RFP

General Information

• Competition:

• Full and Open Competition.

• The CO will evaluate each requirement at the Task Order (TO) level to determine if it qualifies and can be set aside for small businesses only.

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

• Period of Performance:

• No Phase-In Period

• Base Period - 6/01/2025 - 5/31/2027

• Option 1 – 6/01/2027 - 5/31/2030

• Option 2 – 6/01/2030 – 5/31/2035

• On-Ramping - The parties mutually agree that the original solicitation shall remain open during the life of this contract and that at any time NASA may award contracts to additional vendors for IDIQ requirements. As deemed necessary during the life of this contract, NASA will allow submission of proposals for IDIQ contracts. The requirement for submission of on-ramp proposals will be established via solicitation notice. The decision to request proposals under the clause will be solely at NASA’s discretion and will only occur after this requirement has been synopsized.

• Off-Ramping is an option if the contractor decides that they no longer wish to participate in the contract.

• Type of Contract:

• Multiple Award contract with the ability to issue Firm-Fixed-Price (FFP) Indefinite Delivery/ Indefinite Quantity (IDIQ) TOs.

• After the NOIS3 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 $500.

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

General Information: Task Ordering

• Only the Contracting Officer may issue Task Orders (TOs).

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

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

(NOV 2023)

• Addendum to 52.212-4

• Additional clauses incorporated by reference into the contract

SF1449Please follow specific fill in instructions found in the RFP pg. 67

SF1449, 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 http://www.acquisition.gov/browse/index/far http://www.hq.nasa.gov/office/procurement/regs/NFS.pdf

FAR Arrangement of Regulations

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

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 (MAY 2024)

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

Ryon Stewart, CoECI Deputy Manager & NOIS3 SLPT Chair

Section 3.0 Statement of Work (SOW)

The SOW is composed of 6 sections:

1. Introduction (Section 3.1)

2. Scope of Work (Section 3.2)

The contractors shall use one or more of the following methodologies to meet the requirements of the specific task orders

a) Crowd-Based Challenges and Competitions

b) Crowd-Based Freelance Projects

c) Crowd-Based Micro-Task Projects

d) Other Crowd- Based Methods

1. End Products and Services (Section 3.2.1)* The contractor shall provide one or more of the end products and services below using one or more of the methodologies described above

a) Technical Solutions

b) Data Science

c) Software

d) Engineering Design

e) Technology Search or Landscape Analysis

f) Multimedia

g) Expert Services

h) Crowd Program Formulation

i) Public Engagement Campaigns

*To get on contract, you must be capable of providing at least one end product or service a-e

Section 3.0 Statement of Work (SOW) Cont.

3. Contract Management and Administration (Section 3.3)

• 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 issued task order.

• The work the Contractor performs on this contract shall be performed primarily at the contractor’s facility and/or virtually via the Contractor’s Information Technology (IT) infrastructure, unless specified otherwise in the Task Order.

4. Work Authorizations (Section 3.4) The Contracting Officer will issue Request for Task Plans (RFTPs)

5. Task Order Execution (Section 3.5) Describes what requirements (a-m) the contractor must accomplish to execute the task order

6. Reporting Requirements (Section 3.6) Close-out report presented to stakeholders and provide data associated with task order execution

Statement of Work

To get on NOIS3, the contractor must be capable of providing at least one 3.2 methodology and deliver at least one 3.2.1 end product or service, to accomplish the 3.5 task order execution requirements.

RFP Section 4: Solicitation Provisions

Section 4- Solicitation Provisions

52.212-3 Offeror Representations and Certifications – Commercial Items (MAY 2024) Alternate I (FEB 2024)

• 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 http://www.sam.gov/SAM/

• 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

Volume I – Technical Acceptability Factor

Technical Understanding of Requirements

Sample Project Plan

Volume II - Responsibility Considerations

Responsibility Information

Volume III - Model Contract

Completed and signed SF 1449

Sections 1-3 are all required with the Offeror fill-ins completed. The model contracts may be used by the Government to enter into official contracts between the two parties.

Section 4 shall also be submitted but will not be part of the Model Contract.

Anticipated Offeror Proposal Outline

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 Unique Entity ID is assigned to suppliers of government agencies.

• A Unique Entity ID may be obtained via registration in SAM.

• The Unique Entity ID 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.

Proposal Submission Instructions

Method of Proposal Delivery (See Section 5.1 for Full Instructions)

• The offeror shall submit its proposal via NASA’s Enterprise File Sharing and Sync Box (EFSS Box), a FedRAMP Moderate certified platform.

• Electronic submissions shall not contain hidden formulas, tables, be locked, be password protected, or contain links to data not included in the electronic copy.

• All electronic submissions should be searchable and should not contain scanned documents, except those documents that must be provided in their native format (e.g., signature pages, prior award fee letters for past performance, DCAA/DCMA approval letters, as applicable).

• The offeror shall ensure documents are free from viruses and malware, as documents determined by NASA to contain a virus or malware will not be opened or evaluated.

• Subcontractors may submit their required proposal information separately using the instructions in this provision.

• The offeror shall ensure subcontractor submissions are made no later than the date and time specified for proposal submission and comply with all solicitation instructions.

• Offerors are encouraged to check with their corporate IT staff to determine if there are firewall restrictions that would need to be addressed prior to the submission of proposal files through NASA’s EFSS Box.

Proposal Submission Instructions Cont.

Method of Proposal Delivery (See Section 5.1 for Full Instructions)

• Prior to the submission of proposal files, offerors interested in submitting a proposal in response to this solicitation should notify Damian P. Gillette of their intent to submit a proposal at least 48 hours prior to the intended submission date, at the following email address: damian.p.gillette@nasa.gov.

• Offerors, especially those that have not previously submitted a proposal utilizing NASA’s EFSS Box, should coordinate the submission of a test file with Damian P. Gillette’s name no less than 5 days in advance of the proposal due date specified in the solicitation to allow time to work through any submission issues.

• Offerors should electronically submit their proposals not later than 1:00pm Central Time one working day prior to the date specified for receipt of proposals, if offerors seek to coordinate with the Contracting Officer regarding the proposal’s receipt.

• NASA is not required to verify proposal receipt prior to the submission deadline.

mailto:damian.p.gillette@nasa.gov

Proposal Submission Instructions Cont.

The offeror shall submit all proposal files to:

https://nasagov.app.box.com/f/77a9b814038d402bb3b5f6c2d98863ec.

The offeror shall follow instructions regarding proposal submission found at:

https://www.hq.nasa.gov/office/procurement/other/EFSS-Box-Offeror- Proposal-Submission-Instructions.pdf.

https://nasagov.app.box.com/f/77a9b814038d402bb3b5f6c2d98863ec https://www.hq.nasa.gov/office/procurement/other/EFSS-Box-Offeror-Proposal-Submission-Instructions.pdf https://www.hq.nasa.gov/office/procurement/other/EFSS-Box-Offeror-Proposal-Submission-Instructions.pdf

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, None

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.

Technical Acceptability Factor - Volume I

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. Offeror Proposed Methodologies and End Products and Services

The Offeror shall identify (with an “x”) which methodology(ies) and end product(s) and service(s) as described in the SOW the offeror intends to utilize to meet the SOW requirements. Note: The Offeror must provide at least one from SOW 3.2.1 End Products and Services a.-e.

SOW 3.2.1 End Products and Services

SO

W

.2

S co pe o f W or k:

M et ho do lo gi es

a. Technical Solutions

b. D ata Science

c. Softw are

d. Engineering D esign

e. Technology Search or Landscape Analysis

f. M ultim edia

g. Expert Services

h. C row d Program

Form ulation

i. Public Engagem ent

C am paign

a. Challenges & Competitions

b. Freelance

c. Micro-Task

d. Other

2. 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. Describe each Section 3.5 element (a-m) in the order provided and, as applicable, reference each element in the sample project plan. As stated in Section 3.5, if an element is not applicable, the Contractor must provide a justification for each.

d) A description of unique processes, novel approaches, or innovations relevant to the SOW and overall requirements and/or narrative detailing how the offeror can be successful.

Technical Acceptability Factor - Volume I Cont.

Technical Acceptability Factor - Volume I Cont.

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

Statement of Work

To get on NOIS3, the contractor must be capable of providing at least one 3.2 methodology and deliver at least one 3.2.1 end product or service, to accomplish the 3.5 task order execution requirements.

Responsibility Considerations - Volume II

Responsibility Considerations - Volume II

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

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

• The model contract shall include all pages contained in Sections 1-3, all required offeror fill-ins completed, and completion of and signature on the SF 1449. Section 4 shall also be submitted but will not be part of the model contract.

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

Note: this section will not be part of the Model Contract.

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 will elect to award a contract without discussions to the technically “Acceptable” responsible offeror(s)

Evaluation Ratings

Section 6: Evaluation Discussions

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

• The Government will award without discussions.

• The Government intends to award to multiple offerors

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

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 may utilize a technical library to share relevant technical information to help industry in its understanding of the technical details of the government requirement

Conclusion

Thank you for attending the JSC Preproposal Conference for the NOIS3 Procurement!