Attachment J-2 - DRL and DRD A0001.pdf

80JSC022R0003 JSC Engineering, Technology, and Science II Contract J-2

J-2-1

JSC Engineering, Technology and Science II Contract

Data Requirements List (DRL) and

Data Requirements Descriptions (DRD)

Attachment J-2

J-2-2

Data Requirements List and

Data Requirements Descriptions (Based on JSC-STD-123)

The following pages set out the documentation requirements of this contract, starting with a DRL, which is an index to the DRDs. Each DRD prescribes the required data product content, schedule, type, and other particulars for specific data submission requirements.

Subject to the Clause 52.227-14, Rights in Data - General, this document sets forth the data requirements in each Data Requirements Description (DRD) and shall govern that data required for this contract. The contractor shall furnish data defined by the DRDs. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this document. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) regulation or clause, the regulation will take precedence over this document, per FAR 52.215.33. NASA-Owned/Contractor-Held records shall be managed by the Contractor in accordance with Title 36 of the code of Federal Regulations, Chapter XII B, Records Management, and NMI 1440.6, NASA Records Management Program. The records shall be organized in accordance with the instructions in NHB 1442.1, NASA Uniform Files index, as applicable. The contractor shall disposition records and non-records in accordance with NHB 1441.1, NASA Retention Schedules, which has been approved by NASA and the National Archives and Records Administration (NARA). All questions on records management issues shall be directed through the Contracting Officer to the JSC Records Management Officer.

Documents included as applicable documents in the data requirements form a part of this document to the extent specified herein. References to documents other than applicable documents in the data requirements of this document may sometimes be utilized. These do not constitute a contractual obligation on the contractor. They are to be used only as a possible example or to provide related information to assist the contractor in developing a response to that particular data requirement.

DESCRIPTION

This document identifies and defines the requirements and data types for information and data required under this contract.

The Data Requirement Descriptions (DRDs), along with the Data Requirements List (DRL), define, by an individual Data Requirement, the information and data required for each deliverable document.

The data types are used to identify the approval and control required for each DRD. The Data Requirements List (DRL) is an index of all the DRDs by category and the data types, as described below.

Documentation submitted pursuant to this clause may incorporate references to other current approved documentation, provided the references are adequate and include such identification elements as title, document number, and approval date (where applicable). However, if the pertinent information is of relatively minor size, the contractor shall incorporate the information itself, in lieu of using a reference. The contractor shall assure that any referenced information is readily available to appropriate users of the submitted document.

NUMBER OF COPIES AND DISTRIBUTION REQUIREMENTS

J-2-3

The contractor shall submit data product as required in each DRD. Additional distribution shall be made as directed, in writing, by the Contracting Officer. The number of copies required will not exceed the limits set forth in Clause 1852.208-81, Restrictions on Printing and Duplicating, without prior Contracting Officer approval.

ELECTRONIC FORMAT

Unless otherwise specified in the DRD, all the data requirements shall be delivered in a format compatible with JSC software loads and be delivered into the JSC Engineering Design Information Infrastructure (JEDII).

JSC DDMS has transitioned to a product life cycle management (PLM) capability known as the JEDII. The JEDII System is built upon the Windchill platform utilized by most NASA centers, current human spaceflight programs, and many industry partners. JEDII provides an environment where organizations can securely store, manage, curate, and share organizational information via libraries per Agency data security and document retention schedule requirements and provides projects of any size the ability to organize and manage project related objects (Ops Cons, PMPs, SEMPs, schedules, etc.) organized by folder structure or associated directly to the appropriate level of project design. JEDII also provides projects a part-centric approach to organize project data, in addition to in-place configuration management of the project's design baseline, resulting in a single source of truth for the project. The part-centric organization also allows project data to align WBS, sub-systems, and design breakdown to be aligned in a single environment and can provide providing complete PLM for a project and resulting operational system.

DISTRIBUTION

Unless otherwise specified in the DRD, distribution, routing, and approvals will be electronically configured in JEDII at contract start.

Approval

(1) Type 1 – NASA approval -- Data and changes thereto requiring official approval by the NASA Office of Primary Responsibility (OPR) (typically in JEDII) before formal release or implementation.

Revisions/Updates may be requested by either NASA or the contractor.

(2) Type 2 - Mandatory submittal -- Data provided to NASA for coordination, information, review, and/or management control

(3) Type 3 - Submitted upon request -- Data prepared and retained under a specific contract to be made available to NASA upon request

NOTE: Documents submitted under this clause, even though directly (Type 1) or implicitly (Type 2) approved by NASA, shall not take precedence over the specifications as set out in Section C, Statement of Work or Task Orders as applicable.

The contractor shall normally deliver a complete revised Type 1 or Type 2 data requirement with NASA comments incorporated within 45 days of receipt of comments.

DRD Categories:

The DRDs are grouped into categories for clarity of purpose and ease of use. The groups are defined as follows:

• MGMT = Management – these documents address contract management processes and employee compensation

• IT = Information Technology – these documents address IT requirements.

• BP = Business Processes – these documents address non-technical business processes.

• SMA = Safety and Mission Assurance – these documents include safety assessments, problem reporting, parts assessments and requirements. They also include parts, safety, quality, reliability, and configuration management plans.

J-2-4

• RV = Planning, requirements, and verification documentation – these are project planning documents, systems requirements, specifications, and verification.

• SW = Software Specific – these documents are software requirements, design, development, and testing documents.

• TD = Technical Products and Data Packages – these documents capture the results of design reviews, testing, and analysis.

J-2-5

Table 1 - DRL Reference

NUMBER TITLE

SECTION 1.0 Contract Management MGMT-01 Contract Management Plan MGMT-02 Efficiencies and Innovations MGMT-03 Contract Management Report and Contract Management Summary Review MGMT-04 Export Control Plan MGMT-05 Contract Phase-In Plan MGMT-06 Partnership and Technology Incubation Plan

MGMT-07 RESERVED

MGMT-08 Notification of Potential Labor Dispute and Contingency Strike Plan MGMT-09 Total Compensation Plan MGMT-10 External Customer Plan MGMT-11 Technology, Innovation, and Process Improvement Plan MGMT-12 Organizational Conflicts of Interest Mitigation Plan MGMT-13 Small Business Subcontracting Plan

MGMT-14 RESERVED

SECTION 1.1 Information Technology IT-01 Information Technology (IT) Capital Planning and Investment Control (CPIC) IT-02 Information Technology (IT) Security Plan and Reports SECTION 1.2 Business Processes BP-01 NASA Contractor Financial Management Report BP-02 Data and Records Management Plan BP-03 Flights Products Configuration Management Plan

BP-04 FINANCIAL REPORTING CONTRACTOR-HELD PROPERTY

BP-05 ENVIRONMENTAL COMPLIANCE REPORTS

BP-06 New Technology Summary Report BP-07 Reports Required for Logistics BP-08 SOW 1 Cost Proposal BP-09 Government Property Management Plan BP-10 Re-procurement Data Package SECTION 1.3 Safety and Mission Assurance SMA-01 Quality Plan SMA-02 Electrical, Electronic, and Electromechanical (EEE) Parts Control Plan SMA-03 Safety and Health Plan

SMA-04 RESERVED

SMA-05 Software Assurance Plan

SMA-06 Problem Reporting and Corrective Action (PRACA) for the JSC Government Furnished Equipment (GFE) and Flight Products

SMA-07 Government-Industry Data Exchange Program (GIDEP) and NASA Advisory Problem Data Sharing and Utilization Program Documentation and Reporting

SECTION 2.0 Planning, Requirements, and Verification Documentation RV-01 Project Schedule RV-02 Regular Status Report/Summary Review RV-03 Project Technical Requirements Specification (PTRS)

J-2-6

NUMBER TITLE

RV-04 Project Requirements and Verification Document (PRVD) RV-05 Certification and Acceptance Requirements Document (CARD) RV-06 Interface Requirements Document (IRD) and/or Interface Control Document (ICD) RV-07 End Item Specification RV-08 Engineering Drawings and Model Files RV-09 Flight Projects Authorization to Proceed Record RV-10 Flight Products Verification and Validation Plan RV-11 Flight Products Qualification Plan RV-12 Flight Products Qualification Test Procedures RV-13 Flight Products Acceptance Test Procedures RV-14 Flight Products Qualification Report

SECTION 2.1

Software Requirements and Verification Documentation

SW-01 Software Requirements Document SW-02 Software Development Plan SW-03 Software Design Document SW-04 Software Code SW-05 Software Quality Assurance Plan SW-06 Software Test Description SW-07 Software Test Plan SW-08 Version Description Document (Software and/or Firmware) SECTION 2.2 Technical Products and Data Packages TD-01 Flight Products System Requirements Review (SRR) Data Package TD-02 Preliminary Design Review (PDR) Data Package TD-03 Flight Products Critical Design Review (CDR) Data Package TD-04 Acceptance Data Package (ADP) TD-05 Limited Life Items List TD-06 Certification Data Package

TD-07 RESERVED

TD-08 Engineering Analysis TD-09 Flight Products Verification and Validation Report

TD-10 RESERVED

TD-11 Test Report TD-12 Delivery and Acceptance Report TD-13 Electronic Government Certification Approval Request (eGCAR) TD-14 Flight Products Workmanship Specification List TD-15 Electrical, Electronic, and Electromechanical (EEE) Parts List and Analysis Report TD-16 Hardware Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) TD-17 Space Station Payload Safety Data Package TD-18 Hazard Reports (HRs)

TD-19 RESERVED

TD-20 RESERVED

TD-21 RESERVED

TD-22 RESERVED

J-2-7

1. DRD Title 2. Date of current version

3. DRL Line

Item No.

MGMT-01

RFP/Contract No. (Procurement completes)

Contract Management Plan 09/24/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

Document the Contractor’s overall and detailed planning and operations for successfully accomplishing the contract requirements.

Technical Administrative

S&MA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

8. Preparation Information (Include complete instructions for document preparation)

Scope: The Contract Management Plan (CMP) shall be an umbrella document, which encompasses and integrates all contract management activities necessary to successfully accomplish the contract requirements. The CMP shall provide a comprehensive integration of all management systems of the prime and subcontractors. The plan shall include those processes specifically required to accomplish the Statement of Work (SOW), as well as those systems and procedures that are to be set in place by the Contractor to adhere to regulations and requirements set forth in the solicitation and the resulting contract.

Content: The CMP shall cover, but not be limited to:

i. The contractor shall describe the overall proposed contract management approach, strategies, policies, processes for work planning, subcontractor management, and indirect cost management including any efficiencies proposed. This description shall include a description of the organizational structure and elements, including a chart depicting the organization and a description of the overall rationale for this approach.

ii. The contractor shall describe the management relationships between the contractor’s key personnel and associated NASA personnel, including communication channels, lines of authority (including the line of succession if Program Manager is unavailable), reporting relationships, and responsibilities of all organizational elements. Describe any subcontractors, team members, or joint venture partners, and their relationships within the structure or between the organizational elements and any other subcontractors, team members, or joint venture partners. Describe the reporting responsibilities of the Program Manager to corporate management and the relationship between the Program Manager and the prime’s corporate management as well as the management of any subcontractors, team members, or joint venture partners. Describe the overall authority of the Program Manager to make decisions independent of corporate management.

J-2-8

iii. The Contractor shall describe the policies, procedures, practices, and techniques for Task Order (TO) processing, including a discussion of the timeline and process/procedure associated with providing TO estimates to NASA once a TO has been received from NASA.

iv. The Contractor shall describe the policies, procedures, practices, and techniques for workforce management, including the following:

(1) Recruitment and employment methods and policies.

(2) Approach to providing flexible workforce planning. Include discussion on recruiting; communication of promotion opportunities; retention of personnel, especially high demand skill areas; and the effects on management, subcontractors, continuity and quality of services, and other factors resulting from changes in staffing levels.

(3) Approach to identify critical skills (e.g. specialty engineering) across the contract and explain how and to what level those critical skills will be maintained. Also include how the loss of a critical skill will be mitigated.

v. The Contractor shall describe the risks anticipated in successful management of the contract. Include the decision to accept, mitigate, or other action for each risk and include the rationale for each.

vi. The Contractor shall describe the methods to ensure timely delivery of quality services.

vii. The Contractor shall describe the process for the coordination and execution of all contract technical and administrative tasks, and how the contractor’s technical personnel (individuals and line managers) will interact with NASA line management.

viii. The Contractor shall describe the process to ensure the Government will receive the services ordered by providing the method, level and frequency of internal surveillance. Describe how the management policies, procedures, and techniques are monitored to ensure their effectiveness and facilitate continuous improvement.

Describe the methods of identifying deficiencies and plans for correcting deficiencies. Describe the process for Management reviews/status reviews to NASA management.

ix. The Contractor shall describe the staffing location plans, including lease arrangements, for the contractor’s off-site facilities. Discuss any other issues related to logistics management.

x. The Contractor shall describe the strategies/approach to ensure that the contractor can facilitate a proactive and efficient close out of the contract at contract end in as short a time as practicable including but not limited to possible use of the Quick Closeout procedures of FAR 42.708, NFS 1842.708 and 1842.708-70.

xi. The Contractor shall describe its approach for the fair and improved inclusion of Underserved Communities to the maximum extent possible and consistent with applicable law, in its contractor and subcontractors’ workforce performing the essential functions of the contract. This shall include the approach to attract, hire, subcontract, retain, and promote to ensure equity in professional compensation (FAR 52.222-46, Evaluation of Compensation for Professional Employees and NFS 1852.231-71 Determination of Compensation Reasonableness). The Contractor shall describe the senior leadership/corporate commitment recognizing the importance of diversity and inclusion of its workforce performing under the JET II contract to achieve NASA’s present and future mission objectives. In accordance with Executive Order 13985, Underserved communities include Black, Latino, and Indigenous and Native American persons, Asian Americans and Pacific Islanders and

J-2-9 other persons of color; members of religious minorities; lesbian, gay, bisexual, transgender, and queer (LGBTQ+) persons; persons with disabilities; persons who live in rural areas; and persons otherwise adversely affected by persistent poverty or inequality.

Format:

• Initial: See Proposal instructions

• Updates: Default

Submission: One time and as required – Type 1

• Initial: See Proposal instructions

• Final: No later than 30 days prior to contract start

• Updates: NLT 45 days after major changes in organization or approach

Distribution:

• Initial: As specified in the Proposal Instructions

• Updates: Default

Note: Upon Contract Award, the Contractor’s Contract Management Plan becomes a part of the contract.

J-2-10

1. DRD Title 2. Date of current

3. DRL Line

MGMT-02

RFP/Contract No. (Procurement completes)

Efficiencies and Innovations 9/23/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

To provide proposed contract language for Efficiencies and Innovative Techniques.

Technical Administrative

S&MA

MGMT-01 Contract Management Plan

Scope: To provide proposed contractual language for proposed efficiencies and innovative techniques for consideration by the Government. The contractual language may cut across the SOW, any IDIQ Task/Delivery Orders, and/or across multiple IDIQ Task/Delivery Orders. Such contractual language shall be implementable by the Offeror and may be incorporated into the contract through mechanisms such as a Section J Attachment, SOW language, Task Order additions/modifications, additions to other DRDs, or unique contract clauses.

Content: If innovations and efficiencies are being proposed, the contractor shall propose contractual language for the proposed innovations and/or efficiencies, identified in the Mission Suitability Factor. All innovations and efficiencies shall include a reference to the location in the Mission Suitability Volume. If accepted, proposed changes will be authorized and incorporated into the appropriate location of the contract following contract award.

Format: See Proposal Instructions

Submission: One time and revisions as required – Type 1

• Initial: As specified in the Proposal Instructions (Attachment J-16)

Distribution:

• Initial: As specified in the Proposal Instructions

J-2-11

3. DRL Line

MGMT-03

Contract Business Review/Contract Management Review and Reporting

04/12/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

Provide information on the contractor’s safety, technical, quality, financial, and deliver-to-schedule progress for use by the contract management team consisting of Engineering, S&MA, and Administrative personnel

Technical Administrative

Scope: The monthly Contract Management Report shall contain information on the contractor's safety, technical, quality, cost, and deliver- to-schedule performance. This report, along with detailed financial reports, serves as the contractor's formal reports given to NASA for contract surveillance. The information in the Contract Management Report shall discussed at the monthly Contract Business Review. The Contract Management Summary Report shall be presented at the quarterly Contract Management Review (SOW 1.1).

Content:

Contract Business Review and Contract Management Report: The contents of the review and associated report shall address all active contractual activities and performance. The Contract Business Review is typically attended by the CO, COR, Analyst as well as other NASA technical managers. The structure of the report shall be selected by the contractor and agreed upon by the NASA COR. The following shall be addressed in the review and report at a minimum:

1. SAFETY SUMMARY

• OSHA reportable events

• Personnel Injuries

• JSC on-site Close Calls and Status involving JETS II contractor personnel

2. OVERALL CONTRACT STATUS

• Key contract level metrics, including but not limited to:

o Total staffing o Voluntary Attrition o Actual vs. Bid Rate for average labor

• Status of contract Areas of Emphasis (if any)

• Status of performance against small business goals

2. COST PERFORMANCE SUMMARY

J-2-12

• Monthly Estimate Variance (Labor and NLR) o Prior and Current FY

• Monthly WYE – 533 Labor (Onsite, Offsite, Total WYE and Total Head Count) o Prior and Current FY

• EAC Trend (By Month) o Prior and Current FY

• EAC Trend (Labor and NLR) o Prior and Current FY

• SOW 1.0 (Management and Administration) EAC o Prior and Current FY

• Actual and EAC SOW 1.0 Allocation Rate o Prior and Current FY

• Percentage of FY EAC SOW 2.0 Hours vs Estimated SOW 2.0 Hours for SOW 1.0 Rate Determination

• Rate Adjustments o Remaining Adjustments o Best/Worst Case Net Impacts $

• Final Rate Status

3. Summary status of each active TO including but not limited to:

• Overall Health

• Technical

• Cost

• Schedule

• Risk

• Customer Perception

• Staffing

4. OCI

• Any changes to Organization Conflict of Interest status

Contract Management Summary Review (CMSR) and Contract Management Summary Report: The CMSR and associated report is targeted for a larger audience than the Business Review. The CMSR replaces the Business Review, but the Contract Management Report is still required each month. The COR and the contractor shall agree upon the contents of the review. The contractor shall track any actions provide a status as the next review.

The following shall be addressed in the review and report at a minimum:

• Overall status and performance for the period including issues and accomplishments

• Summary status of all remaining open Discrepancy Reports (DR) and closure plan (JETS II generated)

• Contractor initiatives during the period

J-2-13

• Status of the effort for the fair and improved inclusion of Underserved Communities

• Safety status

• Division status – accomplishments and issues

• TIPI status

• Partnership and Technology Incubation status

• External Customer status

• Cost Status

• Small Business Status

Format: Default

Submission: Reports – Monthly – Type 2, Content/Structure Updates – One time and revisions as required – Type 1

• Contract Management Summary Report: Due not later than the 15th calendar day of the month following the month being reported. (This includes months where the Contract Business Review is replaced by the CMSR)

• Contract Management Summary Review: Report delivered within 3 business days of the review.

Distribution: Default

J-2-14

3. DRL Line

MGMT-04

Export Control Plan 07/14/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

Document the contractor’s approach for export control. Technical Administrative

S&MA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional) Attachment J-17 NFS 1852.225-70, Contract Clause H.19, Subcontracting with International Partners SOW Section 1.2.5

Scope: The plan shall describe all export control activities related to the performance of contract requirements.

The plan shall include procedures for issuance of a quarterly report listing all exports affected for the subject contract on behalf of NASA by the contractor during the reporting quarter. The list is to include information describing the item exported, licenses (if acquired), exemptions, license information, transaction status, compliance activities, and records of process completion for license exceptions or exemptions classifications on those exports.

Content: The contractor shall prepare and submit an Export Control Plan (ECP), describing the contractor’s planned approach for accomplishing contract functions while adhering to export laws, regulations and directives.

The ECP shall describe the Export Control Log, which shall contain information describing the item exported, licenses (if acquired), exemptions, license information, transaction status, compliance activities, and records of process completion for license exceptions or exemptions classifications on those exports. The ECP shall identify a point of contact (POC) for all export control issues. The ECP shall identify how the Export POC will interface with the relevant NASA Export Control Representatives.

Format: Default

Submission: One time and revisions as required – Type 1

• Initial: 45 days prior to contract start

• Final: Approved 30 days prior to contract start

Distribution:

• Initial: See Proposal Instructions

J-2-15

• Updates: Default.

Note: Upon approval the contractor’s Export Control Plan becomes a part of the contract.

J-2-16

3. DRL Line

MGMT-05

Contract Phase-In Plan 04/12/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

To describe the Contractor's planned approach for contract phase-in. Technical Administrative

S&MA

Attachment J-10

Scope: A Phase-In Plan shall be prepared which describes the Contractor’s approach for the transition of responsibility from the Incumbent Contractor during the 60-day transition period. The Plan must address the Contractor’s approach to assume responsibilities by contract start.

Content: The Contractor is expected to meet full performance requirements from the start date of the base contract period. Prior to performance of services ordered by the Government under this contract, the Contractor shall accomplish all tasks required to begin work ordered under this contract.

The Offeror shall submit a Phase-in Plan which shall detail the proposed implementation processes and strategies for effecting a smooth transition. The plan shall contain, at a minimum, detailed rationale, schedule, and specific approach to successfully complete each item described below. Address the following items:

(i) Describe in detail the plan for maintaining continuous and efficient operations at JSC. Describe how you will work with incumbent Contractors and NASA, including resources and interfaces expected from each to ensure an effective transition and continuous service.

(ii) Provide a phase-in schedule to accomplish all proposed phase-in steps/milestones and the personnel responsible for those steps/milestones. Describe your approach for how you will implement the schedule.

(iii) Provide details for initial staffing and training of personnel, including the percentage of incumbent personnel that you plan to hire. Provide rationale for hiring or replacing incumbent personnel. Describe any special provisions your company has regarding hiring incumbent employees.

(iv) Address the office space that is required for phase-in.

(v) Approach for ensuring completion of badging requirements and personnel security clearances to ensure employees are cleared for access to JSC and its associated facilities, as required, prior to start of the contract.

J-2-17

(vi) Describe how an inventory will be performed with the Incumbent Contractor of all records that will be transitioned. Records transition shall be completed at contract start.

(vii) Describe your approach and risk mitigation strategies to identify any requirements for application or system connectivity or integration with JSC. This shall include the following Information Technology preparation:

1. Identify all contractor-provided applications that will need to be integrated at JSC.

2. Identify any application or system connectivity needs to or from JSC.

(viii) Address property control transfer, including schedule and milestones for completing 100% inventory including but not limited to Government Furnished Property and Installation Accountable Government Property.

(ix) Identify approach, including resources, facilities and equipment to providing offsite capabilities

(x) Identify the risks associated with your plan and ways to mitigate those risks.

• Initial: See Proposal Instructions

Distribution:

• Updates: Default.

Note: Upon Contract Award, the Contractor’s Phase-in Plan becomes a part of the contract.

J-2-18

3. DRL Line

MGMT-06

Partnership and Technology Incubation Plan 06/11/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

To attract and retain entrepreneurs and startups in commercial space and to reduce the risk of the startup environment

Technical Administrative

S&MA

MGMT-03 Contract Management Report

Scope: NASA JSC works with organizations in Houston and throughout Texas and the region to enable small business to develop and bring solutions to meet our mission objectives. The JETS II contractor may work with economic development organizations in partnership with JSC organizations to identify businesses and create on-ramps for the discovery and delivery of technology driven products or services to NASA, or for the use of space technologies in terrestrial business applications.

Content: The JETS II contractor shall develop a plan and propose approaches to:

- Attract and retain entrepreneurs and startups in commercial space and to reduce the risk of the startup environment

- Engage and facilitate the interaction with the larger aerospace community with the emphasis on Houston and the JSC local area

This plan will include specific steps which:

- Facilitate collaborations to mutually develop technologies with the aerospace industry, other industries, academia, etc.

- Facilitate technology transfer and facilitate commercialization of space technologies.

- Facilitate partnerships between NASA JSC (specifically EA and XA) and industry.

The contractor shall identify and propose approaches to achieving these goals. The contractor shall identify if NASA action is required to implement specific approaches or other dependencies, and if this action will require authorization on a Task Order or change to the contract as appropriate.

The Partnership and Technology Incubation Plan shall include sufficient rationale to demonstrate the feasibility and effectiveness of the contractor’s proposal including an analysis of benefits and risks. The plan shall include metrics that NASA can use to evaluate the effectiveness of the plan. The metrics may be included as part of J-11 Performance Evaluation Plan.

A Partnership and Technology Incubation Plan status, delivered as part of the Contract Management Summary Report, shall include a status of the metrics.

J-2-19

Format: See Proposal Instructions

Submission: One Time and Revisions as Required – Type 1

• Initial: See Proposal instructions

Distribution:

• Initial: See Proposal instructions

• Updates: Default

Note: Upon Contract Award, the Contractor’s Partnership and Technology Incubation Plan becomes a part of the contract.

J-2-20

1. DRD Title 2. Date of current version

3. DRL Line

MGMT-07

Reserved

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

Scope:

Content:

Format:

Submission:

• Initial:

Distribution:

• Initial:

• Updates:

J-2-21

1. DRD Title 2. Date of current version

3. DRL Line Item No.

MGMT-08

Notification of Potential Labor Dispute and Contingency Strike Plan

06/10/20

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

The notification of Potential Labor Dispute and Contingency Strike Plan will be used by the NASA Contracting Officer and Contractor Industrial Relations Officer to facilitate the coordination of activities between the Contractor and the affected NASA operational directorates to ensure that necessary steps are taken to prepare for any potential strike situations and to prevent the disruption of work.

S&MA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional) FAR 52.222-1, Notice to the Government of Labor Disputes

Scope: A Notification of Potential Labor Dispute must be submitted at the first indication of potential labor unrest and 45 days prior to the expiration of any Collective Bargaining Agreement. The Notification shall describe the situation that has the potential of impacting the contract and provide the corrective actions initiated. A Contingency Strike Plan must be submitted at contract start and updated if there is any indication of potential labor unrest or potential picketing activity. The Notification of Potential Labor Dispute and Contingency Strike Plan are required for the prime contractor and any subcontractors supporting this contract where the employees are represented by a union. Electronic copies of all Collective Bargaining Agreements must be provided within 60 days of ratification or modification to the Contracting Officer and Contractor Industrial Relations Officer.

Contents: The Notification of Potential Labor Dispute shall describe the situation that has the potential of impacting the timely performance of the contract, it should provide the planned negotiation dates with organized labor, and describe other corrective actions initiated. Notification should be made prior to the expiration of Collective Bargaining Agreements, prior to any significant changes to existing working conditions or pay practices, or any situation that could impact the performance of the contract through labor unrest.

The Contingency Strike Plan shall describe the Contractor’s plan for assuring the timely performance of the work under this contract during a strike or work stoppage situation. As a minimum, contents should include: information on implementation of the strike plan, a pre-strike checklist for managers and supervisors, a description of how critical work will be performed, an organization chart of the strike committee membership, phone numbers and physical location of key management personnel (including the person(s) who will be responsible for working labor relations issues), standards of conduct policies during the strike.

Format: Default

Submission: One time and revisions as required – Type 2

• Initial: Contract start

Distribution: Default (CO/COR/Contractor Industrial Relations Officer)

J-2-22 version

3. DRL Line Item No.

MGMT-09

(Insert RFP/Contract Number) Total Compensation Plan 09/27/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

The Contracting Officer must evaluate the reasonableness of compensation for service contracts in accordance with FAR 52.222-46 and JPI 1852.231- 71.

Technical Administrative

S&MA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional) FAR 52.222-41, “Service Contract Labor

Standards” FAR 52.222-46, “Evaluation of Compensation for Professional Employees” FAR 52.222-62, "Paid Sick Leave Under Executive Order 13706" FAR 52.237-10 "Identification of Uncompensated Overtime" NFS 1822.1008-2,” Successorship with Incumbent Contractor Collective Bargaining Agreement” NFS 1831.205-670, “Evaluation of Contractor and Subcontractor Compensation for Service Contracts” JPI 1852.231-71, “Determination of Compensation Reasonableness”

(a) Scope: The Total Compensation Plan (TCP) shall identify and discuss wages, salaries, and fringe benefits for professional employees and non-exempt service employees in all proposed labor categories, including those personnel subject to union agreements, the Service Contract Labor Standards, and those exempt from both of the above. By evaluating the compensation of all labor categories, this plan combines the requirements of FAR 52.222-46 and JPI 1852.231-71. The Plan shall address the requirements of the Service Contract Labor Standards and commit to the compliance of all wage determinations.

The Total Compensation Plan, Incumbent Retention and Pay (IRAP) and Fringe Benefits Analysis of Compensation Plan (FBACP) Templates shall be required for the prime team members when the total potential value is expected to exceed the certified cost or pricing data threshold set forth in FAR 15.403-4 and for all subcontractors that meet the criteria in JPI 1852.231-71(d). The IRAP and FBACP templates shall be provided as part of the Cost/Price Volume of the proposal and will be evaluated as part of the Total Compensation Plan. The TCP should be consistent with both templates. (The IRAP and FBACP Templates are not required as part of a TCP submitted after award). The TCP (excluding the templates)

J-2-23 shall become a part of the contract as Attachment J-13. A compliance matrix is not required. For TCPs submitted after award, the contractor shall submit either a Change Matrix or submit a copy of the TCP in track changes mode.

(b) Content:

(1) State the company name(s) of the prime Offeror (or joint venture team members) and subcontractor(s), using the subcontractor definition found at JPI 1852.231-71(d). For subcontractors that will submit a TCP, state whether the Government can share your compensation data with the prime Offeror. If no preference is stated, then the Government will share your compensation data with the prime Offeror.

(2) The contractor/team shall describe their commitment for compliance with the Service Contract Labor

Standards, any other applicable laws, regulations, statutes, and guidance and all wage determinations, which includes any applicable collective bargaining agreements.

(3) The contractor shall include the rationale for any conformance procedures used or those Service Contract Labor

Standards employees proposed that do not fall within the scope of any classification listed in the applicable wage determination.

(4) State contract year one direct labor rates and planned labor rate escalations for exempt and non-exempt employees. Use the IRAP Template to fulfill this requirement. Explain how wage/salary ranges and their corresponding escalation were established for each labor classification identified. Supporting information shall include data, such as recognized national and regional compensation surveys and studies of professional, public and private organizations used in establishing this proposed TCP. If the offeror is relying upon Wage Determination updates to increase the wages of contract non-exempt and non-union personnel, explain how your company plans to retain these personnel and maintain morale should the Department of Labor not escalate their wages. The contractor shall provide written support to demonstrate that its proposed compensation is reasonable. To demonstrate evidence of reasonableness, the contractor shall provide the applicable portion of the surveys/studies. The surveys/studies provided are not part of the page count.

(5) If uncompensated overtime is proposed, it shall be in accordance with FAR 52.237-10, “Identification of

Uncompensated Overtime”. If proposed, the contractor shall discuss the effects of uncompensated overtime on the Total Compensation Plan, and provide a discussion as to whether the uncompensated overtime is voluntary or involuntary. Describe the possible effects that uncompensated overtime will have on employee morale and retention. The contractor shall provide a copy of the company policy for uncompensated overtime with proposal.

This uncompensated overtime policy is not part of the page count.

(6) State the policies on seniority for benefits with regard to exempt employees. For example, with regard to leave and retirement programs, from what date is seniority calculated – the date of hire, service on the prior NASA contract, or service on all prior NASA contracts?

(7) Discuss the contractor’s company’s fringe benefit policies and practices. Each Offeror must propose a compensation structure that is sufficient to recruit and retain employees.

• For each benefit, discuss whether the benefit applies to exempt employees, non-exempt and non-union employees, and/or non-exempt and union employees, (or some combination thereof).

• For Vacation (or Paid-Time Off) map the hours to the years of service. For example: 1-5 years = X hours; 5-10 years = X hours; 10 -15 years = X hours, 15-20 years = X hours, J-2-24 and 20+=X hours.

• For insurance benefits, discuss whether the benefit applies to the employee only, or the employee and family.

• If a category is non-applicable, then insert: “N/A” in the box.

• Each item must be addressed. Offerors may add fringe benefit categories to the table below, but cannot delete benefit categories. The table may be modified to convey the information.

Fringe Benefit

Company Share of

Premiums (both % and dollar value)

Employee Share of

Premiums (both % and dollar value)

Specific Benefit

Deductibles Amount

Vesting Period

Exempt, Non-

Exempt, and/or

CBA?

Vacation Leave

Sick Leave

Paid-Time Off

Leave Roll- Over

Compensatory Time

Bereavement

Jury Duty

Military Leave

Holiday Leave

Short-Term Disability

Long-Term

Life Insurance

Accidental Death and

Overtime Pay

J-2-25

Submission: One time and revisions as required – Type 2

• Initial: See Proposal instructions

• Updates: As required and in accordance with NFS 1831.205-670, the Contracting Officer must evaluate the reasonableness of compensation for service contracts periodically after award, but at least every three years. Revisions shall be submitted with track changes.

Distribution:

• Initial: See Proposal Instructions

• Updates: Default

Fringe Benefit

Company Share of

Premiums (both % and dollar value)

Employee Share of

Premiums (both % and dollar value)

Specific Benefit

Deductibles Amount

Vesting Period

Exempt, Non-

Exempt, and/or

CBA?

Health Insurance Plan A

Health

Plan B

Dental

Vision

Health Savings Account

Retirement Benefits

401K Plan

J-2-26

3. DRL Line

MGMT-10

External Customer Plan 06/12/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

To utilize the excess capacity of certain EA and XA facilities to appropriate external entities to offset cost.

Technical Administrative

S&MA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional)

Clause H.20 EXTERNAL CUSTOMER EFFORT

NPD 1050.1: Authority to Enter into Space Act Agreements

Scope: The External Customer Plan (ECP) describes the contractor’s multi-year approach for identifying, attracting, and retaining external customers for the excess capacity of identified EA and XA facilities. The intent of the plan is to allow the contractor to utilize EA-XA Directorate facilities and associated equipment, contractor personnel and limited NASA capabilities on a non-interference basis, for the purposes of off-setting the Government’s cost of maintaining such capabilities.

Execution of ECP agreements shall be in accordance with Clause H.20 External Customer Effort. Upon approval, the ECP will become a part of the contract as Attachment J-20. After the finalized ECP is approved by NASA, the Contractor shall enter into a formal agreement with NASA that establishes the terms and conditions for use of Government property.

A report on the status of the effort shall be provided as part of the Contract Management Summary Report.

The report shall include a running list of contacts that are being or have been sought through the ECP process.

Content: The plan shall describe the contractor’s approach for offsetting the Government’s cost of maintaining facilities by marketing and using the excess capacity of the facilities.

Format: Default

• Initial: 30 days prior to contract start

Note: Upon acceptance, the Contractor’s External Customer Plan becomes a part of the contract.

J-2-27

3. DRL Line

MGMT-11

Technology, Innovations, and Process Improvement Plan

04/12/21

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

To identify and promote Technology, Innovations, and Process Improvements that will improve EA and XA products, processes, and operations.

Technical Administrative

S&MA

Scope: The JETS II contractor team shall develop a plan to promote infusion of technology and innovations into EA and XA products, processes and operations over the life of the contract. The Contractor shall identify and propose innovative techniques and methods that when implemented, would result in improved quality of products, processes or operations while maintaining or reducing costs to the Engineering and Exploration Integration and Science Directorates. The proposals must include sufficient rationale to demonstrate the feasibility and effectiveness of the contractor’s proposal including an analysis of benefits and risks. Proposed changes to processes should not be limited to those currently used or described in task orders.

Identify if NASA action is required to implement specific approaches or other dependencies, and if this action will require authorization on a Task Order under Section 2 of the SOW or other changes to the contract as appropriate.

Content: The Technology, Innovation, and Process Improvement (TIPI) plan shall include at the minimum:

• a process for identifying new technologies, innovations, best practices and process improvements

• a process for continuous assessment and reprioritization of opportunities for innovations/improvement a process for engaging external resources with the JETS II contractor and beyond

• a process for targeting areas for improvement

• a process for developing, evaluating and submitting TIPI proposals to NASA

A TIPI status, delivered as part of the Contract Management Summary Report, shall include as a minimum:

• an estimate of cost savings, and other benefit to the Government, for implemented innovations/improvements, realized during the current evaluation period, and three prior evaluation periods

• a status of the implementation of approved innovations/improvements

• a summary of new proposals for improvement/innovations of EA and XA products, processes and operations including rationale for each identified candidate

J-2-28

Format:

• Initial: See Proposal Instructions

• Updates: Default

Submission: One time and revisions as required – Type 1

• Initial: See Proposal Instructions

Distribution:

• Initial: See Proposal Instructions

Note: Upon Contract Award, the Contractor’s TIPI becomes a part of the contract.

J-2-29

3. DRL Line

MGMT-12

RFP/Contract No. (Procurement completes)

Organizational Conflicts of Interest (OCI) Plan 03/16/18

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one)

To document the Contractor’s comprehensive management approach and implementation methods for avoiding, neutralizing, mitigating, or waiving organizational conflicts of interest.

Technical Administrative

S&MA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional) FAR Subpart 9.5, Organizational and Consultant

Conflicts of Interest NFS 1852.209-71, Limitation of Future Contracting NFS 1852.237-72, Access to Sensitive Information NFS 1852.237-73, Release of Sensitive Information NASA Guide on Organizational Conflicts of Interest (March 2010)

Scope: The OCI Plan describes the Contractor’s comprehensive management approach and implementation methods for avoiding, neutralizing, mitigating, or waiving organizational conflicts of interest. After approval, the OCI Plan will become part of the contract.

Content: The OCI Plan shall discuss the following:

Purpose: A summary of the Contractor’s rationale for instituting and applying the OCI Plan.

Update Criteria: A description of the criteria and process for determining when an update to the plan is required.

Contractor’s OCI Assessment Methodology: A summary of the general methodology used to identify, avoid, neutralize, or mitigate OCI issues. Define company roles, responsibilities, and procedures for screening (i.e., identifying/recognizing, analyzing/evaluating, resolving, and reporting) existing and new business opportunities for actual/potential OCIs. Include any Contractor policies defining organizational or employee sanctions for violations of Contractor’s OCI procedures or requirements. Identify any Contractor recordkeeping or self-audit requirements related to Contractor’s OCI program. Identify any affiliated companies/entities (e.g., a parent company or a wholly owned subsidiary) and procedures for coordinating OCIs with such affiliated companies/entities. Explain how the Contractor will flow down the provisions of this mitigation plan to any subcontractor that may have a conflict with regard to performing the requirements of this contract.

Contractor’s OCI Response Procedures: A summary of the steps that the Contractor will take when an OCI has been identified or when circumstances have changed such that an OCI issue is probable. Include

J-2-30

Contractor procedures for reporting of all potential/actual OCIs during performance of the contract and the point of contact for OCI reports.

Identified OCI Risks: A description of identified potential OCI risks, due to the Contractor’s relationships or potential relationships with the Government, other companies, and other contracts. The description shall characterize the risk and measures to avoid, neutralize, or mitigate each OCI threat. If using a firewall, explain how these actions will operate to successfully address the conflict without adversely affecting performance of the contract. Additionally, Contractor shall identify any potential OCIs created by the requirements of this RFP which the Contractor intended to resolve using methods other than mitigation.

Personnel Clearance Procedures: A description of the procedures the…