2026 02 27__Amendment 00002 80MSFC26R0002 Sections J-M.docx
DOCX document 13 MB Posted
- Solicitation number
- 80MSFC26R0002
About this file
This file is Amendment 00002 to the ESSCA II Final RFP (Sections J-M) for solicitation 80MSFC26R0002 issued by NASA's Marshall Space Flight Center. The amendment updates Attachment L-1 (the Excel Pricing Model) and extends the proposal submission deadline to Monday, March 16, 2026, at 2:00 p.m. Central Time. The document also provides an ESSCA II RFP to Amendment 00001 Clause and Provision Change Matrix to assist potential offerors in understanding Federal Acquisition Regulation (FAR) and NASA FAR Supplement (NFS) clause and provision updates resulting from the Revolutionary FAR Overhaul (RFO) and associated Procurement Class Deviations (PCD). This matrix is provided for informational purposes only and does not constitute official Agency guidance; the final ESSCA II RFP with all amendments takes precedence. Offerors are responsible for downloading the complete amended solicitation and must acknowledge receipt of all amendments as part of their proposal submission. Continued monitoring of sam.gov for any future amendments is required.
The underlying ESSCA II solicitation is a hybrid indefinite-delivery, indefinite-quantity (IDIQ) contract for engineering and science capability skills augmentation support and related services to NASA MSFC, Michoud Assembly Facility (MAF), and Stennis Space Center, with limited support capabilities for NASA Headquarters and other NASA Centers. The NAICS code is 541715 (Research and Development in Physical, Engineering, and Life Sciences), with a small business size standard of 1,300 employees. The contract will include a four-month phase-in period, a five-year base ordering period, and an option for a three-year additional ordering period. Orders may be issued as cost-plus-award-fee (CPAF), cost-plus-fixed-fee (CPFF), or firm-fixed-price (FFP). This is a full and open competition.
View the file
Other files
Show all 27
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
80MSFC26R0002 Section M
Please refer to ESSCA II RFP 80MSFC26R0002 Sections A-I.pdf to see the solicitation cover page and Sections A through I.
PART III – List of Documents, Exhibits, and Other Attachments
SECTION J
LIST OF ATTACHMENTS
| Attachment |
| Title |
| J-l |
| Performance Work Statement |
| J-2 |
| Data Procurement Document |
| J-3 |
| Performance Requirements Summary |
| J-4 |
| Draft Award Fee Evaluation Plan |
| J-5 |
| Small Business Engagement Plan |
| J-6 |
| Small Business Subcontracting Plan |
| J-7 |
| Rates Schedule and Labor Categories |
| J-8 |
| Automated Tools for Order Management Simplification (ATOMS) Suite of Tools Requirements and Processes |
| J-9 |
| Contract Work Breakdown Structure (CWBS) |
| J-10 |
| On-Site Safety, Health, and Environmental (SHE) Plan |
| J-11 |
| Off-site Safety, Health and Environmental Plan |
| J-12 |
| Installation-Provided Property and Services |
| J-12-A |
| Installation-Accountable Government Property (IAGP) List |
| J-13 |
| List of Government-Furnished Property |
| J-14 |
| Government Property Management Plan |
| J-15 |
| Organizational Conflict of Interest (OCI) Plan |
| J-16 |
| Wage Determinations |
| J-17 |
| IDIQ Task Order Listing |
| J-18 |
| Acronym List |
| J-19 |
| Pursuits Culture and Partnering Plan |
| J-20 |
| DD254, Department of Defense Contract Security Classification Specification |
| J-21 |
| Task Order and Delivery Order Content Requirements |
| J-22 |
| Management Plan |
| J-23 |
| Contractor Personnel Certification Plan |
| J-24 |
| Mandatory and Required Training |
| J-25 |
| Information System Security Plan |
80MSFC26R0002 Section J
J-2
NATIONAL AERONAUTICS AND SPACE ADMINISTRATION (NASA) ENGINEERING SERVICES AND SCIENCE CAPABILITY AUGMENTATION (ESSCA) II
ATTACHMENT J-1
PERFORMANCE WORK STATEMENT
1.0 SCOPE
This Performance Work Statement (PWS) broadly defines the requirements for Engineering Services and Science Capability Augmentation (ESSCA) II provided to the Marshall Space Flight Center (MSFC) in Huntsville, Alabama; the Stennis Space Center (SSC) in Hancock County, Mississippi; and the Michoud Assembly Facility (MAF) in New Orleans, Louisiana, which is managed by MSFC. Throughout the entirety of the contract, all references to MSFC are inclusive of MAF. In addition, this contract may support NASA Centers including Armstrong Flight Research Center (AFRC), Ames Research Center (ARC), Glenn Research Center (GRC), Goddard Space Flight Center (GSFC), National Aeronautics and Space Administration (NASA) Headquarters (HQ), Johnson Space Center (JSC), Kennedy Space Center (KSC), and Langley Research Center (LaRC).
The ESSCA II requirement is a follow-on to the ESSCA contract. Services and skills are to be provided across a broad spectrum of engineering and science disciplines and requested support will include, but not be limited to, research, design, development, analysis, testing, operations, and sustaining engineering.
The ESSCA II contract will provide engineers, scientists, and engineering technicians in support of MSFC and other Centers, as well as programs, projects, and other activities across the Agency, both present and future. The contract also provides scope for end-item deliverables. The contract includes support for facilitating partnerships and identifying new pursuits and opportunities that align with MSFC strategy. ESSCA II will also support reimbursable work for which MSFC, and other Centers, are responsible. This work can include support to the Department of Defense (DoD), other Government agencies, commercial industry, and academia.
The Contractor’s work is controlled by means of Task Orders (TOs) for skills augmentation support and Delivery Orders (DOs) for end-item deliverable requirements. The TOs range from general technical support within an organization, to specific tasks including, but not limited to, supporting flight hardware design reviews and leading independent review teams. The dynamic nature of the work required by this PWS demands significant flexibility in the allocation of engineering, science, and technical resources. DOs can vary widely from ready-to-use systems to end-item deliverables that include, but are not limited to: software, trade studies, support equipment, prototypes, flight hardware, electronic systems, mockups, test articles, training hardware, laboratory test equipment, tooling, manufacturing demonstration articles, and research instruments. The specific requirements for each end-item deliverable will be documented in a DO.
The sharing of technical resources across Center organizations is strongly encouraged. The Government will be responsible for ensuring work completed under each TO and DO is satisfactory. In most cases, the Contractor is expected to complete requested work with minimal guidance from the Government.
2.0 CONTRACT MANAGEMENT OPERATIONS AND CONTROL
2.1. Management
The Contractor must:
2.1.1. Provide all necessary management, data requirement descriptions (DRDs) (as required by Attachment J-2, Data Procurement Document [DPD]), and equipment and supplies, not otherwise provided by the Government, required to perform the engineering and science services and end-item deliverable support as defined in this PWS.
2.1.2. Account for costs associated with contract management operations (CMO) (e.g., program management, Automated Tools for Order Management Simplification (ATOMS) Suite of Tools, office space, accounting, and human resources) as indirect charges in accordance with the Contractor’s accounting approach and Cost Accounting Standards Board (CASB).
2.1.3. Provide all necessary personnel, training, travel, and materials as specifically described in TOs and DOs.
2.1.4. Comply with NASA, MSFC or other Center, as applicable, regulations, policies, clauses, directives, procedures, and standards when performing all work under this PWS. Other Centers will include Center specific regulations, policies, clauses, etc., as applicable, when requesting TO support under this contract.
2.1.5. Maintain a facility clearance through the life of the contract. The Government will complete the DD254 Form, Department of Defense Contract Security Classification Specification, and provide it to the Contractor in the limited cases where access to classified information is required.
2.1.6. Provide the planning, coordination, leadership, supervision, and surveillance of all activities necessary to assure disciplined performance of work and timely application of resources for the accomplishment of TOs and DOs issued under the contract.
2.1.7. Maintain communication with the Government initiator and alert the contracting officer’s representative (COR) and CO of any problems that would prevent meeting TO and DO requirements.
2.1.8. Report and document this work and fulfill the requirements of associated Data Requirement Descriptions (DRDs) as outlined in Attachment J-2, Data Procurement Document (DPD).
2.1.9. Integrate risk management into the overall performance of contract requirements.
2.1.10. Develop, submit, implement, and maintain a small business subcontracting plan in accordance with FAR 52.219-9, Small Business Subcontracting Plan, to provide small business concerns the maximum practical opportunity to receive a portion of subcontract awards.
2.1.11. Develop, submit, implement, and maintain a Small Business Engagement Plan in accordance with DRD 1839MA-005.
2.1.12. Prepare and submit a Re-Procurement Incumbent Compensation Data Package in accordance with DRD 1839MA-004.
2.1.13. Deliver all limited rights data (as defined in FAR 52.227-14) expected to be used in the performance of this contract within 30 days of award. For purposes of this contract, the term "developed" means that an item, component, or process exists and is workable. Thus, the item or component must have been constructed or the process practiced. Workability is generally established when the item, component, or process has been analyzed or tested sufficiently to demonstrate to reasonable people skilled in the applicable art that there is a high probability that it will operate as intended. Whether, how much, and what type of analysis or testing is required to establish workability depends on the nature of the item, component, or process, and the state of the art. To be considered “developed,” the item, component, or process need not be at the stage where it could be offered for sale or sold on the commercial market, nor must the item, component, or process be actually reduced to practice within the meaning of Title 35 of the United States Code.
2.2. Planning and Control
The Contractor must:
2.2.1. Establish, implement, and maintain technical competence and oversight of all work performed under this PWS.
2.2.2. Assure the technical excellence, cost control, and timeliness of all required work. Due to the dynamic nature of the work required by this PWS, significant flexibility in the allocation of engineering, science, and technical resources is required and sharing technical resources across Center organizations is strongly encouraged.
2.2.3. Provide necessary Human Resources (HR) functions such as recruiting, hiring, compensation administration, management of attrition, succession planning, resolution of performance and conduct issues, and other HR activities, required to provide a highly qualified workforce to perform the requirements of the TOs and DOs.
2.2.4. Be ultimately responsible for resolution of HR issues for all personnel working under the ESSCA II contract, including associated teammates and subcontractors.
2.2.5. Provide the overall management effort required to integrate technical and programmatic functions necessary to achieve the requirements of the contract. The Contractor must prepare, submit, implement, and maintain a Management Plan in accordance with DRD 1839MA-001.
2.2.6. Fully integrate all related plans and activities, including those of subcontractors.
2.2.7. Prepare, submit, implement, and maintain an Organizational Conflict of Interest (OCI) Plan in accordance with DRD 1839MA-003.
2.2.8. Prepare, submit, implement, and maintain a Government Property Management Plan in accordance with DRD 1839LS-001.
2.2.9. Prepare, submit, implement, and maintain an On-site Safety, Health, and Environmental (SHE) Plan in accordance with DRD 1839SA-001.
2.2.10. Prepare and submit mishaps and safety statistics to the MSFC Industrial Safety Branch in accordance with the Onsite Mishap Reporting and Safety Statistics Reports, DRD 1839SA-003.
2.2.11. Prepare, submit, implement, and maintain a Contractor Personnel Certification Plan in accordance with DRD 1839SA-002.
2.2.12. Prepare and submit technical information concerning any invention, discovery, improvement, or innovation made by the Contractor in the performance of work under this contract in accordance with DRD 1839CD-003, Technology Reports.
2.2.13. Prepare and submit a Weekly Contract Status Briefing in accordance with DRD 1839MA-008.
2.2.14. Prepare, submit, implement, and maintain a plan to promote partnerships between MSFC and industry, academia, and other Government agencies in accordance with DRD 1839MA-009. These partnerships should align with MSFC pursuits culture and utilize available personnel across the skill areas listed in this PWS.
2.2.15. Prepare, submit, implement, and maintain IT Security capabilities in accordance with NFS 1852.240-76, NPR 2810.1, Security of Information and Information Systems, that is consistent with NASA IT security plan and requirements in accordance with DRD 1839CD-001, Security Requirements for Unclassified IT Resources.
2.2.15.1. External IT systems that interface with NASA systems must have separate control plans and require an Authorization to Operate, from a designated Government Authorizing Official in the NASA Risk Information Security Compliance System (RISCS) prior to accessing NASA systems.
2.2.16. Assist in planning and defining support for new collaborations, programs, and projects.
2.2.17. Prepare and submit report of purchases authorized through the Office of the Chief Information Officer (OCIO) Commercial IT Request (CITR) Application, in accordance with the Commercial IT Authorization Report, DRD 1839CD-004.
2.2.18. Prepare and submit report of all IT expenditures consistent with the Agency’s guidelines and policies regarding the management and reporting of IT resources, in accordance with the Information Technology (IT) Capital Planning and Investment Control (CPIC), DRD 1839CD-005.
2.2.19. Prepare, submit, implement, and maintain an Off-site Safety, Health, and Environmental (SHE) Plan in accordance with DRD 1839SA-004.
2.2.20. Prepare and submit a Commercial Artificial Intelligence (AI) Risk and Impact Assessment (CAIRIA) in accordance with DRD 1839CD-006.
2.3. Facilities
The general expectation is that work ordered through TOs will be performed at MSFC, or other Center provided facilities, following the onsite work guidelines of each Center, and in other locations as approved in writing by the CO. The general expectation is that work ordered through DOs will be performed off-site. Telework may be allowed as specified in individual TOs and DOs. Government-provided property and services, as summarized in NFS 1852.245-71, Installation-Accountable Government Property, and Attachment J-12, Installation-Provided Property and Services, and specifically defined in TOs and DOs, may be made available to all on-site personnel to perform this contract.
2.3.1. CMO personnel who are charged as an indirect cost and are not located at on-site facilities under a TO or DO must be located at an off-site Contractor facility, except for safety staff, property management staff and receiving staff, as noted below. MSFC will provide NASA computers to Contractor personnel located off-site supporting CMO to facilitate enhanced communication and data sharing with both the Government and the Contractor’s on-site workforce.
2.3.2. The Contractor’s safety staff, consisting of at least two safety professionals, must be located on-site at MSFC to support daily safety-related activities.
2.3.3. The Contractor must prepare and submit both an on-site and off-site employee location listing for all Contractor and subcontractor personnel supporting MSFC, and other Centers as applicable, in accordance with DRD 1839CD-002, On-site/Off-site Employee Location Listing.
2.3.4. Contractor use of Government Furnished Information Technology resources must comply with NPD 2540.1, Acceptable Use of Government Furnished Information Technology Equipment, Services and Resources.
2.3.5. Contractor may have property management staff and receiving staff onsite to support operations.
2.4. ATOMS Suite
The Contractor must:
2.4.1. Make available for use, maintain, and operate an ESSCA II ATOMS Suite consisting of one or more software-based tools used to implement the functionality defined in Attachment J-8, Automated Tools For Order Management Simplification (ATOMS) Suite Of Tools Requirements And Processes.
Attachment J-8 defines the requirements and rationale for the following tools:
(1) The ATOMS Preparation Tool (APT) used by the Government to develop and revise Task Order Requests (TORs), Task Order Change Requests (TOCR), Delivery Order Requests (DORs) and Delivery Order Change Requests (DOCRs);
(2) The ATOMS Routing Tool, used to automate the routing, review, and approval of the Government TORs, TOCRs, DORs, DOCRs, and the Contractor's corresponding Task Order Plans (TOPs), Task Order Change Plans (TOCPs), Delivery Order Plans (DOPs) and Delivery Order Change Plans (DOCPs);
(3) The ATOMS Funding Tool (AFT) used to track funding at the subtask level by Procurement Request Line Item (PLI) and Accounting Line Item (ALI) applied to the contract;
(4) The ATOMS ESSCA II Document Library (AEDL) used to store DRDs delivered in accordance with Attachment J-2 as well as other contract-related documents and templates created by the Contractor or the Government; and,
(5) The ATOMS Suite reporting capabilities generate reports that are transient and utilize data as of the time generated. There is no versioning or maintenance of prior reporting runs, although a report may draw data from older sources.
2.4.2. The APT and ART must be operational no more than 30 calendar days after start of phase-in.
2.4.3. The AFT must be operational no later than the first day of the contract base ordering period.
2.4.4. The AEDL must be operational at the start of phase-in.
2.4.5. The ATOMS Suite Reporting capability must be operational no more than 30 calendar days after start of contract base ordering period.
2.4.6. Include costs for operating, maintaining, and responding to Government enhancement requests of the ATOMS Suite as part of CMO burdens applied to the fully burdened labor rates in Attachment J-7, Schedule of Rates and Description of Labor Categories.
2.4.7. Implement the ATOMS Suite as a Web-based application(s).
2.4.8. Backup the ATOMS Suite, including all associated data, at least weekly.
2.4.9. Be responsible for providing the security necessary to protect the Contractor data within ATOMS Suite, including backups. Implement resolutions for Government identified security vulnerabilities within 24 hours.
2.4.10. Host the ATOMS Suite off-site and ensure accessibility for remote access.
2.4.11. Address the ATOMS Suite as part of the IT Security Planning in accordance with PWS Section 2.2.18.
2.4.12. Route TOPs, TOCPs, DOPs, and DOCPs to the Government within the ATOMS Suite, in accordance with Attachment J-8.
2.4.13. Release the TO or DO within the ATOMS Suite upon acceptance in accordance with the Task Ordering clause NFS 1852.216-80, Task Ordering Procedure.
2.4.14. Provide an online user’s guide for the ATOMS Suite. The user’s guide should be organized into sections for different types of users.
2.4.15. Provide ATOMS Suite customer support from 8:00 a.m., to 4:00 p.m., Central Time, during a normal Government workday.
2.4.16. Provide ATOMS Suite responses to individual requests for customer support no later than one (1) business day after the request.
2.4.17. Provide solutions to ATOMS Suite customer support requests and problem reports to minimize impact to Government operations.
2.4.18. Provide initial and on-going training for users on a scheduled and an as-needed basis.
2.4.19. Perform continuous assessment and improvement of ATOMS Suite operations and architecture to ensure efficiency and performance, including a minimum of 0.5 WYE/year of support for Government identified or requested enhancements and customizations.
2.4.20. Notify users of ATOMS Suite status during both scheduled and un-scheduled maintenance.
2.4.21. Perform any planned preventative maintenance and upgrades from 5:00 p.m. to 7:00 a.m., Central Time, daily.
2.4.22. Notify the Government of modifications prior to implementation.
2.4.23. Notify the Government users of scheduled maintenance at least 24 hours prior to implementation.
2.4.24. Restore operation of the ATOMS Suite within four (4) hours for un-scheduled maintenance.
2.4.25. Document the ATOMS build architecture to include a top-level functionality description of the major components (e.g. APT, ART, etc.), interfaces between components, and user interfaces, along with identification and description of whether each is Proprietary, Commercial, Limited Rights, or Unlimited rights. The document must be maintained.
2.4.26. Reserved.
2.4.27. Maintain the data within the ATOMS Suite as Government records, in accordance with MPR 1440.2, MSFC Records Management Program, and digitally transfer these records to the Government at contract completion. The COR may request interim copies of data from the ATOMS Suite during the contract, but these copies do not replace the ATOMS Suite as the official location of the records.
2.5. Order Management
The Contractor must:
2.5.1. Respond to TORs, TOCRs, DORs, and DOCRs submitted by the Government through the ATOMS Suite in accordance with the timelines in NFS 1852.216-80, Task Ordering Procedure.
2.5.2. Submit TOPs, TOCPs, DOPs, and DOCPs to the Government through the ATOMS Suite in accordance with the content defined in NFS 1852.216-80, Task Ordering Procedure, and the formats defined in Attachment J-21, Task Order and Delivery Order Content Requirements.
2.5.3. Submit and release TOPs to Technical Direction provided by the COR (see Section 2.10) submitted through the ATOMS Suite in accordance with PWS Section 2.4.
2.5.4. Release Task Orders through the ATOMS Suite in accordance with the timelines in NFS 1852.216-80, Task Ordering Procedure.
2.5.5. Prepare and submit Task Order Activity Reports in accordance with DRD 1839MA-006.
2.6. Financial Management
The Contractor must:
2.6.1. Prepare and submit a Financial Management Report, 533M, including required supplemental information, in accordance with DRD 1839MA-007.
2.6.2. Track the amount of funding assigned to each subtask, based upon amounts defined in contract funding mods, with Funding PRs, adjusted by the Contractor for actual costs reported on the 533M, and funding transfers by the Government through the ATOMS Suite.
2.6.3. Cost the Government’s money by oldest money first, then first in/first out (FIFO).
(a) Funding will be identified by the Fund Code as supplied by the Government. The Fund Code is a 10-digit alpha numeric that identifies the fiscal year (FY) the funds were appropriated (e.g., EXPX22016D).
(b) FIFO methodology uses several sequential numbers provided by the Government.
(c) The Purchase Requisition (PR) number is a sequentially assigned number from the Government accounting system Systems, Applications and Products (SAP) (e.g., 4200578392). The Contractor must apply cost using the lowest numerical sequence after identifying the oldest money based on the Fund Code.
(d) The PLI is a sequentially assigned number from the Government accounting system SAP (e.g., 1, 2, 3). The Contractor must apply cost by using the lowest numerical sequence after identifying the oldest money first and then the PR number.
(e) The ALI is a sequentially assigned number from the Government accounting system SAP (e.g., 1, 2, 3). The Contractor must apply cost by using the lowest numerical sequence after identifying the oldest money first, PR number second, followed by the PLI. The ALI will be the last identifier used in the management of cost on the contract unless otherwise identified.
2.6.4. Maintain consistency between the Contractor's financial accounting system, the 533M and 533M supplemental reports, and the ATOMS Suite.
2.6.5. Submit initial 533M, including required supplemental information, concurrently with first invoice.
2.7. Contractor Procurements
The Contractor must:
2.7.1. Procure only materials, supplies and equipment necessary for the accomplishment of this PWS, with the exception of property furnished or made available for use under the contract, TOs, and DOs.
2.7.2. Ensure the total acquisition cost of a procurement does not exceed $150,000 unless approved by the CO.
2.7.3. Make no purchases for items over the capitalization threshold as defined in NPR 9250.1, Property, Plant, and Equipment (PPE) and Operating Materials and Supplies, until provided an approved form NF1739 by the Government.
2.7.4. Not purchase the information technology (IT) products specified as Desktop Services and Software in Attachment J-12, Installation-Provided Property and Services.
2.7.5. Purchase quality sensitive items as defined in MPR 8730.1, Inspection and Testing, only as necessary to fulfill DO requirements. Quality assurance requirements for these purchases will be provided in the DO.
2.7.6. Obtain COR and CO concurrence prior to purchasing any item intended for immediate transfer to the Government and not maintained as Contractor property.
2.8. Technology, Innovations, and Process Improvements
The Contractor must:
2.8.1. Identify and promote technology, innovations, and process improvements that improve engineering and science products, processes, capabilities, tools, and operations.
2.8.2. Consult with Engineering Directorate management to assure that technology improvements are aligned with focused areas for technology development and MSFC’s pursuits culture.
2.8.3. Prepare, submit, implement, and maintain a Technology, Innovations, and Process Improvement Plan (TIPI) in accordance with DRD 1839MA-002.
2.8.4. Report any significant accomplishments of technology, innovation, and process improvement activities.
2.8.5. Provide reporting in accordance with DRD 1839MA-008, Weekly Contract Status Briefing.
2.9. Phase-In and Phase-Out
The Contractor must:
2.9.1. Perform Phase-In and Close-out/Phase-out contract activities.
2.9.2. Perform phase-in activities for a period not to exceed four (4) months to assume full responsibility for this contract by the start of the base period.
2.9.3. During Phase-In, the Contractor must:
2.9.3.1. Accomplish all tasks required to complete phase-in activities, to include, but not limited to, managing an orderly transition, hiring personnel, obtaining personnel badges and clearances, training personnel, and scheduling performance of work necessary to ensure the effective transfer of effort from the predecessor contractor.
2.9.3.2. Provide all data deliverables due during the phase-in period as specified in Attachment J-2, Data Procurement Document, and obtain any necessary approvals.
2.9.3.3. Participate in meetings with the predecessor contractor and the Government to identify and discuss problems or areas requiring attention during the phase-in period.
2.9.3.4. Receive and store legacy data from contracts phasing into the pending contract effort.
2.9.3.5. Receive property being transferred to the pending contract effort.
2.9.3.6. Receive assignment of any existing purchase orders that will continue beyond the phase-in period.
2.9.3.7. Actively cooperate with the Government in completing any systems/compliance reviews that may be required, including expedient implementation of any necessary corrective actions.
2.9.3.8. Ensure implementation of any requirements agreed to during discussions that are required by the effective date of the contract.
2.9.3.9. Routinely meet with the CO and COR to status transition activities and ensure integration of Government activities performed to support phase-in (e.g. development of TORs, badging requests, transition of property.)
2.9.3.10. Submit a single invoice to the Government at the conclusion of phase-in activities in the amount established for the value of CLIN 0001.
2.9.4. Phase-out is conducted during the final year of the Contract, in parallel with TO, DO, and other routine contract performance. During Phase-Out the Contractor must:
2.9.4.1. Prepare for transition of all activities to the successor Contractor to minimize operational impacts.
2.9.4.2. Cooperate with the successor contractor to facilitate the effective phase-in of the follow-on effort.
2.9.4.3. Disclose necessary personnel records and allow the successor to conduct on-site interviews with these employees. If selected employees are agreeable to the change, release them at a mutually agreeable date and negotiate transfer of their earned fringe benefits to the successor.
2.9.4.4. Participate in meetings with the successor contractor and the Government to identify and discuss problems or areas requiring attention during the phase-in period.
2.9.4.5. Transfer legacy data to the Government and successor contractor.
2.9.4.6. Identify and transfer property to the successor contractor.
2.9.4.7. Assign existing purchase orders (e.g., software licenses) phasing into the successor contract effort that will continue beyond the phase-in period and that are necessary for performance of the successor contract.
2.9.4.8. Notify the Government of existing purchase orders that will be assigned to the successor contract so those costs can be removed from the predecessor contract and applied to the successor contract.
2.10. Technical Direction
The COR is authorized to provide technical direction for the work under ESSCA II. Technical direction encompasses written direction from the COR to provide 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 PWS. The COR does not have authority to issue instruction that constitutes any of the following:
| • | Assignment of additional work outside the PWS; |
| • | A change as defined in Changes clauses incorporated in this contract; |
| • | A basis for any increase or decrease in the total estimated contract cost, the award fee, or the time required for contract performance; |
| • | Changes in any of the expressed terms, conditions, or specifications of the contract; or |
| • | Instruction that interferes with the Contractor’s rights to perform the terms and conditions of the contract. |
The Contractor must proceed promptly with the performance of technical direction duly issued by the COR in the manner prescribed by this section and within the COR's authority. If, in the Contractor's opinion, any instruction or direction by the COR falls outside of the COR’s authority, the Contractor must not proceed but must notify the CO in writing within four (4) days after receiving it and must request the CO to take action as described in this section. Upon receiving this notification, the CO will either issue an appropriate TO/DO change or contract modification within a reasonable time or advise the Contractor in writing within seven (7) days that the instruction or direction is rescinded in its entirety; or the direction is within the requirements of the contract and does not constitute a change under the applicable changes clause, and that the Contractor should proceed promptly with its performance.
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 applicable Changes clause, or a failure to agree upon the contract action to be taken with respect to the instruction or direction, is subject to FAR 52.233-1, Disputes, of this contract.
Any action(s) taken by the Contractor in response to any direction given by any person other than the CO or the COR must be at the Contractor's risk.
Information Technology Purchase Authorization
2.11.1. The contractor must ensure all IT products and services direct charged to the contract are approved through the OCIO’s Commercial IT Request (CITR) Application. This includes, but is not limited to, FITARA, Supply Chain Risk Management (SCRM), IPv6, and 508 compliance. No purchases of commercial IT products or services should be made prior to coordination and approval by the OCIO.
2.11.2. This contract must only be used to purchase software, software maintenance, hardware, or hardware maintenance necessary for the performance of this contract. NASA must own the license(s) or subscriptions for any software or applications purchased.
2.11.3. All hardware must be titled to NASA.
Section 508 Compliance
2.11.4. The contractor must ensure that all products, platforms, services, and communications delivered as part of this work statement that are Information and Communication Technology (ICT) or contain ICT, conform to the Revised Section 508 of the Rehabilitation Act Standards, 36 C.F.R. § 1194.1 & Apps. A, C & D.
2.11.5. Standards may be found at https://www.access-board.gov/ict/.
Records Management
2.11.6. The Contractor must maintain all records created for Government use or created in the course of performing the contract and/or delivered to, or under the legal control of the Government and must be managed in accordance with Federal law, including but not limited to, the Federal Records Act (44 U.S.C. chs. 21, 29, 31, 33), NARA regulations at 36 CFR Chapter XII Subchapter B, as well as NASA records policies (NPD 1440.6, NASA Records Management Program, and NPR 1441.1, NASA Records Management Program Requirements).
2.11.7. The Contractor must ensure that NASA-owned/Contractor-held records are segregated from contractor-owned records and from non-record materials and report holdings of NASA records.
2.11.8. The Contractor must immediately notify the Contracting Officer (CO) and NASA Records Officer upon discovery of any inadvertent or unauthorized removal, defacing, alteration, or destruction of Federal records. Destruction of Federal Records is EXPRESSLY PROHIBITED unless in accordance with records retention schedules or as directed by the CO.
2.11.9. All Contractor employees assigned to this contract who create, work with, or otherwise handle Federal Records are required to complete mandatory NASA-provided records management training. The Contractor must ensure that training has been completed according to agency policies, including initial training and any required annual or refresher training.
2.11.10. The Contractor must incorporate the substance of this clause, its terms and requirements including this paragraph, in all subcontracts under this contract, and require written subcontractor acknowledgment of same.
Use of Artificial Intelligence (AI) During Contract Performance
2.11.11. The Contractor must disclose any potential or intended use of Artificial Intelligence (AI) technologies, tools, or systems in the performance of this contract. If it is unknown at the time of contract award whether AI will be used, the Contractor must provide written notice to the Government prior to the deployment of any AI systems during contract performance. If AI technologies are introduced after the commencement of contract performance, the Contractor must notify the CO in writing prior to the release or deployment of any AI component, capability, or system in the NASA environment.
2.11.12. The Government reserves the right to review, approve, or disapprove the proposed use of AI technology in the performance of this contract. The Contractor must obtain written approval from the contracting office or CO before implementing AI systems.
2.11.13. If any subcontractor intends to use AI technologies in the performance of work under this contract, the Contractor must ensure that similar notification and disclosure requirements apply to all subcontractors. The Contractor is responsible for collecting the notification and disclosure requirements from subcontractors and submitting them to the Government.
3.0 CONTRACT SKILL CATEGORIES
The Contractor must provide the skills and services described in this section as required by the issuance of individual TOs. The nature of work performed will generally fall into a combination of the following categories, with the specific requirements to be defined per TO:
| • | Providing engineering product(s) for work assigned to MSFC, or other NASA centers including, but not limited to, space flight and science missions; |
| • | Providing technical oversight and/or insight support for work assigned to MSFC, or other NASA centers, including, but not limited to, space flight and science missions; |
| • | Providing engineering product(s) and technical oversight and/or insight support for research and development activities; and |
| • | Real-time support for investigations of flight and ground system anomalies, as required. |
The term engineering products is used extensively throughout the PWS. Examples of engineering products include, but are not limited to, analyses, reports, data, databases, designs, drawings, plans, procedures, software, simulations, models, requirements definition and development, diagrams, specifications, standards, and support to trade studies.
The needed services are organized into skill categories. Each skill type as described will envelope various skills that may be required to provide support for or produce engineering products per TOs issued under this contract. Inherent to the skills and capabilities described is a familiarity and expertise with a wide array of engineering design and analysis software packages (e.g., NASTRAN, MATLAB, LabView, Creo, Thermal Desktop, Ansys, MagicDraw, Fluent, NX, Mentor Graphics, LTSpice, MINIVER, RAMP, PLIMP, RMC, GRAD). The description provided below is not intended to cover all skills or engineering products required in this contract; instead, it is intended to broadly define what types of skills and engineering products may be required over the entire life of the contract. The actual skills required for this contract are dependent upon the content of the TOs, which may require a mixture of the skill sets below. Innovations in engineering and sciences may result in changes to necessary skills, within the limits of the general contract scope, during the contract period.
3.1. Aerosciences Design, Development, and Test
The Contractor must:
3.1.1 Provide skills and services related to flight mechanics; Guidance, Navigation, and Control (GN&C); atmospheric, planetary, space and natural environments; blast modeling; debris transport analysis and impact modeling; aerothermodynamics; and aerodynamics to support the design, development, analysis, integration simulation, modeling, and testing of space systems, propulsion systems, space transportation systems, scientific research experiments, ground support equipment, and special equipment for current and future programs, projects, and other activities.
3.1.2 Deliver engineering products associated with areas of compartment venting, aero-acoustics, aerodynamic heating, aerodynamic flight control components, trajectory design, mission analysis, navigation design, separation systems analysis, blast and debris environments, orbital mechanics, guidance design, vehicle dynamics, control systems design, slosh and Pogo analysis, stability analysis, and propulsion dynamics. The Contractor must also deliver engineering products in areas such as atmospheric science, including but not limited to; influence on launch vehicles and spacecraft, influence on operations, modeling and programming, space environment characterization, space environment modeling and programming, spacecraft charging and plasma environment, meteoroid environment physics, meteoroid environment modeling and programming, meteoroid impact analysis. These products must include but not be limited to design, development, analysis, integration, analytical tool development, simulation modeling, requirements definition, trade studies, and test analysis.
3.1.3 Provide skills and services related to computational fluid dynamics analysis of aerothermodynamic environments and wind tunnel test planning, operations, data reduction, and evaluation.
3.1.4 Provide support for and generate engineering products associated with research and new technology development for flight mechanics, GN&C, mission analysis, atmospheric and natural environments, blast modeling, debris transport analysis, aerothermodynamics, and aerodynamics.
3.2. Avionics & Electrical Systems Design, Analysis, and Test The Contractor must:
3.2.1 Provide skills and services related to avionics and electrical systems to support the design, development, analysis, and testing of space systems, propulsion systems, space transportation systems, scientific experiments, ground support equipment, and special equipment for current and future programs, projects, and other activities.
3.2.2 Deliver engineering products associated with technical areas such as: electronic circuitry including power, analog signal, digital, and Field-Programmable Gate Array (FPGA); electrical design and integration including batteries, solar arrays, fuel cells, cable design, cable interconnect diagrams, and electrical system schematics; electrical, electronic and electromechanical parts (EEE Parts) including electrical and electronic part failure analysis, parts management, obsolescence, and radiation analysis, electromagnetic environmental effects (i.e., electromagnetic interference [EMI] and electromagnetic compatibility [EMC]) including lightning, electrostatic discharge, EMI testing, and power quality testing; radio frequency (RF) systems including communication, global positioning system (GPS) and range safety; hardware for GN&C, including both inertial and optical sensor systems and associated test facilities; audio and video electronics; imagery systems; sensors and instrumentation; sensors, wireless sensor micro-fabrication, harsh environment sensor research, structural health monitoring research; systems health management; avionics fault management; avionics emulators (real-time and non real-time); electro-optics; printed circuit board design and construction, including surface mount and through-hole component installation and emerging technologies such as printed electronics; electro-mechanical packaging design, analysis and assembly, and support development and implementation of workmanship standards; electronic test equipment and test software; and avionics and software systems integration. Example engineering products include the design, development, assembly, test, analysis, modeling and simulation of the following: development hardware, prototype hardware, flight hardware, ground hardware, payloads, subsystems, science investigations, exploration initiatives, and analytical tools.
3.2.3 Provide support for and generate engineering products associated with research and new technology development for avionics and electrical design, analysis, and test areas.
3.3. Flight Software and Ground Test Design, Analysis, and Test The Contractor must:
3.3.1 Provide skills and services to develop launch vehicle, spacecraft, and space systems’ software requirements, design, code, and test. The Contractor must perform unit-testing, integration, qualification testing and certification, and configuration control of this software. The Contractor must produce flight software for embedded systems intended to operate launch vehicles and spacecraft. The Contractor must provide skills necessary to develop in-space and ground software applications for research and technology applications. The Contractor must provide skills necessary to develop software applications for instrumentation and components associated with environmental control and life-support system instrumentation and components.
3.3.2 Provide technical skills necessary to develop requirements, design, code, and tests of ground software, including real-time simulation and modeling of launch vehicles*, simulation of space systems and subsystems, hardware-in-the-loop simulation, test automation software, and all-digital simulations. The Contractor must provide technical skills necessary to develop tools to support the development, test, analysis, and operations of software systems, including skills in cloud computing technologies to support the development and operations of these tools. The Contractor must provide technical skills related to hardware and hardware/software integration engineering and for ground test systems to support the real-time modeling and simulation design, development, integration, test, and evaluation of real-time hardware-in-the-loop facilities. The Contractor must provide services and engineering products such as: system integration of lab automation tools and displays, avionics and avionics software models; cable interconnect diagrams; cable harness drawings; grounding diagrams/analysis; avionics emulators and associated breakout boxes for both data and power; integrated engineering analysis for voltage drop and grounding systems (anchoring of model to flight data); hardware integration analysis; design integration; analytical tool development; and simulation and modeling.
* Support for real-time simulation and modeling of the SLS vehicle and subject matter expertise for real-time simulation and modeling for other vehicles will be accessed through another contract.
3.3.3 Support and maintain Capability Maturity Model Integration (CMMI) maturity level ratings of 2 and 3.
3.3.4 Provide support for and generate engineering products associated with research and new technology development for flight software and ground test systems design, analysis, and test.
3.4. Materials Research, Analysis, Testing, Processes, and Hardware Development The Contractor must:
3.4.1 Provide skills and services for and generate engineering products associated with advanced materials research and microgravity research including but not limited to:
a. Advanced Materials Research – Research into advanced materials including hybrid composites, polymeric/elastomeric materials, metallic and non-metallic structural materials, protective coatings, lubrication systems, high temperature thermal protection materials, ionic liquids, and cryogenic thermal protection materials. This also includes development of Integrated Computational Materials Engineering capabilities, techniques, and tools.
b. Reduced Gravity Research – Design, construction, and maintenance of scientific equipment that will be utilized for reduced gravity materials science experiments on Earth, the International Space Station, and future low-Earth orbit (LEO) and Lunar research stations.
3.4.2 Provide skills and services for and generate engineering products associated with multiple materials analysis disciplines, including but not limited to:
a. Analytical Chemistry – Provide chemical data relating to hardware and materials as well as the development of new capabilities, tools, and techniques.
b. Damage Tolerance Analysis – Determination of a material’s tolerance to damage, fracture, and fatigue to predict service life in the expected operational environment. The Contractor must develop damage tolerance and fracture control techniques and perform fracture control reviews for programmatic insight support and materials reviews.
c. Data Management – Management, reduction, and dissemination of analytical data that will be utilized for making engineering decisions relating to materials processing and hardware development.
d. Failure Analysis – Analysis of failed hardware, including but not limited to flight, ground support, development, and test hardware, to determine causes of the failure.
e. Materials Diagnostics – Materials diagnostics and evaluation of microstructures using microscopy and microhardness techniques, among others.
f. Materials Selection Analysis - Includes review of specification requirements, verification of materials processing and forms, review of properties and material allowables, and review of performance data in operational environments.
g. Metallography – Includes cross sectioning, mounting, and polishing of materials for microstructural analysis.
h. Metallurgical Analysis – Analysis of metallic materials, their microstructures, and the relationship between properties and microstructure.
i. Non-Destructive Evaluation (NDE) – Includes the development of NDE techniques and processes such as x-ray, ultrasonics, structured light scanning and photogrammetry for the detection of defects, flaws, and cracks in flight, development, and prototype test hardware.
j. Sustainability, Risk, and Obsolescence Analysis – Includes evaluation of environmental impact, safety, and health regulations on the sustainability, risk, and obsolescence of specific materials and processes.
3.4.3 Provide skills and services for and generate engineering products associated with multiple types of materials testing, including but not limited to:
a. Corrosion Testing – Includes characterization of materials degradation in damaging environments and evaluation of corrosion mitigation variables.
b. Mechanical Testing – Includes testing of materials at room temperature and in simulated operational environments, including but not limited to, gaseous and liquid hydrogen, nitrogen, and helium environments, to characterize performance in expected environments. The Contractor must also generate engineering products associated with the collection of materials properties supporting the generation of design allowables for materials process development and hardware designs.
c. Environmental Effects Testing – Includes testing environmental effects on materials including vacuum, atomic oxygen, ultraviolet and ionizing radiation, plasma, fluid systems, contamination, and foreign object debris.
3.4.4 Provide skills and services for, and generate engineering products associated with, the development and optimization of advanced manufacturing processes including but not limited to:
a. Additive Manufacturing Process Development – Includes the development of metallic and non-metallic additive manufacturing processes including, but not limited to, equipment testing and modification, build model generation, and post build analysis and verification.
b. Composites Process Development – Includes the development of advanced composites processing.
c. Heat Treatment Development – Includes the development of heat treatment processes to maximize material properties such as strength, hardness, and fracture toughness.
d. Metal Joining Process Development – Includes metal joining process development including fusion welding, friction stir welding, friction plug welding, brazing, and soldering.
3.4.5 Provide skills and services for, and generate engineering products associated with, the development of hardware. This includes prototype hardware and the integration of multiple materials engineering disciplines including but not limited to:
a. Hardware Prototyping – Includes multi-discipline engineering development of prototype hardware. The Contractor must operate and maintain associated tooling, instrumentation, and facilities used in the construction of prototype ground hardware and prototype flight hardware. The Contractor must also provide services and engineering products supporting the development, integration, verification, and validation of metallic and non-metallic manufacturing processes, tooling designs, and manufacturing process standards needed to move from prototype to production environments.
b. Integrated Materials Engineering – Includes integrated materials engineering support for multi-discipline hardware development activities relating to metallic and non-metallic materials, materials processing, thermal protection systems, interface materials, protective coatings, contamination control, planetary protection, and the performance of classes of materials pertinent to mission profile environments.
c.…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .