OCI RFI RPOC V.pdf
PDF 127 KB Posted
- Solicitation number
- 80JSC022RPOCV
About this file
This request for information (RFI) from NASA's Johnson Space Center (JSC) seeks industry input on potential organizational conflicts of interest related to the upcoming Rendezvous, Proximity Operations, and Capture V (RPOC V) contract. The RPOC V effort will include oversight of non-Russian vehicles to the International Space Station as well as oversight and trajectory activities for Gateway and the Human Landing System. Responses should address any potential OCI issues from the contractor's perspective, proposed mitigation strategies, and whether any other OCI concerns exist. Interested offerors must submit responses by February 10th, 2022 for NASA to review and provide written feedback. Additionally, the related federal contract opportunity notice announces an industry day on January 24th and one-on-one meetings from January 25th to discuss the RPOC V acquisition.
View the file
Other files
Show all 25
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
The purpose of this RFI is to inform industry that NASA/JSC is providing interested parties an opportunity to provide information regarding potential organizational conflicts of interest (OCI) arising from the upcoming Rendezvous, Proximity Operations, and Capture V (RPOC V) contract.
NASA will provide a written response and an optional virtual briefing to each interested party submitting a response to this RFI. Written responses/briefings are intended to provide information on the Government’s analysis of the mitigation approach proposed in the company’s OCI mitigation strategy. Written responses/briefings will not discuss how to mitigate an OCI but will provide context on the Government’s analysis of the OCI mitigation strategy. The Government will only address information provided in the company’s OCI mitigation strategy, will not address hypotheticals or NASA non-public information, and will not entertain any new information brought up during the briefing.
The nature of the work anticipated under the RPOC V contract may create the potential for OCI(s) as currently described in FAR Subpart 9.5. Each interested party should review FAR Subpart 9.5 in light of NASA’s anticipation of OCI issues and consider carefully the extent to which an OCI may arise before making the decision to compete for the RPOC V contract.
Specifically, NASA anticipates that the effort under the RPOC V contract will include the following types of tasks which could lead to potential OCI issues:
• Oversight of all non-Russian Visiting Vehicles to the International Space Station (ISS) including Commercial Crew Transportation Capability (CCtCAP), Commercial Resupply Services (CRS) Program, Private Astronaut Missions (PAM), Commercial Element (Axiom), and HTV (H-II Transfer Vehicle) and its follow-on HTV-X including analyzing the spacecraft design and the rendezvous, proximity operations, and capture capabilities of the vehicles.
• Oversight and/or partnering activities related to Guidance, Navigation, & Control, trajectory, and/or mission design of Gateway and/or the Human Landing System
(HLS).
• Oversight of Commercial LEO space station Guidance, Navigation, and Control, trajectory, and/or mission design development.
These types of tasks could lead to the following categories of OCI depending on the composition of the team selected for the RPOC V contract:
• Potential impaired objectivity if the RPOC V contractor or its subcontractors are assessing data developed by themselves or related companies or subcontractors.
• Potential impaired objectivity if the RPOC V contractor or its subcontractors or related companies are responsible for assessing or involved in creating safety analysis/hazard reports for hardware or data under another JSC contract.
• Unequal access to information if the RPOC V contractor are responsible for assessing data developed and provided under another JSC contract.
This list is representative of potential OCI issues that NASA has identified, however, it is not intended to be all inclusive of areas of OCI concern that your company may identify related to the performance of the RPOC V contract requirements.
Interested parties are requested to address the following questions in their response:
1. What type(s) of OCI issues would your company or potential team identify, if any, should you choose to propose on the RPOC V contract?
2. What strategies would you anticipate proposing to mitigate the OCI issues that you identified (if any)? Please provide strategy details, previous examples/experience with other contracts with NASA or other agencies, etc.
3. Are there any other types of potential OCI issues with the proposed RPOC V contract that were not identified in this RFI?
4. Does your company foresee any OCI issues associated with the RPOC V contract that would cause you to decide not to propose on the potential RPOC V RFP?
Responses must be submitted via e-mail to the Contracting Officer listed below by 4:00 PM Central Time on February 10, 2022. NASA will review any responses received regarding potential OCI and each offeror’s proposed OCI mitigation strategy. NASA will respond to each company who submits a mitigation strategy. NASA’s response is not intended to serve as a confirmation that, in fact, all potential OCI issues have been identified, an OCI will ultimately exist, or that an interested party is capable of successfully avoiding or mitigating an identified OCI. NASA’s response is also not intended to encourage or discourage any interested party from responding to an RFP issued for RPOC V in the future. Furthermore, NASA’s response in no way alters or interprets FAR 9.5 as it applies to a final statement of work or a final proposal submission, should an interest party elect to submit a proposal to an RFP for RPOC V.
Subsequent to this OCI submission and NASA’s response, NASA will not consider further information as it relates to this RFI.
The documents currently on the NASA RPOC V acquisition website are for information and planning purposes to allow industry the opportunity to comment, and to promote competition only.
NASA will not affirmatively release any information received in response to this RFI to the public, but may use information received in developing the best approach for a contract strategy, and therefore such information may be recognizable to the interested party who submitted it. Any information submitted in response to this RFI that is marked as “Confidential Commercial or Financial Information” will be considered as voluntarily submitted in accordance with the Freedom of Information Act.
All questions should be directed to the point of contact identified below. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by NASA to form a binding contract. NASA is under no obligation to issue a solicitation or to award any contract on the basis of this RFI. NASA will not pay for any information solicited under this RFI. No solicitation exists; therefore, do not request a copy of a solicitation. If a solicitation is released it will be synopsized on SAM.gov. It is the interested party’s responsibility to monitor this website for the release of any subsequent solicitation or synopsis.
Point of Contact Name: J.R. Carpentier Title: Contracting Officer Email:
john.r.carpentier@nasa.gov mailto:john.r.carpentier@nasa.gov
NASA will provide a written response and an optional virtual briefing to each interested party submitting a response to this RFI. Written responses/briefings are intended to provide
Accessibility Report
Filename:
OCI RFI RPOC V.pdf
Report created by:
Organization:
[Enter personal and organization information through the Preferences > Identity dialog.]
Summary
The checker found no problems in this document.
Needs manual check: 0
Passed manually: 2
Failed manually: 0
Skipped: 3
Passed: 27
Failed: 0
Detailed Report
Document
Rule Name Status Description
Accessibility permission flag Passed Accessibility permission flag must be set
Image-only PDF Passed Document is not image-only PDF
Tagged PDF Passed Document is tagged PDF
Logical Reading Order Passed manually Document structure provides a logical reading order
Primary language Passed Text language is specified
Title Passed Document title is showing in title bar
Bookmarks Passed Bookmarks are present in large documents
Color contrast Passed manually Document has appropriate color contrast
Page Content
Rule Name Status Description
Tagged content Passed All page content is tagged
Tagged annotations Passed All annotations are tagged
Tab order Passed Tab order is consistent with structure order
Character encoding Passed Reliable character encoding is provided
Tagged multimedia Passed All multimedia objects are tagged
Screen flicker Passed Page will not cause screen flicker
Scripts Passed No inaccessible scripts
Timed responses Passed Page does not require timed responses
Navigation links Passed Navigation links are not repetitive
Forms
Rule Name Status Description
Tagged form fields Passed All form fields are tagged
Field descriptions Passed All form fields have description
Alternate Text
Rule Name Status Description
Figures alternate text Passed Figures require alternate text
Nested alternate text Passed Alternate text that will never be read
Associated with content Passed Alternate text must be associated with some content
Hides annotation Passed Alternate text should not hide annotation
Other elements alternate text Passed Other elements that require alternate text
Tables
Rule Name Status Description
Rows Passed TR must be a child of Table, THead, TBody, or TFoot
TH and TD Passed TH and TD must be children of TR
Headers Skipped Tables should have headers
Regularity Skipped Tables must contain the same number of columns in each row and rows in each column
Summary Skipped Tables must have a summary
Lists
Rule Name Status Description
List items Passed LI must be a child of L
Lbl and LBody Passed Lbl and LBody must be children of LI
Headings
Rule Name Status Description
Appropriate nesting Passed Appropriate nesting
Back to Top
File details come from the government source that posted it. Updated .