Related PWS Section Answer/Response

1 Does this work include scope of work that is currently on PESS? Full Yes, PEMSS is a new requirement that encompasses portions of PESS II and selectively incorporates limited existing work from FILMSS II and other contracts, with the majority of FILMSS II scope supported through other means.

2 Is this set aside for small business? Set-Aside Yes.

3 Why the NAICS Code change? NAICS Code

The NAICS code for an acquisition must be selected based on the principal purpose and actual work requirements of the contract, not solely on which classification qualifies more contractors as small businesses. As such, the principal purpose aligns more closely with NAICS 541715, which covers scope requirements primarily in support of research and experimental development in physical, engineering, and life sciences. Due to this the NAICS Code has been updated from 541330 to 541715.

4 Is this considered a new requirement? Full See response to question 1 above.

5 Could you provide the incumbent contractor, contract number, and contract value? Full As this is a new requirement incumbent contractor information is not fully applicable.

6 Name of the Labor Category Spreadsheet shows PRESS vs. PEMSS Labor Category Excel Spreadsheet The name has evolved over time and the Labor Categories Title will be updated on subsequent posting to reflect the updated name to PEMSS.

7 PWS Pages ae not extractable is there a way to make them extractable? Full

If the PWS PDF pages are not currently extractable, you may still be able to view them using standard PDF reader software such as Adobe Acrobat Reader or similar applications. If you are experiencing difficulty accessing or viewing the pages, please ensure you have the latest version of your PDF viewer installed. In the meantime, the pages should remain viewable for reading and reference within the PDF application.

Does NASA intend to compete PEMSS as a total small business set-aside, or full and open? The draft PWS spans electrical and electronics, thermal, fluid mechanics, cryogenics, sensors and instrumentation, controls, microfluidics, chemical and biological and biomedical support, metal fabrication and machining, facility and laboratory operations, and programmatic support. The determination materially affects whether specialist small businesses position as prime with a subcontractor team or as a subcontractor to a large integrator, and firms need it before investing in teaming agreements. Set-Aside

NASA intends on competing PEMSS as a small business total set aside and therefore subcontracting goals will not be required.

Please confirm the NAICS code assigned to PEMSS. PWS 4.1.15 (Metal Fabrication, Machining, and Instrumentation), 4.1.16 (Mechanical Hardware), 4.1.17 (Electronics), and 4.1.20 (Space Shop) describe fabrication, assembly, and manufacturing work rather than professional services. Will a single services NAICS code apply to the entire contract, or will any portion carry a separate manufacturing NAICS code with its own size standard? NAICS Code

See response to question 3 above.

The Industry Day labor category file is titled "Project, Research, Engineering, and Science Services (PRESS) Labor Category Descriptions," and its column F header reads "Technical Discipline(s) (as utilized by PESS II/FILMSS II)." Neither acronym matches PEMSS. Please confirm that this file is the labor category basis for PEMSS, and clarify whether PRESS reflects a planned change to the acquisition name or is a reference to a separate contract vehicle. Labor Category Excel Spreadsheet

The name has evolved over time and the Labor Categories Title will be updated on subsequent posting to reflect the updated name to PEMSS.

Draft PWS paragraph 4.1.7 is titled "Proposal and Solicitation Support," but paragraphs 4.1.7.1 through 4.1.7.6 describe engineering disciplines (thermal, fluid mechanics, cryogenic, electrical/electronics, sensors and instrumentation, and chemical/biological/biomedical/radioactive systems) that are unrelated to proposal support. The same numbering is carried in the Industry Day Data Sheet. Is this the intended structure, or will the engineering discipline paragraphs be renumbered in the final PWS? Offerors will cite these paragraph numbers in capability and past performance narratives, and a renumbering after submission would break those references. 4.1.7 Proposal and Solicitation Support

The current structure of Draft PWS is subject to change and the final PWS will be posted with the Request For Proposal (RFP).

PWS 2.0 states that the majority of work will be performed on-site at NASA Ames. Will the solicitation specify a minimum on-site percentage, or a required number of on-site days per week or per task order? On-site and off-site labor are priced differently, and the on-site share drives assumptions about badging, workspace, and facility access. Without a stated minimum, offerors will price the same requirement against different assumptions and the cost proposals will not be directly comparable. 2.0 Scope

The expectation is for the selected contractor to demonstrate the ability to staff and fulfill requirements as they evolve throughout the contract period. This work will be broken-out at the Technical Directive/Work Package Level, and the requirements may vary depending on the specific nature of the tasks and the organization requesting the work. As such, the Government may specify anticipated on-site percentages at the task order level based on the needs of each Technical Directive/Work Package. Further solicitation instructions and evaluation criteria will be posted in the Draft RFP.

PWS 4.1.7.4 states the Contractor shall use Government-provided Altium, Orcad/Cadence, and LabView. Please clarify whether the requirement is use of those specific tools, or delivery in the native and neutral formats they produce under Government configuration control. If an equivalent commercial tool delivers in the required native or neutral format, will NASA accept it as meeting the requirement? Please also confirm how many seats of each Government-provided tool will be furnished, and whether that count is per contract or per task order, since license availability constrains how many personnel can perform the task concurrently. 4.1.7.4 Electrical/Electronics

File formats will be determined at the Technical Directive/Work Package Level, and the requirements may vary depending on the specific nature of the tasks and the organization requesting the work.

Similarly, the number of seats for Government-provided tools will be subject to the nature of the work and organization.

PWS 4.1.7.5.2 combines payload and instrument power system design with ARC facility electrical scope, specifically the ARC Electrical Distribution Systems, the Protective Relay System, the Ames Power Monitoring System, and Government-provided SKM software. These are distinct disciplines with different qualifications. Will NASA separate them into distinct task areas or work packages, so that a firm qualified in payload and instrument power electronics can be evaluated on that scope without also demonstrating facility distribution and protective relay experience? 4.1.7.5.2 Power Systems Design and Development

Evaluation criteria will be released with the Draft RFP.

If NASA establishes a small business subcontracting goal for PEMSS, will it be expressed as a percentage of total contract value or as a percentage of subcontracted value? For an effort of this type, prime-retained program management, facility operations, and continuously staffed on-site work can constitute a large share of total value, so a total-value denominator can be satisfied without engaging specialist small businesses. A subcontracted-value denominator is measurable at award rather than only in retrospect. Subcontracting Goals

NASA will not be establishing small business subcontracting goals as this acquisition will be a total small business set-aside and the requirements for a small business subcontracting plan is not applicable. Teaming with similarly situated entities is recognized under FAR 52.219-14 for the purposes of limitations on subcontracting. According to the regulation, work performed by similarly situated entities counts toward the prime contractor’s performance requirements. Similarly Situated entities include those small businesses that have the same small business program status as that which qualified the prime contractor for the award (e.g., for a small business set-aside contract, any small business concern, without regard to its socioeconomic status); and is considered small for the size standard under the North American Industry Classification System (NAICS) code the prime contractor assigned to the subcontract.

16 Will the presentation slides be provided after this event? Full Yes, the presentation slides and interested vendors list have been posted after the event. We will continue to update the posting attachments to include the master Q&A spreadsheet as they are completed.

17 What's the process for requesting the use of NASA facilities for SBIR's? Select from drop down Please reach out to https://www.nasa.gov/sbir_sttr/ and they will be happy to assist you further 18 Can NASA share their rationale for selecting NAICS 541330? NAICS Code See response to question 3 above.

Is PEMSS considered a consolidation of portions of the existing PESS II and FILMSS II requirements, or a new requirement that incorporates selected existing work? Set-Aside

See response to question 1 above.

Section 3.0 requires the Contractor to maintain a Facility Clearance at the Top Secret level per Exhibit F (DD254). Is this requirement flowed down to all subcontractors regardless of scope, or is it required of the Prime only, with uncleared subcontractors permitted to perform unclassified work such as fabrication, engineering analysis, software, and data support? 3.0 Contract Management

The draft RFP language is currently under development, and NASA intends to provide further guidance and clarification on how Facility Clearance requirements are applied to subcontractors versus the Prime Contractor. At this stage, it is anticipated that the requirement for a Top Secret Facility Clearance, as stipulated in the future Exhibit (DD254), will primarily apply to the Prime Contractor.

Subcontractors will only be required to maintain a Top Secret Facility Clearance if it is anticipated that they will be performing classified work. Subcontractors performing unclassified tasks—such as fabrication, engineering analysis, software development, and data support—may not be required to hold a Top Secret clearance. NASA will specify in the upcoming RFP whether uncleared subcontractors are permitted for these unclassified assignments and outline any restrictions or additional requirements. Please continue to monitor future draft RFP releases and SAM.gov updates for detailed instructions and criteria regarding Facility Clearance flow-down and subcontractor eligibility.

Section 3.6.5, Use of Artificial Intelligence (AI) During Contract Performance, is currently a placeholder referencing PIC 25-03A. Will this language be published in draft for industry review before the RFP is released? Additionally, will it govern the Contractor's internal use of AI tools during performance, AI delivered to the Government as a product or service, or both?

3.6.5 Use of Artificial Intelligence (AI During contract

Performance

NASA intends to further develop this section and publish the draft language for industry review prior to the release of the RFP. NASA will provide additional instructions and distinctions as the draft RFP is further developed, so please monitor future SAM.gov releases for detailed information regarding the scope and application of Section 3.6.5.

Section 3.6.2 requires the Contractor to define an approach to the automatic generation of software source code, including validation of the generation tools, configuration management of tool inputs and outputs, allowable scope, V&V of generated code, and policies for manual changes. Does the Government intend this section to encompass large language model based code generation, or is it scoped to model based tools such as Simulink and Embedded Coder? If it encompasses LLM based generation, how will Section 3.6.2 and Section 3.6.5 be reconciled?

3.6.2 Automatic Generation of Software Source

Code

NASA's intent is for this section to require contractors to articulate a comprehensive approach to the automatic generation of software source code, covering aspects such as tool validation, configuration management, allowable scope, verification and validation (V&V) of generated code, and policies governing manual modifications. This requirement is not limited solely to traditional model-based tools like Simulink and Embedded Coder; it is anticipated to also encompass large language model (LLM) based code generation and other AI-assisted technologies. Offerors will be expected to describe their methods and controls for utilizing LLMs and similar tools, both in the proposal phase and potentially at the work package level during contract performance, consistent with Section 3.6.2.

As the draft RFP is further developed, NASA will provide additional guidance to clarify how Section 3.6.2 and Section 3.6.5 interact, particularly regarding requirements for AI-assisted and automatically generated code. Offerors should monitor upcoming RFP releases for specific instructions, criteria, and any distinctions between these sections. NASA aims to ensure clarity and consistency in requirements, so that offerors can confidently address both traditional model-based and LLM-based code generation approaches in their proposals and during contract execution.

PEMMS Market Research Industry Day Q&A (August 13, 2026) Questions Received

Section 3.6.4, IT Security Control, is currently a placeholder. Will this language be published before the RFP, and will it establish requirements distinct from the FISMA and Authority to Operate obligations described in Section 4.1.12? 3.6.4 IT Security Control

Section 3.6.4, IT Security Control, is currently a placeholder and will be further developed and included in the draft RFP. NASA intends to publish this language prior to the release of the RFP to ensure clarity for offerors. The requirements established in Section 3.6.4 are expected to provide additional guidance and may include requirements distinct from those outlined in Section 4.1.12, which covers FISMA and Authority to Operate obligations. Offerors should monitor upcoming RFP releases for specific instructions and criteria related to IT Security Control, including any new or separate requirements.

Section 4.1.7 requires support for the development of a NASA dashboard tool covering announcements of opportunity, and for database solutions to store, access, and characterize proposal data. Is this new development or the sustainment of an existing tool? If a system of record exists today, what is it, and will its architecture and data be made available at task order start? 4.1.7 Proposal and Solicitation Support

At present, the systems supporting NASA dashboard tools for announcements of opportunity and associated proposal data—including solutions for storing, accessing, and characterizing proposals—may vary and include a mix of internal repositories and applications. Section 4.1.7 does not require exclusive use of existing tools; instead, contractors should be prepared to either sustain current systems or develop new solutions, such as integration layers, as needed to fully meet the requirements. If a system of record is currently in place, details regarding its architecture and data availability at task order start will be clarified within the work packages.

For requirements under Sections 4.1.3, 4.1.4, and 4.1.7 that would benefit from machine learning or retrieval based tooling over NASA document and proposal corpora, must all processing occur within the FISMA accreditation boundary described in Section 4.1.12? Does a NASA approved large language model service exist within that boundary today, and if not, what is the approval pathway for a contractor proposed capability?

4.1.12 Flight Project and Mission Operations

Information Technology Support

NASA’s large language model (LLM) environment is dynamic, with services and providers regularly evolving. For requirements under Sections 4.1.3, 4.1.4, and 4.1.7 that leverage machine learning or retrieval-based tools on NASA document and proposal corpora, all processing must occur within the FISMA accreditation boundary as described in Section 4.1.12. At this time, it is not possible to definitively confirm the existence of a NASA-approved LLM service within that boundary, as offerings may change. If such a service is unavailable, contractors should follow NASA’s established approval pathway for proposing new capabilities. This typically involves submitting a capability for review, ensuring compliance with NASA’s security, privacy, and accreditation requirements, and working closely with NASA stakeholders to achieve approval. Contractors are encouraged to consult Section 4.1.12 and related procurement guidance for the most current process and criteria.

Section 4.1.4 requires establishing and maintaining project operational and documentation databases including those used for requirement traceability, and mapping areas of expertise and capabilities to one another and to proposal development activities. What systems hold this content today, and is the expectation sustainment of existing repositories or development of a new integration layer across them?

4.1.4 Data Document Management and Archival

Support

At present, the specific systems housing project operational and documentation databases—including those supporting requirement traceability and mapping expertise to proposal activities—may vary and could include a range of internal tools and repositories. Section 4.1.4 does not mandate reliance solely on existing platforms; instead, responsive contractors should be prepared to either sustain current repositories or develop new solutions, such as an integration layer, to ensure full compliance with the requirements outlined in the relevant work packages.

Approximately what share of the total estimated labor hours falls within the Applied Manufacturing Division (Code RM) fabrication, machining, inspection, and production planning scope of Sections 4.1.15 through 4.1.20, as compared with the engineering, science, software, and information technology scope? This proportion materially affects whether firms specializing in a single domain can participate meaningfully.

4.1.15 Metal Fabrication, Machining, and

Instrumentation

The Government will provide the estimated WYE count by major functional area—including engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management—at the Labor Category Description level as part of the Draft Request For Proposal. Given the dynamic nature of NASA’s evolving technology landscape, any of these areas may grow or shrink over the course of the contract based on circumstances, budget, or agency direction. As a result, the ratio established at the beginning of the contract may not necessarily remain constant throughout the period of performance.

The scope spans CNC machining and welding, veterinary and animal care operations, cryogenic and thermal analysis, flight software, and mission cybersecurity. Does the Government intend a single award covering the full scope, or multiple awards segmented by capability domain? If a single award is intended, what subcontracting structure does the Government anticipate for domains outside a prime's core competency? 4.0 Technical Requirements

The Government intends to issue a single award Indefinite Delivery Indefinite Quantity (IDIQ) contract encompassing the entire scope, which includes CNC machining and welding, veterinary and animal care operations, cryogenic and thermal analysis, flight software, and mission cybersecurity. Subcontracting arrangements may be used at the contractor’s discretion to address areas outside their core competencies, but overall responsibility for performance and adaptability remains with the prime contractor.

The Labor Category Descriptions attachment is titled "Project, Research, Engineering, and Science Services (PRESS) Labor Category Descriptions," the technical discipline column is annotated "as utilized by PESS II/FILMSS II," and row 1 reads "PROPRIETARY NOTICE: Post Notice here." Is this the final labor category set for PEMSS, or an interim reference from a predecessor acquisition? Labor Category Excel Spreadsheet

The name has evolved over time and the Labor Categories Title will be updated on subsequent posting to reflect the updated name to PEMSS.

Given that the scope includes substantial metal fabrication, machining, welding, and inspection work alongside engineering services, has the Government considered whether NAICS 541330 with a $25.5M size standard is the appropriate primary code, and will any portion of the requirement be assigned an alternate NAICS? NAICS Code

See response to question 3 above.

Section 5.1 establishes a 60-day phase-in. Does the Government anticipate substantial retention of incumbent personnel, and will FAR 52.222-17, Nondisplacement of Qualified Workers, or a comparable right of first refusal apply? Small business teaming decisions depend heavily on whether staffing is expected to transfer or be recruited. 5.1 Phase-in

At this time, the Government has not made a definitive statement on the anticipated retention of incumbent personnel. The applicability of FAR 52.222-17, Nondisplacement of Qualified Workers, or a similar right of first refusal, will be clarified in the solicitation or contract documents.

Section 2.0 states the majority of work will be performed on site at NASA Ames. For labor categories supporting software, firmware, data systems, records management, technical writing, and proposal support, will remote or hybrid performance be permitted, and if so is there an anticipated on site percentage the Government will specify at the task order level? 2.0 Scope

This work will be broken-out at the Technical Directive/Work Package Level, and the requirements may vary depending on the specific nature of the tasks and the organization requesting the work. As such, the Government may specify anticipated on-site percentages at the task order level based on the needs of each Technical Directive/Work Package.

Section 4.1.7.5.10 describes the Ames Power Monitoring System as a Center wide network of power meters reporting to a central server for trend monitoring, consumption verification, usage scheduling, and utility cost control. Is the scope limited to sustainment and troubleshooting of the existing system, or would the Government consider task orders for predictive analytics, anomaly detection, and load forecasting built on the existing meter data?

4.1.7.5.10 Ames Power Monitoring System (APMS)

Applications

While the current scope emphasizes sustainment and troubleshooting of the existing system; it may be expanded to include advanced capabilities in response to future Task Orders.

Draft PWS Section 5.1 states that the Phase-in Plan will cover a 60-day phase-in period, while an approximately 30-day phase-in was described at the August 13, 2026 Industry Day. Which duration should offerors plan against, and will the PWS be updated to match in the draft RFP? 5.1 Phase-in

PWS Section 5.1 has been updated to reflect a 30-day phase-in period, aligning with the Industry Day acquisition strategy chart (slide 44). This 30-day phase-in now precedes the base period and replaces the previously referenced 60-day duration.

Section 4.1.2.3.2 covers web-based applications, technical databases, and digital infrastructure that are currently developed and operated under existing contracts. During phase-in, does NASA anticipate that system access, hosting arrangements, and operating documentation for these existing systems will be transferred to the incoming contractor, and will continuity of these systems be an evaluated element of the Phase-in Plan? 5.1 Phase-in

NASA will require the existing contractor(s) to actively facilitate the phase-in process for any new entrants selected by NASA. This support includes the timely and complete transfer of system access, hosting arrangements, and operating documentation for all web-based applications, technical databases, and digital infrastructure currently managed under existing contracts. While documentation, access, and knowledge may differ across the portfolio of tools, NASA expects that operating knowledge, credentials, and relevant procedures will be transferred to the incoming contractor in a manner that ensures minimal disruption and maintains system continuity.

The Industry Day identified PESS II (80ARC021D0001) and FILMSS II (80ARC024DA004) as the contracts PEMSS partially encompasses, with expirations in March 2027 and November 2026 respectively, and a PEMSS contract effective date of February 2027. For the FILMSS II scope that transitions to PEMSS, how does NASA anticipate bridging the interval between FILMSS II expiration and PEMSS phase-in, and will offerors be asked to address that continuity in the Phase-in Plan? 5.1 Phase-in

The timing of the award and phase in for PEMSS is intended to align with current contract scope phase out.

At the Industry Day, NASA described a contract management capability for work package and task order intake, proposal display and review, automatic reviewer notification, and reporting at the subtask and deliverable level. Is this system expected to be provided and operated by the contractor, or will NASA furnish an existing system? If contractor-provided, will the requirement appear in the draft RFP PWS? 3.0 Contract Management

The contract management system described will be provided and operated by the contractor.

Sections 3.6.4 (IT Security Control) and 3.6.5 (Use of Artificial Intelligence During Contract Performance) are currently placeholders in the draft PWS. Will both be populated in the draft RFP, and does NASA anticipate that offerors will be asked to describe their approach to AI-assisted and automatically generated source code, consistent with Section 3.6.2, in the proposal or at the work package level during performance?

3.6.5 Use of Artificial Intelligence (AI During contract

Performance

The forthcoming language for the reserved language in Sections 3.6.5 and 3.6.4 will be added for the Draft RFP posting and will address contractor use of AI-assisted engineering and software development tools by requiring compliance with NASA's IT security, privacy, and risk assessment requirements for all AI systems used during contract performance.

The Industry Day described a commercial fixed-price IDIQ using fixed-price CLINs for defined requirements and fixed-price level-of-effort CLINs for undefined requirements. For continuing operational scope such as platform and infrastructure operations and recurring multimedia and event support, does NASA anticipate fixed-price level-of-effort structuring or discrete fixed-price work packages? Will that structure be established at the CLIN level in the RFP or at the task order level? 2.0 Scope

NASA anticipates a hybrid approach for continuing operational scope under the PEMSS IDIQ contract. The RFP will establish both fixed-price (FP) and fixed-price level-of-effort (FP-LOE) CLINs at the contract level. For requirements that are well-defined and can be delivered as discrete work packages, NASA will utilize FP CLINs. For requirements that are ongoing, variable, or not fully defined at the outset—such as platform/infrastructure operations and recurring multimedia/event support—NASA expects to use FP-LOE CLINs, which specify labor hours and skill mix at a fixed price.

The final determination of which pricing structure applies to a given requirement will be made at the task order (work package) level. Each task order will specify whether the work is managed as a discrete FP package or as FP-LOE, based on the nature of the requirement and mission needs. This approach provides flexibility to tailor technical requirements and pricing to the specific scope of work, ensuring both cost control and operational agility.

PWS Section 5.1 describes a 60-day phase in the plan, while the Industry Day acquisition strategy chart (slide 44) describes an approximately 30-day phase preceding the base period. Which duration governs? 5.1 Phase-in

See response to question 34 above.

Will the Draft RFP provide historical or projected work package quantities, hours, or FTE counts by PWS section so offerors can realistically price FP and FP LOE CLINs? 4.0 Technical Requirements

No, the Government will provide the estimated WYE count at the Labor Category Description level as part of the Draft Request For Proposal. However, because this is a new requirement, detailed historical staffing levels, labor category mix, incumbent workforce data, and workload volumetrics from the predecessor contracts are not fully applicable and therefore will not be available.

Will teaming with similarly situated entities be recognized for purposes of the limitations on subcontracting under FAR 52.219-14, and will small business subcontracting participation be addressed in the evaluation criteria? Set-Aside

See response to question 15 above.

Can the Government identify which PWS functions must be performed on site versus those eligible for remote or hybrid performance, for example, the remote operations capability referenced for the MMOC at Industry Day?

4.1.12 Flight Project and Mission Operations

Information Technology Support

This work will be broken out at the Techical Directive/Work Package Level, and varies depending on work requirements and organization needing the work.

For Section 3.6.2, which software classes and projects does the Government anticipate applying automatic code generation requirements to, and will validation and verification tooling be Government-furnished or contractor-provided?

3.6.2 Automatic Generation of Software Source

Code

See response to question 22 above.

Is a Top Secret facility clearance required at the time of proposal submission or at contract award, and will the DD254 authorize subcontractor access at the appropriate levels? 3.0 Contract Management

The DRFP/RFP will contain the requirements if facility clearance is required at propsal or award.

Can the Government share the current combined contractor staffing level or annual value for the portions of PESS II and FILMSS II that will migrate into PEMSS? 2.0 Scope

The Government will provide the estimated WYE count by major functional area—including engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management—at the Labor Category Description level as part of the Draft Request For Proposal. However, because this is a new requirement, detailed historical staffing levels, labor category mix, incumbent workforce data, and workload volumetrics from the predecessor contracts are not fully applicable and therefore will not be available.

When will the reserved language for Section 3.6.5 (Use of AI during contract performance, PIC 25-03A) and Section 3.6.4 (IT Security Control) be released, and will it address contractor use of AI-assisted engineering and software development tools?

3.6.5 Use of Artificial Intelligence (AI During contract

Performance

The forthcoming language for the reserved language in Sections 3.6.5 and 3.6.4 will be added for the Draft RFP posting and will address contractor use of AI-assisted engineering and software development tools by requiring compliance with NASA's IT security, privacy, and risk assessment requirements for all AI systems used during contract performance.

Will NASA provide representative historical work-package/task-order data from the predecessor contracts, including labor categories, staffing levels or hours, period of performance, and authorized value, to support development of realistic staffing and pricing assumptions? If so, when will that information be made available? 3.2 Technical Requirements management

The Government will provide the estimated WYE count by major functional area—including engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management—at the Labor Category Description level as part of the Draft Request For Proposal. However, because this is a new requirement, detailed historical staffing levels, labor category mix, incumbent workforce data, and workload volumetrics from the predecessor contracts are not fully applicable and therefore will not be available.

49 NASA identified NAICS 541330 for PEMSS. Is NASA evaluating applicability of the Military and Aerospace Equipment and Military Weapons exception to the 541330 size standard for this acquisition?NAICS Code See response to question 3 above.

Does NASA anticipate making the set-aside determination prior to release of the Draft RFP, and will NASA communicate the determination with the Draft RFP? Set-Aside

See response to question 8 above.

Will NASA clarify, by the release of the RFP or sooner, the anticipated contractual mechanism for establishing and modifying individual work packages/task orders, including how changes in scope, skill mix, staffing level, schedule, and deliverables will be incorporated after authorization? 3.2 Technical Requirements management

Yes, NASA intends to provide clarification regarding the anticipated contractual mechanism for establishing and modifying individual work packages or task orders. This information will be detailed either in the release of the Request for Proposal (RFP) or sooner if possible. The guidance will address how changes in scope, skill mix, staffing levels, schedule, and deliverables will be managed and incorporated after authorization. NASA is committed to ensuring transparency and enabling effective contract administration for all stakeholders.

For planning purposes, can NASA provide historical information regarding the approximate number of active work packages/task orders, typical duration, frequency of modifications, and range of staffing levels under the predecessor contracts? 3.2 Technical Requirements management

The Government will provide the estimated WYE count by major functional area—including engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management—at the Labor Category Description level as part of the Draft Request For Proposal. However, because this is a new requirement, detailed historical staffing levels, labor category mix, incumbent workforce data, and workload volumetrics from the predecessor contracts are not fully applicable and therefore will not be available.

During Industry Day, NASA stated that the overall contractor workforce has historically remained relatively stable while required skills and staffing needs change over time. Does this statement refer to the combined workforce supporting PESS II and FILMSS II? If so, can NASA provide the approximate current workforce by major technical area and identify any areas where material growth or reduction is presently anticipated under PEMSS? 4.0 Technical Requirements

The Government will provide the estimated WYE count by major functional area—including engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management—at the Labor Category Description level as part of the Draft Request For Proposal. However, because this is a new requirement, detailed historical staffing levels, labor category mix, incumbent workforce data, and workload volumetrics from the predecessor contracts are not fully applicable and therefore will not be available.

Given the planned FY27 Science Directorate realignment discussed during Industry Day, does NASA anticipate changes to the draft PWS 4.3 scope, organizational ownership, or anticipated staffing requirements before release of the Final RFP? 4.3 Science Support

While the final version of the PWS section 4.3 cannot be determined until the completion of the realignment process, NASA is closely monitoring any potential impacts from the FY27 Science Directorate realignment discussed during Industry Day. At this time, NASA does not anticipate significant changes to the draft PWS 4.3 scope, organizational ownership, or staffing requirements prior to the release of the Final RFP.

The Labor Category Descriptions attachment is titled "Project, Research, Engineering, and Science Services (PRESS)." Please confirm that this attachment applies to PEMSS and whether PRESS is a prior or alternate name for the requirement. Labor Category Excel Spreadsheet

PRESS was the prior name for this requirement, and the attachment has not yet been updated accordingly. The updated title will reflect this change when the DRFP is posted. Please note that the Labor Category Descriptions attachment will be revised to align with the current title of PEMSS.

Could you please confirm whether PEMSS is considered a consolidation of portions of the existing PESS II and FILMSS II requirements, or a new requirement that incorporates selected existing work? Set-Aside

See response to question 1 above.

The Acquisition Strategy identified at Industry Day stated that PEMSS is anticipated to be a total Small Business Set-Aside, awarded under NAICS code 541330 with a $25.5M size standard. This is significantly lower than the annual value of the consolidated contracts (in 2025, FILMSS 2 was valued at $29.5M and PESS 2 was valued at $24.7M) and limits NASA’s competitive pool to companies who are unlikely to have sufficient experience to perform the work. How was this NAICS code and size standard chosen prior to the receipt of sources sought responses? Set-Aside

See response to question 3 above.

NASA engineering and science services contracts are experiencing significant changes as the Agency undergoes strategic insourcing.

Will the Government please share the anticipated magnitude of PEMSS based on the current plan? If possible, please identify areas that were historically staffed by contractors that will not be under PEMSS. This is critical to industry making pursuit and teaming decisions prior to the DRFP. Full

The Government will provide the estimated WYE count by major functional area—including engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management—at the Labor Category Description level as part of the Draft Request For Proposal. Given the dynamic nature of NASA’s evolving technology landscape, any of these areas may grow or shrink over the course of the contract based on circumstances, budget, or agency direction. As a result, the ratio established at the beginning of the contract may not necessarily remain constant throughout the period of performance.

Both predecessor requirements being consolidated into PEMSS (PESS 2 and FILMSS 2) were competed under NAICS 541715, and the draft PEMSS PWS continues to emphasize engineering and technology development, scientific research, technology maturation, and support to evolving NASA R&D missions. What has changed in the principal purpose of the requirement that supports changing the NAICS classification from 541715 to 541330? NAICS Code

See response to question 3 above.

What specific aspects of the PEMSS scope led NASA to conclude that NAICS 541330 better represents the principal purpose of the acquisition than NAICS 541715, particularly given the substantial science, research, technology-development, experimentation, design, test, and mission-development work described in the PWS? NAICS Code

See response to question 3 above.

61 What is the estimated total contract value (TCV) contract ceiling? Full The maximum IDIQ value will be provided with the Draft RFP.

Does PEMSS include any scope that was not formerly part of PESS II or FILMSS II, such as ATOM, ISRDS, AFSS, or other Ames contracts? Full

Yes, the scope of PEMSS is not strictly limited to what was covered under PESS II or FILMSS 2 and may integrate additional requirements from other sources.

What is the estimated WYE count by major functional area: engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management? Full

The estimated WYE count by major functional area—including engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management—will be provided at the Labor Category Description level in the Draft Request For Proposal posting. As this is a new requirement, information regarding the incumbent contractor is not fully applicable.

Will animal care, veterinary support, IACUC administration, or biospecimen archive functions require specific certifications, licenses, or prior Ames experience? 4.3 Science Support

Yes, support of these functions will involve meeting all regulatory and animal care & use requirements as currently implemented at Ames facilites.

65 How many personnel are estimated to require Secret, Top Secret, or TS/SCI clearances? Full Variable based on work package requirements.

Since PEMSS will incorporate portions of the existing PESS II and FILMSS II work, would it be fair to view the new requirement as generally continuing similar support under a new contract structure, rather than a significant change in the underlying need? Full

See response to question 1 above.

Given the existing support and the planned transition into PEMSS, is it reasonable to assume that funding is in place for the time being, or are there any funding considerations we should be aware of that could affect the current acquisition timeline? Full

At this time, funding has been secured for this government requirement and is compliant with the Anti-Deficiency Act. The NASA Office of Procurement has confirmed that all funding practices are in accordance with the Federal Acquisition Regulation (FAR). Therefore, it is reasonable to assume that funding is in place for the current phase; no additional funding concerns are anticipated that would impact the acquisition timeline during the planned transition into PEMSS.

One last quick clarification on the Industry Day materials. We noted the programs/organizations listed as being supported by PEMSS, including Engineering, Programs and Projects, Aeronautics, Science, Exploration Technology, Safety and Mission Assurance, and Center Operations. Can you confirm that these are the correct program areas/directorates we should associate with the PEMSS requirement? Full

Yes.

NASA has identified NAICS 541330, Engineering Services, for the contemplated follow-on requirement. Given that the new requirement will encompass work currently performed under both PESS II and FILMSS II, and both predecessor contracts were competed under NAICS 541715, would NASA consider retaining NAICS 541715 for the follow-on acquisition? NAICS Code

See response to question 3 above.

Will the Government require each offeror proposing as a joint venture to submit with its proposal the fully executed joint venture agreement, the SBA-approved mentor-protege agreement, the SBA approval date, and the expiration date of that mentor-protege agreement? Will offerors be required to certify that the agreement will remain in effect through the date of award? Set-Aside

Yes, the Government will require each offeror proposing as a joint venture to submit, with its proposal, the fully executed joint venture agreement, the SBA-approved mentor-protege agreement, the SBA approval date, and the expiration date of that mentor-protege agreement. Additionally, offerors will be required to certify that the agreement will remain in effect through the date of award.

How will the Government evaluate and verify compliance with 13 CFR 125.8(c), which requires the small business partner to perform at least 40% of the work performed by the joint venture and requires work performed by the mentor's affiliates and subcontractors at any tier to be counted toward the mentor's share? Will offerors be required to submit a workshare exhibit identifying, at the labor category level, the entity that will employ the personnel performing each category? Set-Aside

The Government will evaluate and verify compliance with 13 CFR 125.8(c) by reviewing the proposed work distribution within the joint venture. Specifically, the evaluation will focus on ensuring that the small business partner is responsible for performing at least 40% of the total work performed by the joint venture, as required by the regulation. For an SBA Mentor-Protégé JV, SBA approves the Mentor-Protégé Agreement (MPA), not the resulting individual JV agreement. To obtain the M/P exception from affiliation, SBA must approve the MPA before the mentor and protégé submit an offer as a JV. See 13 CFR §125.9(d)(1)(i). The resulting JV must satisfy the applicable SBA JV requirements in 13 CFR §§121.103(h) and 125.8. The FAR 19.201-1(b)(1) provides that a JV may qualify as a small business if it complies with 13 CFR §121.103(h) and §125.8(a) and (b). The offeror must also represent its size in writing at the time of initial offer under FAR 19.201-1(c).

Will the Government make available to all offerors the historical staffing levels, labor category mix, incumbent workforce data, and workload volumetrics for both predecessor contracts, so that non-incumbent offerors can price and staff the requirement on an equal informational basis? Full

The Government will provide the estimated WYE count by major functional area—including engineering, manufacturing/fabrication, science/lab support, mission operations IT, project support, and contract management—at the Labor Category Description level as part of the Draft Request For Proposal. However, because this is a new requirement, detailed historical staffing levels, labor category mix, incumbent workforce data, and workload volumetrics from the predecessor contracts are not fully applicable and therefore will not be available.

Can you please confirm if that will be all that is allowed or if it will also include the exception: except for $47.0 million annual receipts for Military and Aerospace Equipment and Military Weapons and Contracts and Subcontracts for Engineering Services Awarded Under the National Energy Policy of 1992 and Marine Engineering Services. NAICS Code

See response to question 3 above.