80GRC022R0012 Request for Proposal_Final Signed.pdf

80GRC022R0012

National Aeronautics and Space Administration John H. Glenn Research Center Lewis Field Cleveland, OH 44135-3191

August 8, 2022

GRC Office of Procurement, CHB

TO: All Prospective Offerors

SUBJECT: Request for Proposal (RFP), Solicitation No. 80GRC022R0012, for “High-Speed Endoatmospheric Commercial Vehicle Conceptual Design Study and Technology Roadmaps Development”

You are invited to submit a proposal in response to the National Aeronautics and Space Administration (NASA) Glenn Research Center’s (GRC) solicitation. The principal purpose of this requirement is to provide the Hypersonic Technology Project (HTP) and Commercial Supersonic Technology (CST) project with design and technology roadmap information needed for the development of strategies to enable environmentally sustainable, civilian high-speed travel in support of the Aeronautics Research Mission Directorate’s (ARMD) 2019 Strategic Implementation Plan Thrust 2.

NASA will conduct this acquisition as a full and open competition. The North American Classification System (NAICS) code for this acquisition is 541715 and the small business size standard is 1500 employees.

This competitive acquisition will result in a Firm-fixed Price contract. The contract will have an intended total potential period of performance of 12 months.

The anticipated contract award date is December 8, 2022, with a January 1, 2023 contract effective date. The contract will be performed offsite at the Contractor’s facilities with the potential use of onsite NASA facilities if appropriate.

Potential offerors should pay close attention to all solicitation instructions.

NASA GRC appreciates the comments received in response to the release of the Draft RFP and Industry Day. These comments resulted in improvements to the quality and content of the overall RFP. Offerors should review the RFP in its entirety, as it contents has changed from the Draft RFP version. The following identifies some areas where significant changes or clarifications have been made from the Draft RFP to this Final RFP:

• Statement of Work

• Data Rights Clauses

• Past Performance Requirements

• Subcontracting Plan Requirements

• A total investment of approximately $2,500,000 is anticipated for this Solicitation. Actual number and value of the awards will depend on the quality and content of the proposals received.

This list is not intended to cover all changes nor describe all RFP requirements. Again, Offerors should carefully review the RFP in its entirety and read all information previously posted on SAM.gov from the Virtual Industry Day: https://sam.gov/opp/f0a936e96b25440985ff04fde7b1d0b8/view

Offerors are encouraged to refer to Federal Acquisition Regulation (FAR) provision 52.215-1 Instructions to Offerors – Competitive Acquisition, in particular paragraph (f)(4) which discusses the Government’s right to award a contract without discussions. Due to the schedule of this acquisition, NASA suggests all Offerors submit their best and final proposal taking into consideration the data rights required, statement of work, and required clauses in this RFP.

In order to control and protect sensitive data owned by the Government and its Contractors, NASA policy requires all acquisition-related documents be released in Adobe Portable Document Format (PDF). The Offeror’s Price Volume Proposal shall be included in Microsoft Excel format with working cell formulas.

Documents related to this acquisition, including this letter, solicitation, and links will be attainable electronically from the World Wide Web through the Government-wide point of entry website at www.SAM.gov. Potential Offerors are requested to periodically monitor the website for updates.

NASA FAR Supplement (NFS) clause 1852.215-84 Ombudsman, is applicable. The Center Ombudsman for this acquisition can be found at http://prod.nais.nasa.gov/pub/pub library/Omb.html.

This RFP does not commit NASA GRC to pay any proposal preparation costs, nor does it obligate NASA GRC to procure or contract for these services. This request is not an authorization to proceed, and does not authorize payment for any charges incurred by the offeror for performing any of the work call for in this solicitation.

Proposals submitted in response to this solicitation shall be due no later than September 12, 2022, 4:30pm ET. Proposals shall be submitted to the Contracting Officer (CO), Rita K. Dickens, at rita.k.dickens@nasa.gov. Please be sure to read all proposal submission instructions in Section L of the

RFP.

All questions regarding this RFP should be submitted in writing, electronically, citing the solicitation number to the CO, Rita K. Dickens at rita.k.dickens@nasa.gov on or before August 23, 2022, 4:30pm ET in order to allow for a proper response and dissemination. The Government reserves the right to not respond to any questions received concerning this solicitation after the questions due date.

Accordingly, Offerors are encouraged to carefully review all solicitation requirements and submit questions to the Government as early as possible.

Thank you for your support. We look forward to receiving your proposals.

Rita K. Dickens Contracting Officer

Enclosure(s): (1) SF 33 and Final RFP #80GRC022R0012

ENCLOSURE 1

SF33 and Request for Proposal

RFP 80GRC022R0012 “High-Speed Endoatmospheric Commercial Vehicle Conceptual Design Study and Technology Roadmaps Development”

(SF33 on following page)

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 1852.216-78 FIRM FIXED PRICE (DEC 1988)

The total firm fixed price of this contract is $[OFI].

(End of clause)

B.2 Contract Line-Item Number (CLIN) Structure

CLIN 0001 (Firm Fixed Price) – Research & Development

This CLIN captures all of the tasks listed in the Statement of Work in Section C of the contract.

(End of section)

SECTION C – DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

C.1 STATEMENT OF WORK

High-Speed Endoatmospheric Commercial Vehicle Conceptual Design Study and Technology Roadmaps

Development

Dated: July 26, 2022

1.0 Introduction/Background:

In recent years there has been a significant increase in the number of aerospace companies, both well-established and start-ups, that have proposed and begun to build and test aircraft concepts aimed at endoatmospheric, commercial point-to-point travel in the supersonic to hypersonic speed regime. This growth in interest prompted the NASA Hypersonic Technology Project (HTP) to hold a forum in January 2020 with stakeholders across government and industry in conjunction with the AIAA SciTech Conference.

As a result of that meeting, HTP subsequently funded two studies to begin to examine the economic viability, regulatory barriers, and technical challenges associated with this high-speed commercial market.

These studies identified supersonic design points where market viability potentially exists, as well as high level challenges to enabling the market. As a result, NASA is interested in design solutions both for near-term vehicles as identified in the market studies in Table 1 as well as longer-term vehicles that incorporate currently low technology readiness level (TRL) technology and may close technically and economically at a different design point within the high speed design matrix in Table 2.

HTP and NASA’s Commercial Supersonic Technology (CST) project, under the Advanced Air Vehicles Program (AAVP), are jointly tasked with developing a strategy to enable an environmentally responsible/sustainable civilian high-speed market. NASA is seeking to stimulate innovation and foster the pursuit of conceptual designs for high-speed (‘high-speed’ defined as Mach 2 through Mach 5) commercial transports that could enter service in the next decade (i.e., 2030-2040) or beyond, market permitting. These commercial transports must be able to overcome significant performance and environmental challenges for the benefit of the public. These conceptual vehicle design studies will identify key technology development needs and opportunities that will enable such vehicles.

Proposals are sought to address the work approach of the offeror to design and analyze classes of vehicle designs that may fall within the Mach 2 – 5 range, with the specific speed, passenger count, range, and allowable TRL to be determined after contract award. Desired specifications for a baseline vehicle design, based roughly on values in Table 1, will be informed by results of a separately contracted, ongoing life cycle costs analysis study which will not be completed until after the contract award. However, offeror input will be factored into these specifications. An additional design variant, incorporating low TRL technologies, may differ from the baseline design for any of the parameters identified in Table 2. Such differences will be determined, in part at the offeror’s discretion, in negotiation with NASA following the award.

reference vehicle design may also be used to provide data to other U.S. Government agencies for standards and rulemaking.

The second objective is to develop technology roadmaps to address environmental, economic, and societal barriers to the sustainability goals of NASA. These sustainability goals include adherence to current or anticipated regulations for landing and takeoff noise, emissions, and sonic boom, as well as economic considerations for technology integration and fuels, and integration into the current or future anticipated airport infrastructure and national airspace system. The technology roadmaps may be used to help prioritize future research activities, and to inform rulemaking discussions in areas (e.g., cosmic radiation exposure or cabin depressurization risk) for which appropriate regulations or metrics are not yet established. These roadmaps would include not only technologies centric to the feasibility and viability of the vehicle itself, but also potential aeroderivative technologies that would have a high impact to the public. These efforts may be led by the contractor in partnership with other organizations.

4.0 Description of the Work/Contractor Tasks:

Task 1: Vehicle Conceptual Design Studies

The contractor shall produce advanced vehicle conceptual designs, as well as corresponding airframe and propulsion technology roadmaps needed to enable high-speed commercial aircraft. Subtasks include the following steps:

1) Develop a near-term technology baseline vehicle conceptual design using near term technologies (e.g., TRL 6 and above) and assess system:

a) performance (e.g., maximum range and Mach number, total flight time, fuel usage per passenger mile, etc.)

b) weight

c) environmental compliance (e.g., sonic boom, landing/takeoff noise, and sea level static and cruise emissions)

2) Develop technology roadmaps (with notional timeframes and cost to mature to TRL 6) that identify what advanced technologies can be incorporated into the baseline vehicle concepts to produce advanced vehicle conceptual designs that meet thresholds and goals identified in Task 2.

3) Develop an advanced technology vehicle conceptual design (which potentially incorporates the baseline vehicle in step 1 and advanced technologies in step 2) and assess an advanced vehicle concept for:

a) performance (e.g., maximum range and Mach number, total flight time, fuel usage per passenger mile, etc.)

b) weight

c) environmental impacts (e.g., sonic boom, landing/takeoff noise, and seal level static and cruise emissions)

4) Prioritize the advanced technologies that will need to be developed to achieve the projected performance, weight, and environmental compliance.

5) Provide monthly reporting on the conceptual design and technical road mapping activity to the contract monitors.

Steps 1 and 3 include the following elements:

• Following design requirements determined in the earlier market studies and life cycle cost modeling study, develop two or more conceptual design variants for a high-speed (Mach 2-5) commercial passenger transport. One variant (see step 1) will be developed exclusively using existing high-TRL technologies, and another (see step 3) may incorporate low-TRL technologies or components (such as new engine technologies) that could feasibly be developed (considering certifiability) by 2040. Design objectives shall be based on a combination of performance metrics (e.g., fuel usage per passenger mile, flight time, or range) and environmental metrics related to sonic boom, emissions and LTO noise.

• Include sufficient fidelity in the design and analysis to meet accepted standards for detailed conceptual design, and to allow for independent analysis by Government or third parties. In particular, the conceptual design and analysis shall incorporate the following:

o Aerodynamic and propulsion force/moment databases that cover key operational points.

o Aerothermal analysis and thermal management, including cabin environmental control.

o Airframe structural analysis, potentially including thermal deformation effects.

o Packaging, subsystems, and power generation, with consideration for passenger egress and safety. Mitigation strategies for cosmic radiation exposure (particularly for flight crew) may also be considered.

o Mass property estimations.

Task 2: Environmental, Economic, and Societal Barriers Road Mapping

The contractor shall create a roadmap that identifies requirements through 2040 to enable the high-speed market from the standpoint of addressing environmental, economic, and public acceptance barriers to sustainability. Subtasks include the following steps:

1. Identify regulatory (e.g., noise), market (e.g., fuels price), infrastructure (e.g., unique airport requirements), or public acceptance (e.g., nonregulated emissions) gaps that preclude entry or sustainment of the proposed vehicle system(s) into the high-speed market.

a. Quantify threshold (minimum viable product) and goal (ideal solution) for all key metrics.

b. Identify and quantify any performance gaps relative to metric thresholds.

2. Propose technologies that are enabling in closing any threshold performance gaps and enhancing in meeting performance goals.

a. Identify discrete technologies and quantified effects on metrics of interest.

b. For discrete technologies, identify any dependencies, current technology readiness levels, development cost, and expected timeline to TRL 6.

c. Identify each technology as enabling or enhancing relative to the defined threshold and goal for each metric.

d. Identify any residual gaps where the technology doesn’t enable meeting the threshold requirement.

3. Provide monthly reporting on the road mapping activity to the contract monitors.

4. Report on the road mapping effort

a. Summarize the technology items in tabular format

b. Graphically present a technology roadmap for a minimally viable product, as well as any identified remaining gaps that would need to be resolved without technology.

c. Graphically present a technology roadmap for a goal product, as well as any identified remaining gaps that would need to be resolved without technology.

• Aircraft mass properties for maximum takeoff, empty, payload, and propellant weights in units of pounds mass, including breakouts of structure, propulsion, payload, and subsystems.

• Aircraft center of gravity position and moments of inertia at key operating points.

• Aircraft sideline, lateral, and approach noise assessment in EPNL

• Aircraft cruise overpressure noise in PLdB

• Aircraft sea level static and cruise emissions reported as indices of CO2, H2O, SOx, and NOx in units of g/kg as well as total mission emissions in units of kg.

• Diagrams and/or models of aircraft packaging, including cabin, cockpit, fuel tanks, stowage, major subsystems, and landing gear (stowed and deployed).

• Structural layout and design information, including information of primary and secondary structural materials or layups.

• Aircraft power requirements at key operational points.

• Aircraft concept of operations, including information on assumptions and constraints, modes of nominal and off-nominal operation, definition of flight phases, nominal climb, cruise, and descent information, flight envelope (e.g., V-n diagram), ground system requirements, airport requirements (e.g., runway length).

Task 2: Road Mapping

• Listing of potential technologies, including dependencies, current TRL, and quantified impact to metrics of interest in Excel format.

• Graphical presentation of roadmaps in PowerPoint format.

Tasks 1 – 2 • Monthly status presentations in PowerPoint format, presented in a virtual meeting.

• One mid-term presentation in PowerPoint format, presented in either a live or virtual meeting.

• Final vehicle conceptual design and technology roadmap written report in Word format

• Final vehicle conceptual design and technology roadmap presentation in PowerPoint format, presented in either a live or virtual meeting.

Other Considerations:

Applicable Documents/Background:

The final briefings and reports from the 2020 HTP-funded market studies are publicly available and can be found on the NASA Technical Reports Server at the following links for

• the SAIC final report (https://ntrs.nasa.gov/citations/20210015471) and presentation (https://ntrs.nasa.gov/citations/20210015472); and

• the Deloitte final report (https://ntrs.nasa.gov/citations/20210014711) and presentation (https://ntrs.nasa.gov/citations/20210014932).

• University of Arlington Aerospace Vehicle Design Laboratory final report, “Hypersonic, Commercial Transportation Feasibility Study,” NASA Contract No. NNL13AA08B, Task Order No.

80LARC20F0015.

6.0 Points of Contact:

Contracting Officer (CO) Name: Rita Dickens Phone: (216) 433-3805 Email: Rita.K.Dickens@nasa.gov

Contracting Officer’s Representative (COR) Name: Erik Axdahl Phone: (757) 864-8318 Email: Erik.L.Axdahl@nasda.gov

Alternate Contracting Officer’s Representative (ACOR) Name: Jonathan Burt Phone: (216) 433-3431 Email: Jonathan.M.Burt@nasa.gov

(End of SOW)

C.2 GRC 52.255-90 TECHNICAL DIRECTION (APR 2016)

(a) Performance of the work under this contract is subject to the technical direction of the Contracting Officer (CO) or the designated Contracting Officer’s Representative (COR).

(b) ""Technical direction"" means a directive to the Contractor that provides clarification of the contract’s general description of the scope of work, to include approaches, solutions, designs, refinements or shifts within tasks, or inquiries related to the general tasks and requirements in the statement of work or specifications.

(c) Technical Direction does not include any instruction that—

(1) Constitutes an assignment of additional work outside the statement of work (i.e. “new work”;

(2) Constitutes a change as defined in the changes clause;

(3) Constitutes a basis for any increase or decrease in the total price, any milestone price, or the time required for performance or delivery;

(4) Changes any of the expressed terms, conditions, or specifications of the contract; or

(5) Interferes with the contractor's rights to perform the terms and conditions of the contract.

(6) Changes any performance-based requirement.

(d) All technical direction will be issued in writing by the CO or the designated COR.

(e) The Contractor shall proceed promptly with the performance of technical direction issued by the CO or COR, unless, in the Contractor's opinion, any instruction or direction falls within any of the categories defined in paragraph (c) of this clause. In the latter event, the Contractor shall not proceed but shall within 5 working days notify the CO in writing of the basis for its opinion. Within 30 calendar days of receiving this notification, the CO will either amend the technical direction, request a proposal for an amendment to the contract or Task Order, advise the Contractor in writing that the technical direction is considered to be within the limits of this clause and that the Contractor should proceed promptly with its performance, or rescind the technical direction in its entirety.

(f) A failure of the Contractor and CO to agree that the instruction or direction is both within the requirements of the contract and does not constitute a change under the changes clause, or a failure to agree upon the contract action to be taken with respect to the instruction or direction, shall be subject to the Disputes clause of this contract.

(g) Any action(s) taken by the Contractor in response to any direction given by any person other than the CO or the designated COR shall be at the Contractor's risk.

C.3 DATA RIGHTS

Technical information, results, and reports developed during this program are expected to be publicly available to U.S. industries, the U.S. Government, and U.S. academia with the following exceptions:

• The information, results and reports shall be controlled per the International Traffic in Arms Regulations (ITAR) and the Export Administration Regulations (EAR) where appropriate.

• Limited rights data and restricted computer software delivered in accordance with 52.227-14 ALT II and ALT III (Dec 2007)

All deliverables/items delivered to NASA will have the markings as specified in 52.227-14 ALT II and ALT III and ALT V. The full version of the clauses can be found in Section I of the contract.

C.4 IDENTIFICATION AND REPRESENTATION OF LIMITED RIGHTS DATA AND RESTRICTED

COMPUTER SOFTWARE (COMBINED CLAUSE)

(a) This clause does not apply to restrictions based solely on copyright.

(b) Consistent with FAR 52.227-15(b), Limited Rights Data and Restricted Computer Software to be delivered in performance of this contract will be identified and listed pursuant to this clause. The Contractor shall not deliver any data in performance of this contract with restrictive or limiting markings unless the data are listed herein or later identified and certified by the Contractor that such data qualify as Limited Rights Data or Restricted Computer Software in accordance with their respective definitions in FAR 52.227-14(a), as specified in paragraph (c) of this clause.

(c) Pre-Award Identification. Pre-award identification of Limited Rights Data or Restricted Computer Software shall be made in the following format and completed on Attachment J.1.1 to Section J.1, List of Attachments.

(Start of identification and representation)

The Contractor represents it has accurately identified, through recorded information, the stages of technical development and the source of funds at a lowest segregable level pertaining to an item, component, process, or computer software, and hereby certifies that the data related thereto and identified below qualify as Limited Rights Data or Restricted Computer Software in accordance with their respective definitions in FAR 52.227-14(a):

Technical Data* or Computer Software** to be Furnished with Restrictions

Basis for Representation***

Represented Rights Category****

Name of Person Representing Restrictions*****

Contractor Fill-in ****** Contractor Fill-in ****** Contractor Fill-in ****** Contractor Fill-in ******

* A representation of limited rights data is applicable to a lowest segregable level pertaining to an item, component, or process. Identify the lowest level pertaining to an item, component, or process.

** A representation of restricted computer software is applicable to a lowest segregable level pertaining to computer software. Identify the lowest segregable level pertaining to computer software.

*** Generally, the development of an item, component, process, or computer software at private expense is the only basis for representing limited or restricted rights on the Government. If development was not at private expense, enter the specific reason for asserting that the Government’s right should be limited or restricted.

**** Enter represented rights category (e.g., limited rights, restricted rights, SBIR rights).

***** Corporation, individual, or other person, as appropriate.

Date

Printed Name and Title

Signature

(End of identification and representation)

(d) Post-Award Identification. In addition to the representations made within this clause, other representations may be made after award when based on new information or inadvertent omission unless the inadvertent omission would have materially affected the Government’s source selection decision, a payment decision, or both. Such identification and representations may be made after award whereby the Contractor shall submit a request to the Contracting Officer as soon as practicable after initial identification in the following format and signed by an official authorized to contractually obligate the Contractor. The Contracting Officer will consider such a request and determine whether or not to accept the request by incorporating it in a contract modification. Such post-award identification shall be made in the following format:

(Start of identification and representation)

Identification and Representation of Limited Rights Data and Restricted Computer Software

The Contractor asserts additional data not previously identified pursuant to the IDENTIFICATION AND REPRESENTATION OF LIMITED RIGHTS DATA AND RESTRICTED COMPUTER SOFTWARE clause and required to fulfill the data delivery requirements qualify as limited rights data or restricted computer software. The Contractor represents it has accurately identified, through recorded information, the stages of technical development and the source of funds at a lowest segregable level pertaining to an item, component, process, or computer software. Furthermore, the Contractor represents it has verified such recorded information and hereby certifies that the data identified below qualify as limited rights data or restricted computer software in accordance with their respective definitions in FAR 52.227-14(a):

Technical Data* or Computer Software** to be Furnished with Restrictions

Basis for Representation***

Represented Rights Category****

Name of Person Representing Restrictions*****

Contractor Fill-in ****** Contractor Fill-in ****** Contractor Fill-in ****** Contractor Fill-in ******

* A representation of technical data asserted as limited rights data is applicable to a lowest segregable level pertaining to an item, component, or process. Identify the lowest segregable level pertaining to an item, component, or process.

** A representation of restricted computer software is applicable to a lowest segregable level pertaining to computer software. Identify the lowest segregable level pertaining to computer software.

*** A representation of other data shall be made at a lowest segregable level (i.e., broad descriptions are generally unacceptable due to indefiniteness). Generally, the development data entirely at private expense is the only basis for representing limited or restricted rights on the Government. If development was not at private expense, enter the specific reason for asserting that the Government’s rights should be limited or restricted.

**** Enter represented rights category (e.g., limited rights, restricted rights, SBIR rights).

***** Corporation, individual, or other person, as appropriate.

******Contractor fill-in after award as applicable.

Date

Printed Name and Title

Signature

(End of identification and representation)

(e) If requested by the Contracting Officer, the Contractor shall provide sufficient recorded information to justify the validity of limited rights data or restricted computer software identified in this clause. Such written justification shall include historical documentary evidence that clearly identifies the stages of technical development and the source of funds at a lowest segregable level pertaining to an item, component, process, or computer software. Conclusory statements without supporting historical documentary evidence shall constitute a failure to provide written justification to substantiate the propriety of the markings. Costs and expenses associated with providing sufficient recorded information to justify the validity of limited rights data or restricted computer software are unallowable costs under this contract. The Contractor shall substantiate its limited rights data or restricted computer software assertions at its own expense.

(f) Based on the Contractor’s actions or deliberate inaction, an omission regarding failing to identify data or a failure by the Contractor to identify, analyze, or verify data as described in this clause may be deemed as an act in deliberate ignorance or reckless disregard of the truth or falsity of the information. The Contractor may not rely on past or commensurate actions or inactions by the Government regarding data not previously identified to the Government as limited rights data or restricted computer software yet delivered to the Government with restrictive or limiting markings and actually or constructively accepted by the Government.

(g) Subcontracting. If applicable, the Contractor shall obtain from its subcontractors sufficient recorded information to justify the validity of limited rights data or restricted computer software identified in this clause necessary to fulfill the Contractor’s obligation in paragraph (e) of this clause. If a subcontractor refuses to accept terms affording the Contractor to provide such sufficient recorded information to the Contracting Officer, the Contractor shall promptly notify the Contracting Officer of the refusal and shall not proceed with the subcontract award without authorization in writing from the Contracting Officer.

SECTION E – INSPECTION AND ACCEPTANCE

E.1 52.246-9 INSPECTION OF RESEARCH AND DEVELOPMENT (SHORT FORM) (APR 1984)

E.2 GRC 52.246-92 INSPECTION AND ACCEPTANCE (JAN 1987)

Final inspection and acceptance of all work performed under this contract, including all deliverable items will be performed at destination.

SECTION F – DELIVERIES OR PERFORMANCE

F.1 52.242-15 STOP-WORK-ORDER (AUG 1989)

F.2 52.242-17 GOVERNMENT DELAY OF WORK (APR 1984)

F.3 PERIOD OF PERFORMANCE

The period of performance of this contract is 12 months.

F.4 PLACE OF PERFORMANCE – SERVICES

The services to be performed under this contract shall be performed at the following locations(s):

Contractor’s Facility.

SECTION G – CONTRACT ADMINISTRATION DATA

G.1 1852.227-70 NEW TECHNOLOGY – OTHER THAN A SMALL BUSINESS FIRM OR NONPROFIT

ORGANIZATION (APR 2015)

[Included if contractor is other than a small business firm or a nonprofit organization]

G.2 1852.227-71 REQUESTS FOR WAIVER OF RIGHTS TO INVENTIONS (APR 2015)

[Included if contractor is other than a small business firm or a nonprofit organization]

G.3 1852.227-72 DESIGNATION OF NEW TECHNOLOGY REPRESENTATIVE AND PATENT

REPRESENTATIVE (APR 2015)

[Included if contractor is other than a small business firm or a nonprofit organization]

G.4 1852.232-80 SUBMISSION OF VOUCHERS/INVOICES FOR PAYMENT (APR 2018)

(a) The designated payment office is the NASA Shared Services Center (NSSC) located at FMD Accounts Payable, Bldg. 1111, Jerry Hlass Road, Stennis Space Center, MS 39529.

(b) Except for classified vouchers, the Contractor shall submit all vouchers and invoices using the steps described at NSSC’s Vendor Payment information web site at:

https://www.nssc.nasa.gov/vendorpayment. Please contact the NSSC Customer Contact Center at 1-877- NSSC123 (1-877-677-2123) with any additional questions or comments.

Fee vouchers shall be separate submissions from vouchers for cost reimbursement. Credit memos for amounts owed back to NASA shall be separate submissions with the same documentation requirements as (c)(2)(i) below.

(c) Payment requests.

(1) The payment periods are stipulated in the payment clause(s) contained in this contract.

(2) Vouchers submitted under cost-type contracts and invoices submitted under fixed-price contracts shall include the items delineated in FAR 32.905(b) supported by relevant back-up documentation. Back-up documentation shall include at a minimum, the following information:

(i) Vouchers.

(A) Breakdown of billed labor costs and associated contractor generated supporting documentation for billed direct labor costs to include rates used and number of hours incurred.

(B) Breakdown of billed other direct costs (ODCs) and associated contractor generated supporting documentation for billed ODCs.

(C) Indirect rate(s) used to calculate the amount of billed indirect expenses.

(D) Progress reports, as required.

(ii) Invoices.

(A) Description of goods and services delivered as part of the contract’s terms and conditions, including the dates of delivery/performance.

(B) Progress reports, as required.

(C) Date goods and services were performed.

(iii) Fee vouchers.

(A) Listing of all provisionally-billed fee by period or date earned since contract award.

(B) A reconciliation of all billed and earned fee.

(C) A clear explanation of the fee calculations.

(d) Non-electronic payment requests. The Contractor may submit a non-electronic voucher/invoice using the steps for non-electronic payment requests described at https://www.nssc.nasa.gov/vendorpayment, when any of the following conditions are met:

(1) The Contracting Officer administering the contract for payment has determined, in writing, that electronic submission would be unduly burdensome to the Contractor.

(2) The contract includes provisions allowing the contractor to submit vouchers or invoices using the steps for non-electronic payment requests. In such instances the Contractor agrees to submit non electronic payment requests using the method or methods specified in Section G of the contract.

(e) Improper vouchers/invoices. The NSSC Payment Office will notify the contractor of any apparent error, defect, or impropriety in a voucher/invoices within seven calendar days of receipt by the NSSC Payment Office. Inquiries regarding requests for payment should be directed to the NSSC as specified in paragraph

(b) of this section.

(f) Other payment clauses. In addition to the requirements of this clause, the Contractor shall meet the requirements of the appropriate payment clauses in this contract when submitting payment requests.

(g) In the event that amounts are withheld from payment in accordance with provisions of this contract, a separate payment request for the amount withheld will be required before payment for that amount may be made.

Contractor more than the amount from time to time allotted to the contract, anything to the contrary in the Termination for Convenience of the Government clause notwithstanding.

(c)(1) It is contemplated that funds presently allotted to this contract will cover the work to be performed until [TBD].

(2) If funds allotted are considered by the Contractor to be inadequate to cover the work to be performed until that date, or an agreed date substituted for it, the Contractor shall notify the Contracting Officer in writing when within the next 60 days the work will reach a point at which, if the contract is terminated pursuant to the Termination for Convenience of the Government clause of this contract, the total amount payable by the Government (including amounts payable for subcontracts and settlement costs) pursuant to paragraphs (f) and (g) of that clause will approximate 75 percent of the total amount then allotted to the contract.

(3)(i) The notice shall state the estimate when the point referred to in paragraph (c)(2) of this clause will be reached and the estimated amount of additional funds required to continue performance to the date specified in paragraph (c)(1) of this clause, or an agreed date substituted for it.

(ii) The Contractor shall, 60 days in advance of the date specified in paragraph (c)(1) of this clause, or an agreed date substituted for it, advise the Contracting Officer in writing as to the estimated amount of additional funds required for the timely performance of the contract for a further period as may be specified in the contract or otherwise agreed to by the parties.

(4) If, after the notification referred to in paragraph (c)(3)(ii) of this clause, additional funds are not allotted by the date specified in paragraph (c)(1) of this clause, or an agreed date substituted for it, the Contracting Officer shall, upon the Contractor's written request, terminate this contract on that date or on the date set forth in the request, whichever is later, pursuant to the Termination for Convenience of the Government clause.

(d) When additional funds are allotted from time to time for continued performance of the work under this contract, the parties shall agree on the applicable period of contract performance to be covered by these funds. The provisions of paragraphs (b) and (c) of this clause shall apply to these additional allotted funds and the substituted date pertaining to them, and the contract shall be modified accordingly.

(e) If, solely by reason of the Government's failure to allot additional funds in amounts sufficient for the timely performance of this contract, the Contractor incurs additional costs or is delayed in the performance of the work under this contract, and if additional funds are allotted, an equitable adjustment shall be made in the price or prices (including appropriate target, billing, and ceiling prices where applicable) of the items to be delivered, or in the time of delivery, or both.

(f) The Government may at any time before termination, and, with the consent of the Contractor, after notice of termination, allot additional funds for this contract.

(g) The provisions of this clause with respect to termination shall in no way be deemed to limit the rights of the Government under the default clause of this contract. The provisions of this Limitation of Funds clause are limited to the work on and allotment of funds for the items set forth in paragraph (a) of this clause. This clause shall become inoperative upon the allotment of funds for the total price of said work except for rights and obligations then existing under this clause.

(h) Nothing in this clause shall affect the right of the Government to terminate this contract pursuant to the Termination for Convenience of the Government clause of this contract.

H.5 1852.235-71 KEY PERSONNEL AND FACILITIES (MAR 1989)

(a) The personnel and/or facilities listed below (or specified in the contract Schedule) are considered essential to the work being performed under this contract. Before removing, replacing, or diverting any of the listed or specified personnel or facilities, the Contractor shall—

(1) Notify the Contracting Officer reasonably in advance; and

(2) Submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this contract.

(b) The Contractor shall make no diversion without the Contracting Officer's written consent; provided, that the Contracting Officer may ratify in writing the proposed change, and that ratification shall constitute the Contracting Officer's consent required by this clause.

(c) The list of personnel and/or facilities (shown below or as specified in the contract Schedule) may, with the consent of the contracting parties, be amended from time to time during the course of the contract to add or delete personnel and/or facilities.

*Personnel and Facilities shall be as proposed*

H.6 GRC 1852.235-74 GRC MODIFICATION TO NFS 1852.235-74 – ADDITIONAL REPORTS OF WORK –

RESEARCH AND DEVELOPMENT (JAN 2014)

In addition to the final report required under this contract, the Contractor shall submit the following report(s) to the Contracting Officer’s Representative:

(a) Monthly progress reports. The Contractor shall submit separate monthly reports of all work accomplished during each month of contract performance. Reports shall follow the formatting and content guidelines identified in the Statemen of Work in Section C.

(b) Report Format. All reports shall include the contents below.

(i) Cover page containing:

(A) Contract number, Task Order Number (if applicable), and title.

(B) The type of report "Monthly Progress Report", and the period being reported.

(C) Contractor's name, address, and organizational segment generating the report.

(D) Signature of Contractor's cognizant Project Manager (or, if submitted electronically, an unambiguous indicator that the Project Manager has generated/reviewed the report)

(E) Date of issuance.

(F) Inclusion of the following statement: ""Prepared for NASA Glenn Research Center, Cleveland, OH 44135.""

(ii) Section I -- Technical Progress Summary: A description of the work performed during the report period and the overall technical progress achieved. The current schedule status shall also be addressed in this summary.

(iii) Section II -- Current Problem(s): A description of any current problem(s) which may impede technical, schedule and/or cost performance, along with proposed corrective action(s). Include an explanation of how the problems could affect the cost and schedule of the reporting categories in the financial and schedular reports if applicable, as well as the effects at the total contract level.

(iv) Section III -- Risk Management: Include a list of Significant Open Risks and associated Mitigation Plans. Significant Open Risks are those that have the potential to affect major development milestones & goals, such as a delivery delay, a design-freeze date, a cost ceiling, a safety or health concern, environmental impacts, a technical trade-off decision, etc. Further guidance, if needed, is available in the following Risk Management reference documents, which are available through the NASA Online Directives Information System (NODIS):

(A) NPR 8000.4, ""Agency Risk Management Procedural Requirements""

(B) GLPR 8000.1, “Risk Management""

(v) Section IV -- Work Planned: A description of the work to be performed during the next monthly reporting period.

(c) Submission dates. Monthly reports shall be submitted by the 15th day of the month following the month being reported. If the contract is awarded beyond the middle of a month, the first monthly report shall cover the period from award until the end of the following month. The final report shall be submitted within 30 days after the completion of the effort under the contract.

H.7 GRC 52.235-90 FINAL REPORT – SUPPLEMENTAL REQUIREMENTS (MAY 2018)

The following requirements are in addition to those stated in the Final Scientific and Technical Reports clause (1852.235-73) of this contract.

(1) In addition to the requirements of NPR 2200.2, Requirements for Documentation, Approval, and Dissemination of NASA Scientific and Technical Information, the format and content of the Final Report shall also follow NASA-SP-2015-7602 ""NASA Publications Guide for Authors"", incorporated herein by reference and made a part hereof. These documents are available at http://www.sti.nasa.gov [Click on ""Tools"" and then “NASA Publication Guide.”

(2) The Contractor shall submit an electronic copy of a DRAFT-FINAL REPORT to the NASA Contracting Officer’s Representative (COR) within 30 days after completion of the technical effort. The COR's review will address technical accuracy, conformance with applicable law, policy and publication standards, and a determination of the availability and distribution of NASA-funded documents containing scientific and technical information (STI), via the Web-based Electronic Document Availability Authorization (E- DAA)/NF-1676B. Acceptance or rejection (in part or in total) of the draft-final report will be accomplished by NASA within thirty (30) days after receipt. Rejected draft-final reports shall be resubmitted within 10 working days for review following correction of the cited deficiency, unless otherwise directed by the NASA CO or NASA COR.

(3) Within thirty (30) calendar days after notification of approval of the Contractor's draft-final report, the Contractor shall distribute the approved Final Report electronically to the COR.

(4) Printing, duplicating, binding and other reproduction required under this contract is subject to the provisions of the Government Printing and Binding Regulations published by the Joint Committee on Printing, Congress of the United States and the clause at NFS 1852.208-81 entitled ""Restrictions on Printing and Duplicating"".

(5) The Contractor is solely responsible for managing the technical effort, the schedule, and the contract funds to ensure delivery of the Draft-Final Report and the Final Report on time. Failure to deliver the Final Report as scheduled, or a request that additional funding be provided by the government to ensure delivery of the Final Report, may result in a Performance Evaluation of ""Unsatisfactory” or a reduction in profit/fee equal to the additional cost associated with delivery of the Final Report, or both.

(6) IF THIS IS A TASK ORDER CONTRACT, the Contractor shall comply with this Final Report requirement for every individual Task Order at the time of Task Order completion. However, the Contractor is not required to provide a comprehensive Final Report for the entire contract.

H.8 1852.244-70 GEOGRAPHIC PARTICIPATION IN THE AEROSPACE PROGRAM (APR 1985)

SECTION I – CONTRACT CLAUSES

I.1 52.202-1 DEFINITIONS (JUN 2020)

I.2 52.203-3 GRATUITIES (APR 1984)

I.3 52.203-5 COVENANT AGAINST CONTINGENT FEES (MAY 2014)

I.4 52.203-6 RESTRICTIONS ON SUBCONTRACTOR SALES TO THE GOVERNMENT (JUN 2020)

I.5 52.203-7 ANTI-KICKBACK PROCEDURES (JUN 2020)

I.6 52.203-8 CANCELLATION, RECISSION, AND RECOVERY OF FUNDS FOR ILLEGAL OR IMPROPER

ACTIVITY (MAY 2014)

I.7 52.203-10 PRICE OR FEE ADJUSTMENT FOR ILLEGAL OR IMPROPER ACTIVITY (MAY 2014)

I.8 52.203-12 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN FEDERAL TRANSACTIONS (JUN

2020)

I.9 52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL CONFIDENTIALITY AGREEMENTS

OR STATEMENTS (JAN 2017)

I.10 52.204-4 PRINTED OR COPIED DOUBLE-SIDED ON POSTCONSUMER FIBER CONTENT PAPER

(MAY 2011)

I.11 52.204-10 REPORTING EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT AWARDS

(JUN 2020)

I.12 52.204-13 SYSTEM FOR AWARD MANAGEMENT MAINTENANCE (OCT 2018)

I.13 52.204-18 COMMERCIAL AND GOVERNMENT ENTITY CODE MAINTENANCE (AUG 2020)

I.14 52.204-19 INCORPORATION BY REFERENCE OF REPRESENTATIONS AND CERTIFICATIONS (DEC

2014)

I.15 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION SYSTEMS (NOV

2021)

(a) Definitions. As used in this clause—

Covered contractor information system means an information system that is owned or operated by a contractor that processes, stores, or transmits Federal contract information.

Federal contract information means information, not intended for public release, that is provided by or generated for the Government under a contract to develop or deliver a product or service to the

Government, but not including information provided by the Government to the public (such as on public websites) or simple transactional information, such as necessary to process payments.

Information means any communication or representation of knowledge such as facts, data, or opinions, in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual (Committee on National Security Systems Instruction (CNSSI) 4009).

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information (44 U.S.C. 3502).

Safeguarding means measures or controls that are prescribed to protect information systems.

(b) Safeguarding requirements and procedures.

(1) The Contractor shall apply the following basic safeguarding requirements and procedures to protect covered contractor information systems. Requirements and procedures for basic safeguarding of covered contractor information systems shall include, at a minimum, the following security controls:

(i) Limit information system access to authorized users, processes acting on behalf of authorized users, or devices (including other information systems).

(ii) Limit information system access to the types of transactions and functions that authorized users are permitted to execute.

(iii) Verify and control/limit connections to and use of external information systems.

(iv) Control information posted or processed on publicly accessible information systems.

(v) Identify information system users, processes acting on behalf of users, or devices.

(vi) Authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.

(vii) Sanitize or destroy information system media containing Federal Contract

Information before disposal or release for reuse.

(viii) Limit physical access to organizational information systems, equipment, and the respective operating environments to authorized individuals.

(ix) Escort visitors and monitor visitor activity; maintain audit logs of physical access; and control and manage physical access devices.

(x) Monitor, control, and protect organizational communications (i.e., information transmitted or received by organizational information systems) at the external boundaries and key internal boundaries of the information systems.

(xi) Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.

(xii) Identify, report, and correct information and information system flaws in a timely manner.

(xiii) Provide protection from malicious code at appropriate locations within organizational information systems.

(xiv) Update malicious code protection mechanisms when new releases are available.

(xv) Perform periodic scans of the information system and real-time scans of files from external sources as files are downloaded, opened, or executed.

(2) Other requirements. This clause does not relieve the Contractor of any other specific safeguarding requirements specified by Federal agencies and departments relating to covered contractor information systems generally or other Federal safeguarding requirements for controlled unclassified information (CUI) as established by Executive Order 13556.

(c) Subcontracts. The Contractor shall include the substance of this clause, including this paragraph ©, in subcontracts under this contract (including subcontracts for the acquisition of commercial products or commercial services, other than commercially available off-the-shelf items), in which the subcontractor may have Federal contract…