About this file

This document contains questions and answers related to a National Aeronautics and Space Administration (NASA) Research Announcement (NRA) soliciting proposals for Model-Based Systems Analysis and Engineering (MBSA&E) for the Sustainable Flight National Partnership (SFNP) Phase 1. NASA anticipates awarding contracts in fiscal year 2023 to support code development within the OpenMDAO platform, participate in one to three one-day MBSA&E industry workshops, and integrate MBSA&E frameworks with OpenMDAO via a REST API library. Questions cover cost proposal templates, commercial tool licenses, the OpenMDAO concept, purchasing from non-U.S. sources, and waiver of invention rights. The final set of questions is due by June 14, 2023.

View the file

Other files

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

Final NRA - NASA Model-Based Systems Analysis and Engineering (MBSA&E) for the Sustainable Flight National Partnership (SFNP) Phase 1

Questions and Answers

1. The tools listed are related more towards architecture and design. Is there a list of tools currently being used for Configuration Management or specialty engineering areas such as Reliability, Safety, Weight, Logistics, etc.?

‐ Configuration management is being done through an internally developed aircraft system hierarchy using Python. Weight is calculated using the Aviary tool which combines sizing methods from legacy tools such as FLOPS and GASP and we are not yet assessing reliability, safety, or logistics. Refer to the Configuration Management Section 6.5 of the NASA Systems Engineering Handbook, NASA SP-2016-6105 Rev2 which is publicly available at https://ntrs.nasa.gov/api/citations/20170001761/downloads/20170001761.pdf

2. Does NASA follow the Government SETR (Systems Engineering Technical Review) process?

Will this need to be supported with the appropriate artifacts?

‐ Refer to the Technical Review Appendix G of the NASA Systems Engineering Processes and Requirements, NPR 7123.1C which is publicly available at https://nodis3.gsfc.nasa.gov/npg_img/N_PR_7123_001C_/N_PR_7123_001C_.pdf

3. Eight CLINs were provided as an example structure to facilitate partial awards and we are assuming it covers the 18-month Period of Performance. 1) If we are not bidding on all CLINs, could our proposal response provide a solution suite that covers less than 18 months? 2) Are CLINs expected to be staggered where appropriate or parallel lines of effort? 3) And, are we to stick as close as possible to the CLIN structure with its naming convention? Or, can we make changes as long as it retains the 8 line item approach?

‐ 1) Yes 2) Each Offeror has the liberty to present the way it works the best for its proposal 3) You may name the CLIN that fits your information; however, the proposed work plan must address the NASA goals and objectives of the CLIN.

4. What is currently being used to drive maintenance - such as on the topics of MSG-3, Reliability Centered Maintenance, etc.? An additional question could be "are we able to review their maintenance strategies, etc.?"

‐ Maintenance considerations for aircraft concepts and technologies have not yet been considered in the MBSA&E framework development.

5. Currently, are there any deliverables that must be delivered per required FARs or some other GOV regulations? It would be beneficial to know if those deliverables must be maintained in current format or if they could be modified per the new framework.

‐ See NRA Section 8.

6. Should we anticipate some level of code development within OpenMDAO and administration of said environment's database repository to be in scope? Or, will the PoP for phase 1 focus only on integration with OpenMDAO (via a REST API library as an example)?

‐ Code development within OpenMDAO is within scope, to varying degrees for each subtopic, for Phase I.

7. In the RFP it states that NASA will request the Offeror to complete and return certifications and representations and Standard Form 33, Solicitation, Offer, and Award. Is there expected to be adequate pricing competition for this effort? If yes, it would be the assumption that this would remove the requirement to certify (TINA requirement), please advise.

‐ As this NRA is a full and open competition, NASA anticipates there will be an adequate pricing competition. Please refer to 15.403-4 Requiring certified cost or pricing data for when and if such certification is required.

8. Would NASA entertain an extension in order to provide additional time to receive inputs from outside sources and to ensure all requirements are met to submit a compliant proposal? Extension requested to August 7, 2023.

‐ An extension is not contemplated at this moment, however, please monitor SAM.gov updates.

9. Section 10.2 Proposal Content and Format. The proposal format and content requirements are outlined below in Table 1. Summary of Proposal Content. The below noted sections of the proposal must be submitted as one searchable, unlocked PDF file with edit permissions enabled as well as Attachment B Cost Proposal in an unlocked Microsoft Excel file. Yet Section 10.1 d) shows a MS Volume.docx file extension and not a PDF. Please clarify:

‐ Section 10.1 d) shows examples of acceptable individual file names, not specific to this solicitation.

10. Table 1 shows the Title of Volume 2 as Past Performance and yet Section II calls it Past Experience. Please clarify.

‐ Section II is Past Experience.

11. Please provide correct spreadsheet(s) to Attachment B – Cost Reimbursable Pricing Template Attachment B only includes spreadsheets for CLIN 001-003 Tech Area 1 and not for CLINs -004 to 008. Please provide additional spreadsheets for CLIN 004 – 008 Tech Area 2 and/or provide directions on how industry should document pricing for CLINs -004 to -008?

‐ The template is only a template. Please modify the spreadsheet to fit your proposal needs.

12. Attachment B CLIN 001-003 Tech Area 1 include references to PWS numbers: Name. Should these PWS references be references to Sections in the applicable NRA Technical Areas?

‐ Yes

13. Will NASA remove I.49 FAR 52.222-41 Service Contract Labor Standards (AUG 2018) in favor of I.50. 52.222-48 Exemption from Application of the Service Contract Labor Standards to Contracts for Maintenance? If not, but an offeror demonstrates that the majority of the work under the award will be performed by engineers, will NASA then remove I.49 FAR 52.222-41 Service Contract Labor Standards (AUG 2018) in favor of I.50. 52.222-48 Exemption from Application of the Service Contract Labor Standards to Contracts for Maintenance?

‐ NASA will remove FAR 52.222-41 from the award when an offeror is in a contract award negotiation.

14. What is the anticipated award date?

‐ The Government anticipates to award contracts in the Government Fiscal year (FY) 2023.

15. The Model Contract contains I.112 NFS 1852.227-71 Requests for Waiver of Rights to Inventions (APR 2015), which states that advanced waivers may be granted for a “class of inventions.” However, the NFS states that any invention waiver petition for such classes of inventions must be directed to “a particular process, machine, manufacture, or composition of matter, or to a narrowly-drawn, focused area of technology.” Please clarify, preferably with examples, what constitutes a narrowly-drawn, focused areas of technology that would meet this requirement for a class of inventions.”

‐ Advance Waiver Request shall identify invention(s) that are: (1) specifically identified, (2) are directed to a particular process, machine, manufacture, or composition of matter, or (3) are drawn to a narrowly focused area of technology, or a combination. A “narrowly focused area of technology” may be viewed as the middle ground between (1) and (2). While an invention may not be believed to be directed to a particular process, machine, manufacture, or composition of matter, the Requestor should be able to specifically identify the narrow area of technology that the anticipated invention pertains or what specific problem is to be overcome.

16. In Section 8, NASA requires participation and presentation at MBSA&E Industry Days/Workshops (TBD). How many workshops should we plan for and how many days will they last?

‐ MBSA&E Industry Days/Workshops are still TBD. While the exact number and format is not currently known, there will likely be 1-3 workshops with each lasting approximately 1 day.

These workshops could be in-person, hybrid, or virtual.

17. The offerors acknowledge that using license free and open-source software tools is typically a preferred resource. However, in some cases there are commercial-licensed tools that offer a competitive advantage to develop some of the project tasks. Is NASA open to receiving proposals based on commercial-licensed tools? In affirmative case, is there a preference for using tools whose licenses are already in use by NASA?

‐ NASA is open to receiving proposals that use commercial-licensed tools. Tools that are not already used by NASA can be proposed.

18. Can you advise if NASA’s OpenMDAO concept is only the Java app specific to SFNP?

‐ OpenMDAO is a Python based software and is not a Java app.

19. Can an awardee directly purchase supplies and/or services from a non-US source?

‐ Section 9.1 states: NASA funding through this NRA may not be used to support research and development efforts by non-U.S. organizations at any level. Participation by non-U.S.

organizations is not permitted, except that (a) research may be conducted with foreign entities on a cooperative, no-exchange-of funds basis; or (b) U.S. award recipients may directly purchase supplies and/or services, which do not constitute research, from non-U.S. sources.

Team members who are not U.S. citizens but are employed by or studying at a U.S.

organization, may receive funding to support their research activities through this NRA. Each Offeror shall submit Attachment C – Eligibility Certification and Supplemental Information Form to determine its eligibility for this NRA.

File details come from the government source that posted it. Updated .