Attachment I-02 Data Requirements Description (DRD) Amendment 00002.pdf

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-1

Attachment I-2

Data Requirements Description (DRD)

Contract Data Requirements List

National Aeronautics and Space Administration NASA Shared Services Center (NSSC)

NASA Transformational Shared Services (NTSS)

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-2

DOCUMENT CHANGE LOG

DRD No. DRD Title Revision Date

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-3

INTRODUCTION

This document defines the requirements for contractual data to be delivered by the contractor to the Government. The data requirements are set forth in each Data Requirements Description (DRD) and shall govern that data required by the contract. The contractor shall furnish data defined by the DRDs as listed on the Contract Data Requirements List (CDRL) by category of data, attached hereto, and made a part of this contract. 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) clause or other term (e.g., requirements statement), that clause or term shall take precedence over the DRD.

Contract Data Requirements List (CDRL): Throughout the performance of the contract, the CDRL provides a listing by number, data type, title, and Office of Primary Responsibility

(OPR).

Data Requirements Description (DRD): Each DRD included in this CDRL prescribes content, format, and submittal requirements. The DRDs included in this CDRL are ordered sequentially as listed in the CDRL page(s) that precede(s) the actual DRDs.

Data Type Description: Each DRD is classified by data type as defined below:

TYPE DESCRIPTION

1 - All submittals of and interim changes to Type 1 DRDs require written approval from the contracting officer before formal release for use or implementation.

2 - NASA reserves a time-limited right to disapprove in writing any submittal of and interim changes to Type 2 DRDs. The contractor shall submit the required data to NASA for review within the time period established in the DRD prior to its release for use or implementation. The contractor shall clearly identify the release target date. If the data is unacceptable, the contracting officer will notify the contractor within the time period established in the DRD from the date of submission, regardless of the intended release date. The contractor shall resubmit the information for reevaluation if disapproved. The submittal is considered approved if the contractor does not receive disapproval or an extension request from the contracting officer within the time period established in the DRD.

3 – Type 3 DRDs shall be delivered as required by the contract and do not require NASA approval.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-4

STATEMENT OF GENERAL REQUIREMENTS

Subcontractor Data Requirement The prime contractor is responsible for flowing down any specific data requirements that apply to subcontracts and vendor agreements.

Reference to subcontractor data in the contractor’s responses is permissible and a copy of the referenced subcontractor data must be supplied with the response document at time of delivery to

NASA.

Data Distribution, Format, and Transmittal Distribution: Distribution recipients and number of copies are identified within each DRD, provided within the contract, or as directed by the Contracting Officer (CO).

Format Electronic Format: Electronic submission of data deliverables is required. Electronic deliverables shall be printable. Data deliverables shall be delivered to NASA in the format specified below unless a specific format is required by a DRD. Data submittals shall consist of a single Adobe Acrobat PDF file and the native format electronic file(s). The preferred native formats include Microsoft Word, Excel, or PowerPoint, as appropriate.

Hardcopy Format: Hardcopy of data deliverables is not required unless electronic delivery is not possible.

Transmittal Data shall be transmitted to NASA by entry into Specify electronic system (e.g.,TechDoc)), or choose one or a combination of the following: email or other mechanism agreed to by the Contracting Officer (CO), Contracting Officer’s Representative (COR), and project representatives who are responsible to receive, index, and store the data deliverables.

If email is used to transmit data deliverables, the email size shall be 10 megabytes or less to ensure receipt by the NASA email servers. Encrypted email format shall be used to transmit data.

Data Transmittal Package: Each data transmittal package shall include a transmittal memorandum that specifies the following:

1. Contract number

2. Data Requirements Description (DRD) number

3. DRD data type

4. Submission date or milestone being satisfied

5. Document number and revision

6. Document title

7. File names of all files being delivered; file naming convention shall clearly identify the document being delivered

8. NASA Records Retention Schedule (NRRS) number, if applicable (See NRRS 1441.1, NASA Records Retention Schedules)

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-5

Document Identification: For all data types, the document number, change legend, date, and title constitute the minimum identification of the specific document and shall appear on the cover and title page. The contract number shall also appear on the cover and title page as separate markings.

The originator and organization shall be included on the title page. The document number, change legend, and date shall appear on each page of the document. All Type 1 documentation shall be marked “PRELIMINARY PENDING NASA APPROVAL,” and once approved shall be reissued with “APPROVED BY NASA” and the date and approval authority annotated on the cover.

Data Restriction Determination and Marking Requirements: The contractor shall properly mark data in accordance with the data rights clause(s) included in the contract. The contractor must make a determination for each individual data deliverable, and shall not apply a default or blanket data restriction marking to all data deliverables (e.g., “data may be export restricted”). If NASA does not agree with the contractor applied data restriction, the CO shall return the data to the contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the “data rights” clause(s) contained in the contract.

Reference to Other Documents and Data Deliverables in Data Submittals: All referenced documents shall be made readily available to the cognizant NASA organization upon request.

Document Revisions

Revisions of documentation previously submitted may be accomplished either by individual page revision or by a complete reissue of the document.

A document shall be completely reissued when, in the opinion of the contractor and/or NASA, the document has been revised to the extent that it is unusable in its present state, or when directed by the CO. When complete reissues are made, the entire contents of the document shall be brought up to date and shall incorporate revised pages. All revisions shall be recorded. A revision log shall identify complete reissues except for periodic reports and documents which are complete within themselves as final.

Individual page revisions shall be made as deemed necessary by the contractor or as directed by the CO.

Changes of a minor nature to correct obvious typing errors, misspelled words, etc., shall only be made when a substantial change is made, unless the accuracy of the document is affected.

All revised pages shall be identified by a revision identifier and a new date. Each document shall contain a log of revised pages that identify the revision status of each page with the revision symbol. This list shall follow the table of contents in each document. The line or lines revised on a given page shall be designated using vertical line in the margin of the page, and the change authority shall be indicated adjacent to the change.

CDRL/DRD MAINTENANCE PROCEDURES

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-6

NASA-Initiated Change: New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion shall be appended. The contractor shall notify the CO in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision is appended.

CDRL or DRD Change Procedures Revisions to the CDRL or DRDs will be identified by NASA in the Document Change Log. The date of the revision, DRD number, title, and revision description will be annotated in the Document Change Log. Revision descriptions will include the modification number, which implements the change, and a brief description of the portions of the CDRL and/or DRD affected within the “Revision” column of the Document Change Log.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-7

Contract Data Requirements List

DRD

No.

DRD

Type

DRD Title OPR

1.0-1 1 Organizational Conflict of Interest Office of Procurement (OP)

1.0-2 3 True Up Submission NSSC

1.0-3 3 Re-procurement Data Package NSSC

2.1-1 3 Employee Roster NSSC

2.1-2 3 Equal Employment Opportunity Report NSSC

2.1-3 3 Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan OP

2.2-1 3 Records Management Plan and Records Management Reports NSSC

2.5-1 3 Contract Performance Measurement Plan NSSC

2.5-2 3 Contract Performance (Metrics) Report NSSC

2.7-1 1 NSSC IT Support Security Management Plan NSSC

2.7-2 3 Key Control and Media Control Reports NSSC

2.8-1 3 Safety and Health Incident (Anomaly) Reports NSSC

2.8-2 1 NSSC IT Support Disaster Recovery Plan NSSC

2.9-1 1 Risk Management Plan NSSC

2.10-1 1 Quality Control Plan NSSC

2.11-1 3 Financial Management Analysis Report NSSC

2.11-2 3 Contractor Accounting Calendar and Productive Hours NSSC

2.11-3 3 Annual Phased Operating Plan NSSC

2.11-4 3 Operational Invoice Validation Data NSSC

2.11-5 3 Operational Invoice Validation Labor Library NSSC

2.17-1 3 Customer Satisfaction Assessment Report NSSC

2.19-1 3 IT Seat and System Hardware Asset Plan NSSC

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-8

3.0-1 3 NSSC Service Delivery Guides (SDG), Work Instructions, Knowledge Articles, web pages and Customer Guides NSSC

3.1-1 3 Financial Management Reports NSSC- Financial

Management Services (FM)

3.1-2 3 Report AP, AR, FBWT and Travel CMPs according to the responsibilities listed in the Agency CMP Manual NSSC-FM

3.1-3 3 Treasury System Administrator Reports NSSC-FM

3.1-4 3 Report, International Transactions of the Federal Government NSSC-FM

3.1-5 3 Treasury Report on Receivables (TROR) and Debt Collection Activities NSSC-FM

3.1-6 3 Fund Balance with Treasury Reports – FMS 224 reporting NSSC-FM

3.1-7 3 Quarterly Report of Recommendations for Open Obligations Against Relocation Contracts NSSC-FM

3.1-8 3 Monthly Unliquidated Obligations Report for Completed Travel NSSC-FM

3.1-9 3 Annual Review of Real Estate Entitlements Report NSSC-FM

3.1-10 3 Report, Office of Government Ethics (OGE): Form 1353 - Semi-Annual Non-Federal Source Payment Report NSSC-FM

3.1-11 3 Officials-in-Charge (OIC) Travel Report NSSC-FM

3.1-12 3 Report, Premium Class Travel Report NSSC-FM

3.1-13 3 Travel Reporting Information Profile (TRIP) Report NSSC-FM

3.1-14 3 Report, China Authorizations Report NSSC-FM

3.1-15 3 Bi-Annual Relocation Open Deck Review NSSC-FM

3.1-16 3 Relocation Income Tax Allowance (RITA) and Extended TDY Tax Reimbursement Allowance (ETTRA) monitoring and reporting

NSSC-FM

3.1-17 3 Quarterly Travel BOC Write-off Report NSSC-FM

3.1-18 3 Audit, Monthly GSA Transportation Post payment Audit for completed transportation disbursements NSSC-FM

3.1-19 3 Report, Monthly Excluded Parties List System (EPLS) Process NSSC-FM

3.1-20 3 Reconcile Final Federal Financial Report (FFR) (SF-425) NSSC-FM

3.2.1.1-1 3 Drug Testing Reports NSSC- Human

Resources Services

(HR)

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-9

3.2.20-1 3 Federal Workers’ Compensation Program (FWCP) Utilization and Costs NSSC-HR

3.2.21.4-1 3 HR Survey Reports NSSC-HR

3.2.23-1 3 SES Executive Core Qualifications (ECQs) Metric Reports NSSC-HR

3.3.13-1 3 Purchase Cardholder Report – Open Cardholders NSSC- Procurement Services (PR)

3.3.13-2 3 Purchase Card Approving Official Report NSSC-PR

3.3.13-3 3 Purchase Card CFO Delinquency Reporting NSSC-PR

3.3.13-4 3 Purchase Card Monthly Transactional, Desk and Convenience Check Audit Reporting NSSC-PR

3.3.13-5 3 Purchase Card Aging Order Log Status Report NSSC-PR

3.3.13-6 3 Purchase Card Monthly Violator Tracking Status Report NSSC-PR

3.3.13-7 3 Purchase Card Service Now (SNOW) Weekly Analysis Report NSSC-PR

3.3.13-8 3 Purchase Card Office of Management and Budget (OMB) Quarterly Reporting NSSC-PR

3.3.13-9 3 Purchase Card “Cardholder Profile” Report NSSC-PR

3.3.13-10 3 Purchase Cardholder Reconciliation Violators NSSC-PR

3.3.13-11 3 NASA Active Cardholders FOIA Report NSSC-PR

3.8.2-1 1 Innovation and Transformation (I&T) Plan NSSC

3.9.2-1 3 NCCIPS Utilization and Billing Reports (Customer Billing & Supplemental Reports)

National Center for Critical Information

Processing and Storage (NCCIPS)

3.9.2-2 3 NCCIPS Planning, Programming, Budgeting, and Execution

(PPBE) NCCIPS

3.9.2-3 3 NCCIPS Economic Impact Report NCCIPS

3.9.2-4 3 NCCIPS Financial Status Report NCCIPS

3.10.1-1 3 Review, Continuous Improvement Strategies, and Shared Services Leading Practices NSSC

3.10.1-2 1 Transition of Level of Effort (LOE) to Fixed Unit Price (FUP) Transactional Services NSSC

3.10.2-1 3 Intelligent Automation Services (IAS) NSSC

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-10

1. DRD Title: Organizational Conflicts of Interest (OCI) Plan

2. DRD No.: 1.0-1 3. Data Type: 1 4.OPR: OP

5. Solicitation No.: 80NSSC23R0001

6. Contract No.: TBD

7. Date Issued: RFP Date

8. Date Revised: N/A 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Plan will communicate the contractor’s approach to identify and resolve OCIs.

The contractor will be held accountable for identifying, dispositioning, and reporting OCIs during contract performance.

11. Distribution: Initial submission shall be per the RFP instructions. As needed submissions shall be electronically submitted to the Administrative Contracting Officer (ACO), Contracting Officer’s Representative (COR), and Alternate Contracting Officer’s Representative (ACOR)

Initial Submission: Plan shall be submitted with the initial proposal.

Submission Frequency: As needed

Format: Contractor’s format is acceptable. The electronic format: Microsoft Office.

Interrelationship: NASA Federal Acquisition Regulation (FAR) Supplement (NFS) 1852.209-71, Limitation of Future Contracting, NFS 1852.237-72, Access to Sensitive Information, NFS 1852.237-73, Release of Sensitive Information, Section I, Model Contract Section 6.5, NFS 1852.209-71 Limitation Of Future Contracting.

Applicable Documents: FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, NFS 1809.500, NASA Guide on Organizational Conflicts of Interest.

Scope: The OCI Plan describes the contractor’s comprehensive approach to identify, avoid, mitigate, neutralize, and report potential OCI issues, including conflicts described in the solicitation and those discovered during contract performance.

Contents: The OCI Plan shall meet the requirements of FAR 9.5 and include the following:

1. Point of contact for OCI issues and reports.

2. Demonstrate an understanding of (1) OCI principles and (2) the full breadth of OCI issues and the types of harm that can result. The Plan at a minimum addresses the three primary types of OCIs (i.e., biased ground rules, unequal access to information, and impaired objectivity).

3. Define company roles, responsibilities, and procedures for (1) screening (i.e., identifying/recognizing, analyzing/evaluating, resolving, and reporting) existing and new business opportunities for actual/potential OCIs and (2) monitoring and reporting all potential/actual OCIs that

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-11 arise, resolving conflicts, and reporting previously unidentified OCIs or potential OCIs to the Government.

4. Describe how employees are notified of the Plan’s requirements and how this notification will be documented. Establish and require entrance training for new employees, refresher training for existing employees, and exit training for departing employees. Describe how completion of this training will be documented, including a copy of any training certification template that the contractor will use to document that its employees have completed training.

5. Describe how the contractor will report breaches of the protective measures in the Plan to the contracting officer. The Plan should describe what processes the contractor will implement following any breach and should indicate that final resolution of the corrective action must be approved by the contracting officer.

6. 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.

7. Address the process for reporting all potential/actual OCIs that arise during performance of the contract. An OCI report shall include (1) a description of the conflict, (2) the plan for resolving the conflict, and (3) the benefits/risks to contract performance associated with plan approval/acceptance.

Specific resolution strategies shall be appended to the Plan upon approval by the Government.

8. Explain how the contractor will flow down the provisions of this Plan to any subcontractor that may have a conflict with regard to performing the requirements of this contract. Discuss affected subcontractors’ OCI program as it relates to this contract and specifically explain how affected subcontractors will identify, resolve, and report actual/potential OCIs associated with this contract.

9. Define organizational and employee sanctions for violations of established OCI procedures/requirements/guidelines.

10. Include an assertion from the Contractor that to the best of their knowledge no OCIs exist currently, if applicable. Provide a list of all the prime’s and subcontractor’s Active NASA contracts and subcontracts, which would provide the CO a better understanding of other NASA work currently being perform by the Offeror that may give rise to an actual or potential conflict.

11. Include a requirement to update this plan as necessary to address specific OCIs. All updates to the plan must be approved by the contracting officer and the updates/changes must be incorporated in the contract to be effective.

12. Require periodic self-audits to ensure compliance with established OCI procedures/requirements/guidelines.

13. Document the training requirements for employees that have access to sensitive information and describe the procedures in the Plan that ensures safeguard of sensitive information and preclude unauthorized access or disclosure. What procedures/documentation (e.g., non-disclosure statement) are in place to identify these employees and validate that these employees will comply with

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-12 mandatory protections of sensitive information.

14. Define records related to the OCI plan (e.g., training and audit records) that will be made available to the Government upon request. Note: The OCI Plan as outlined in paragraphs 1 through 14 above is not for the purpose of addressing other very important contractual obligations such as (1) the contractor’s obligation to protect sensitive information in accordance with NFS 1852.237-72, Access to Sensitive Information, (2) the contractor’s obligation to conduct business in an ethical manner in accordance with FAR 52.203-13, contractor’s Code of Business Ethics and Conduct, and (3) the contractor’s obligation to prevent personal conflicts of interest in accordance with FAR 52.203-16, Preventing Personal Conflicts of Interest.

15. In an appendix to the OCI Plan identify the strategy (e.g., mitigation, limitation on future contracting, etc.) for resolving each OCI that is either identified in the solicitation or created by the requirements of the solicitation/contract and explain the effect of such strategy on performance of the contract. If using a firewall, explain how these actions will operate to successfully address the conflict without adversely affecting performance of the contract. (Note: Specific plans to limit future competition are reflected in the clause at NFS 1852.209-71, Limitation of Future Contracting.)

Remarks: N/A

Maintenance: The contractor shall review the OCI Plan on an annual basis or as directed by the contracting officer to revise the OCI Plan if necessary. Revisions are subject to Contracting Officer approval and shall be incorporated by change page or complete reissue.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-13

1. DRD Title: True Up Submission

2. DRD No.: 1.0-2 3. Data Type: 3 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: The Service Provider shall provide contractual data related to the contract order (I-14) that reconciles with the correlating invoice submitted.

11. Distribution: Electronically to the CO, ACO, COR, and ACOR.

Initial Submission: 60 calendar days after end of contract year 1.

Submission Frequency: 60 calendar days after end of contract year 2 – 8 for all task orders.

Format: Format shall be submitted in Microsoft Office Excel. Format is subject to change as needed and agreed upon with the Government.

Data elements are describe in tables below.

The Excel File must include the Task Order Number and contract year.

FUP

Format Layout shall utilize I-14, adding columns to capture Increase/Decrease Units, Increase/Decrease Rate, Increase/Decrease ODC, Total Value Increase/Decrease, Revised Total Units, FFP Rate, Revised Total ODC, Revised Total Value:

CLIN WBS PWS Description Quantity FFP Rate ODC Total Value

Increase/ Decrease

Unit

Increase/Decrease Rate

Increase/Decrease

ODC

Total Value Increase/Decrease

Revised Total Units

FFP Rate Revised Total

ODC

Revised Total

LOE

Format Layout shall utilize I-14, adding columns to capture Increase/Decrease Hours, Increase/Decrease Dollars, Revised Total Labor Hours, Revised Total Value:

CLIN WBS PWS Description Labor Category

Labor Hours Order

FFP

Rate

Increase/ Decrease Hours

Increase/ Decrease Dollars

Revised Total Labor Hours

Revised

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-14

LOE ODC

CLIN WBS PWS Description ODC Total Order

Increase/ Decrease Dollars

Revised

Interrelationship: Model Contract 3.3, 3.4

Applicable Documents: I-14 Contract Line Items/Order Template

Scope: N/A

Contents:

The SP shall provide data that includes both Fixed Unit Price (FUP) transactions, Level Of Effort (LOE) hours, and Other Direct Cost (ODC). The data provided will be provided in the format as mentioned above.

Maintenance: Changes shall be incorporated by complete reissue.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-15

1. DRD Title: Re-procurement Data Package

2. DRD No.: 1.0-3 3. Data Type: 3 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: Provides requirements for delivery to NASA of information on specific items and supporting documentation related to resource/cost information, to be used for re-procurement activities. In the event of a competitive solicitation for a follow-on effort, NASA may provide non-proprietary historical information such as average composite direct labor rates and approximate seniority profiles of incumbent personnel to all interested parties in order to increase the probability of realistic pricing. The Government does not intend to disclose any contractor proprietary information.

11. Distribution: Electronically to the CO, ACO, COR, and ACOR.

Initial Submission: Due within 30 days of a written request from the Contracting Officer. Subcontractors may submit the requested data directly to the Contracting Officer.

Submission Frequency: N/A

Format: Format shall be submitted in Microsoft Office Excel.

Interrelationship: N/A

Applicable Documents: N/A

Scope: Resource/cost information shall be submitted in accordance with this Data Requirement Description

(DRD).

Contents:

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-16

Scope: Resource/cost information shall be submitted in accordance with this Data Requirement Description (DRD).

Content: A data package shall be submitted containing the following resource/cost information. This data is required from the prime and all subcontractors with at least three (3) Work Year Equivalents (WYEs). Additionally, the combination of prime and subcontractor WYEs must account for no less than 95% of the existing WYEs. If necessary, include subcontractors with less than three (3) WYEs in order to account for no less than 95% of the existing WYEs unless, at the discretion of the Contracting Officer (CO) a percentage of less than 95% is allowable.

1. Labor Resources

a. List of directly charged labor skills by contractor labor category, mapped to NASA’s Standard Labor Categories (SLCs) as identified in Attachment I-12 Labor Categories and/or follow on contract as directed by the CO. Additionally, the information shall be segregated by current Performance Work Statement (PWS) section. Include the number of WYEs currently supporting each PWS section. The WYE detail shall be at the lowest PWS level for which current contract tracking is available. Ensure that WYEs counted at the lowest PWS level are not counted again at the next highest SOW level. See example provided below in Table 1.

Table 1: Example of Data Required per Paragraph (1a):

NASA SLC Contractor Labor Category PWS Section *No. of WYEs

Financial Specialist 3.1 1.75

Human Resource Specialist

3.2 6.25

Procurement Specialist

3.3 4.5

*A WYE is defined as the work of a full-time equivalent person based on your accounting system.

For example, if your accounting system dictates that a WYE constitutes 1,872 productive hours (total hours minus paid time off), then four people working 468 hours per year would make up one WYE.

b. The weighted average current straight time labor rate for each direct-charged labor category identified in paragraph (1a), including the source data that comprises the weighted average rate. Further, provide both the date when these wages were last adjusted for escalation by contractor labor category, and the rate of escalation applied. Also indicate whether any adjustments are projected to be made prior to contract expiration. If so, provide the anticipated date(s) and rate of escalation, and identify the contractor labor categories expected to be affected. See example provided below in Table 2.

Please ensure that all data clearly map to NASA SLCs identified in Attachment I-12 (current contract) and/or follow-on contract.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-17

Table 2: Example of Data Required per Paragraph (1b):

NASA SLC Contractor Labor

Category

No. of WYEs

**Direct Labor Rate

Last Escalation Date and Amount

Future Escalation Date and Amount

Exempt or Non-exempt?

Financial Specialist

1.75 $23.25 April 2022 (2.70%)

April 2023 (3.20%)

Exempt

Human Resource Specialist

6.25 $26.12 April 2022 (2.70%)

April 2023 (3.20%)

Exempt

Procurement Specialist

4.5 $27.12 April 2022 (2.70%)

April 2023 (3.20%)

Exempt

**This is the current weighted average straight-time direct labor rate with NO BURDENS APPLIED and is NOT the contract’s Section B rate table rates, if there are any. The individual direct labor information for each WYE component is also required and shall support the weighted average direct labor rate for each SLC.

c. Seniority level of all WYEs identified in paragraph (1a) above, for fringe benefit calculation purposes. Provide data separately for exempt and non-exempt personnel:

i. Number of WYEs with 0 to less than 5 years of experience.

ii. Number of WYEs with 5 years to less than 10 years of experience.

iii. Number of WYEs with 10 years to less than 15 years of experience.

iv. Number of WYEs with 15 or more years of experience.

d. Insurance categories for all WYEs identified in paragraph (1a) above, for fringe benefit calculation purposes.

i. Number of WYEs with single insurance

ii. Number of WYEs with single +1 insurance

iii. Number of WYEs with single + family insurance

2. Non-Labor Resources

a. Provide total non-labor cost incurred for the most recent 12 month period grouped by expense type (examples may include travel, training, facilities).

Maintenance: Revisions to this DRD shall be incorporated by change page or complete reissue. Revisions are subject to Contracting Officer approval.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-18

1. DRD Title: Employee Roster

2. DRD No.: 2.1-1 3. Data Type: 3 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: The NSSC will utilize the electronically maintained SP Employee Roster for administrative and emergency action purposes.

11. Distribution: NSSC Electronic Library (NSSC CO, Delegates, and NSSC Safety and Security POC)

Initial Submission: 30 days following the start of contract performance.

Submission Frequency: Monthly

Format: Format shall be submitted in Microsoft Office Excel.

Interrelationship:

PWS 2.1.1, SP Personnel Training

Applicable Documents:

NSPLN-1040-0002, Rev. 6.0, NSSC Emergency Action Plan NPR 8715.3D, NASA General Safety Program Requirements

Scope: The SP Employee Roster provides an electronically maintained roster listing of all SP employees working on this contract and shall be available for review at any time by the NSSC CO and the NSSC Emergency Coordinator

Contents: Electronic SP Employee Roster shall include the following data:

o Employee Name;

o Labor Category/Job Title;

o Phone/Cell Number;

o Onsite/Offsite;

o Full Time/Part Time/Less than Part Time;

o Email address; and o Emergency Point of Contact.

Remarks: The SP Employee Roster contains PII information and shall be stored and handled utilizing the requirements set forth within the Privacy Act of 1974 and NPD 1382.17K, NASA Privacy Policy. NASA policy is to: Protect all forms of controlled unclassified information (CUI), including personal information

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-19 and to comply with Federal law and regulations governing management of all personal information collected, used, maintained, and disseminated by or on behalf of NASA in electronic or non-electronic form.

Maintenance: N/A

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-20

1. DRD Title: Equal Employment Opportunity Report

2. DRD No.: 2.1-2 3. Data Type: 3 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: This report will be used by NASA personnel to access the Service Provider’s Equal Employment Opportunity compliance and the Diversity management of the contract effort.

11. Distribution: NSSC Electronic Library (NSSC COR; NSSC CO and Delegates)

Initial Submission: Six (6) months after the start of the contract performance.

Submission Frequency: Every 6 months

Format: The format shall be provided in an electronic format in accordance with Attachment A “SP Equal Employment Opportunity and Diversity and Inclusion Semiannual Report”, Attachment B “SP Equal Employment Opportunity and Diversity and Inclusion Semiannual Report”, and Attachment C “SP Equal Employment Opportunity and Diversity and Inclusion Semiannual Report” formats.

Interrelationship: PWS Section 2.1

Applicable Documents: N/A

Scope: N/A

Contents:

Attachment A Data – SP Equal Employment Opportunity and Diversity and Inclusion Semiannual Report Period 00/00/0000 thru 00/00/0000

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-21

Attachment B Data – SP Equal Employment Opportunity and Diversity and Inclusion Semiannual Report

Attachment C Data – SP Equal Employment Opportunity and Diversity and Inclusion Semiannual Report

A. Recruiting Efforts/Activities:

B. Diversity and Inclusion Efforts/Activities:

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-22

1. DRD Title: Diversity, Equity, Inclusion, and Accessibility (DEIA) Plan

2. DRD No.: 2.1-3 3. Data Type: 3 4. OPR: OP

Administrative ☒

S&MA ☐

10. Description/Use: The DEIA plan demonstrates the contractor’s commitment to fairness regarding diversity, equity, inclusion, and accessibility. This plan will provide NASA with an understanding of how the contractor plans to recruit, retain, and develop a diverse high performing workforce from underserved communities. The plan shall include measurable performance metrics and objectives. The DEIA plan will be utilized as an assessment tool by the contracting officer to monitor the contractor’s progression in its commitment to diversifying its workforce.

11. Distribution: Shall be electronically submitted to the ACO, COR, and ACOR.

Initial Submission: Plan shall be submitted within 30 days of the start of contract performance.

Submission Frequency: Update annually

Format: Contractor’s format is acceptable.

Interrelationship: N/A

Applicable Documents: Executive Order 13985, Advancing Racial Equity and Support for Underserved Communities Through the Federal Government

Scope: In support of the Executive Order 13985, Advancing Racial Equity and Support for Underserved Communities Through the Federal Government, NASA is seeking to advance equity or remove barriers for members of underserved communities to access procurement opportunities. Underserved communities refer to populations sharing a particular characteristic, as well as geographic communities, that have been systematically denied a full opportunity to participate in aspects of economic, social, and civic life.

Underserved Communities include Black, Latino, Indigenous, Native American, Asian Americans and Pacific Islanders and 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.

Contents:

The DEIA Plan shall identify qualitative and quantitative approaches utilized to measure progress in the areas of Leadership and Commitment, Diverse Talent, and Culture and Sustainability. The following shall be addressed annually:

Leadership and Commitment – Demonstrate leadership’s commitment and accountability to diversity, equity, and inclusion. Identify quantitative approaches utilized to measure progress of a Diversity and Inclusion program

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-23

1. What is the operational status of, and level of resources available to, offices or divisions within the organization that are responsible for advancing civil rights or whose mandates specifically include serving underrepresented or disadvantaged communities?

2. What actions has the organization taken to implement affirmative equity-enhancing policies, regulations, guidance, and approaches to emphasizing equity in policy- and rule-making processes?

3. Describe how the organization’s commitment will be communicated internally and externally from leadership to employees and stakeholders.

Diverse Talent – Demonstrate a pursuit of a high performing diverse workforce from underserved communities.

1. Discuss the specific diversity metrics utilized by the organization to measure performance in achieving a diverse workforce and provide the corresponding metrics for the current or most recent organizational reporting period

2. What barriers or opportunities exist to engage subject matter experts from underserved communities in industry and academia? How does the organization plan to overcome those barriers?

3. How will underserved communities be leveraged?

4. Describe recruiting activities, objectives, and outcomes (e.g., number of participants, number interviewed and hired from underserved communities).

Culture & Sustainability – Demonstrate how an inclusive and fair work environment will be cultivated and maintained.

1. Based on the data, what structures and strategies will be used to manage diversity, measure results, refine approaches, and institutionalize a culture of inclusion?

2. Identify actionable opportunities to improve data collection, use, and sharing that would allow for disaggregation, the ability to deliver services more equitably, and better understanding of how programmatic and policy decisions impact underserved communities.

3. Describe other corporate activities that seek to increase support of diversity, equity, and inclusion.

Maintenance: Changes shall be incorporated by change page or complete reissue.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-24

1. DRD Title: Records Management Plan and Records Management Reports

2. DRD No.: 2.2-1 3. Data Type: 3 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: The Service Provider shall develop a plan for documentation development, organization, and management of NSSC records. The NSSC will utilize the plan and reports to ensure compliance with NASA Records Management Procedural Requirements.

11. Distribution: NSSC Electronic Library (NSSC COR, NSSC CO; Delegates)

Initial Submission: 30 days after the start of contract performance

Submission Frequency: Annual review with incorporated changes

Format: Microsoft Excel and Word

Interrelationship:

PWS Section 2.2, Records, Documents and Forms Management

Applicable Documents:

NPR1441.1E, NASA Records Management Program Requirements NPD 1420.1A, NASA Forms Management National Archives and Records Administration (NARA), Recordkeeping Requirements

Scope: The plan shall address and assure timely and accurate organization, identification, marking, management, preservation and disposition of NASA documentation, records, and forms regardless of format.

Contents: The SP shall develop a Records Management Plan for documentation development, organization, and operation of the NSSC records, documents, and forms management programs in accordance with NPR 1441.1E, NASA Records Management Program Requirements and PWS Section 2.2, Records and Forms Management

Remarks: Product shall be compatible with Microsoft Office Suite of software.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-25

1. DRD Title: Contract Performance Measurement Plan

2. DRD No.: 2.5-1 3. Data Type: 3 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: The Service Provider shall provide a comprehensive plan for the development of performance measures addressing timeliness, accuracy, and quality of work performed.

11. Distribution: NSSC Electronic Library (NSSC COR, NSSC CO, Delegates)

Initial Submission: 90 days following the start of contract performance.

Submission Frequency: Annually

Format: Format shall be the existing “NSSC Performance Management Plan” format. Format shall be compatible with Microsoft Office Suite of Software. Format is subject to change as needed and agreed upon with the Government.

Interrelationship: PWS Section 2.5, DRD 2.5-2

Applicable Documents: N/A

Scope: N/A

Contents:

Report shall include all utilization numbers and transactions totals for all services and actions identified in Attachment I-3. The report shall identify the strategy for timely creation of the outputs described in the Contract Metrics Performance (DRD 2.5-2)shall be included in the plan.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-26

1. DRD Title: Contract Performance (Metrics) Report

2. DRD No.: 2.5-2 3. Data Type: 3 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: The report is used to provide Government insight into service provider performance and utilization data in accordance with the NSSC Service Level Agreement. This data will be used by the NSSC Budget and Accounting Division to create the Center and Customer bills for utilization of services.

11. Distribution: Electronic dashboard, NSSC Electronic Library(NSSC COR, NSSC CO, NSSC Budget and Accounting Division, Delegates) via electronic submission.

Initial Submission: 10 calendar days after the end of the first month of contract performance.

Submission Frequency: Monthly (Draft 10 calendar days after the end of the reporting period, Final within 15 calendar days after the end of the reporting period)

Format: The report format shall be in Microsoft Excel. The report retention shall be in a searchable, reportable electronic repository with Government access.

Interrelationship: PWS Section 2.5

Applicable Documents: N/A

Scope: N/A

Contents:

The electronic dashboard shall continuously track the SLIs, and performance measures contained in Attachment I-3 and Attachment I-21 in the contract. The dashboard produced report shall include the total utilization of all actions defined in the Unit of Measure sections of the Service Catalog and Service Level Indicators (SLI).

Remarks: All Bill Reports are available to the public at https://www.nasa.gov/centers/nssc/metrics. Civil Servants in the Business and Administration Office produce the Center Utilization totals (bills) at the end of each month using the SP produced DRD.

Maintenance: Maintain in data warehouse, dashboards, and analytics, and/or other electronic repositories as agreed to with the Government https://www.nasa.gov/centers/nssc/metrics

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-27

1. DRD Title: NSSC IT Support Security Management Plan

2. DRD No.: 2.7-1 3. Data Type: 1 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: To provide Government documentation of the SP’S methodology for managing all aspects of information security, risk management and safeguards to ensure critical components and NASA IT systems associated with transformational and innovative proposals are implemented in accordance with NASA policies and procedures.

11. Distribution: NSSC Electronic Library (NSSC CIO, NSSC CO, NSSC COR, NSSC ACOR)

Initial Submission: 30 days after phase-in start if innovative and transformational projects are included in the offerors proposal. If there are no innovative and transformational projects included in the offerors proposal the IT Security Management plan shall be submitted with each innovation and transformational proposal.

Submission Frequency: Approved IT Support Security Management Plans shall be reviewed and updated annually

Format: Microsoft Office Word

Interrelationship:

PWS Section 2.7 Security Attachment I-8, IT Support Security Management Plan

Applicable Documents:

NPR 2810.1F, Security of Information and Information Systems NPR 1600.1A, NASA Security Program Procedural Requirements NFS 1804.470, Security Requirements for Unclassified Information Technology (IT) Resources NFS 1852.204-76, Security Requirements for Unclassified Information Technology (IT) Resources

Scope: The IT Support Security Plan provides an overview of the security requirements of IT systems and describes the implementation details of the management, operational, and technical security controls in place or planned, and responsibilities and expected behavior of all individuals who access the system

Contents: The NSSC IT Support Security Management Plan shall document the safeguards necessary to ensure sufficient availability, integrity, and confidentiality of that information accessed or managed within the systems and/or applications as well as key and media control. The NSSC IT Support Security Plan shall meet the requirements of the applicable documents in the references noted above and document how the SP

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-28 personnel will utilize, in a secure manner commensurate with the sensitivity of the information involved, those Federal computer systems and software applications managed by others. The Plan shall describe the SP’s processes for implementing information security including personnel background screening, personnel awareness and training, information protection and security incident response.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-29

1. DRD Title: Key Control and Media Control Reports

2. DRD No.: 2.7-2 3. Data Type: 3 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: The NSSC will use the Key Control and Media Control Reports to document lost media (e.g., key, badge, etc.) loss, and aid in the subsequent security investigation, risk remediation and property loss statement if required.

11. Distribution: NSSC Electronic Library (NSSC CO, NSSC COR, NSSC ACOR, and the NSSC Security Coordinator)

Initial Submission: First Incident by close of business (COB) the day after the discovery of loss.

Submission Frequency: The Service Provider shall provide a written report to the NSSC Security Coordinator by COB the day after the discovery of loss.

Format: Microsoft Word

Interrelationship:

PWS Section 2.7.1, Physical Security PWS Section 2.7.3, Key Control, Media Access and Protection

Applicable Documents:

NPR 1600.1A, NASA Security Program Procedural Requirements NPR 1600.4A, Identity and Credentialing Management NPR 1620.3B, Physical Security Requirements for NASA Facilities and Property NPR 2810.1F, Security of Information and Information Systems

Scope: The Key Control and Media Control Reports provides a security measure to account for physical security safeguards.

Content:

A. Access media control number;

B. Location(s) accessed by the person who lost the access media;

C. Date the access media was discovered missing;

D. Name of person who signed for the access media;

E. Immediate risks and mitigation; and F. Any other relevant detail.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-30

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-31

1. DRD Title: Safety and Health Incident (Anomaly) Reports

2. DRD No.: 2.8-1 3. Data Type: 3 4. OPR: NSSC

Administrative ☐

S&MA ☒

10. Description/Use: The NSSC will utilize the Safety and Health Incident (Anomaly) Report to capture and provide an initial description of the mishap or close call for documentation and for further investigative purposes.

11. Distribution: NSSC Electronic Library (NSSC CO, NSSC COR, NSSC ACOR, NSSC Safety Coordinator)

Initial Submission: After First Incident per the below submission frequency.

Submission Frequency: 24 hours post incident for a Class D Mishap or Close Call or within an hour for a Class A, B or C Mishap as defined within Section 1.2 of NPR 8621.1D, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping

Format: Microsoft Word

Interrelationship:

PWS Section 2.8, Safety and Occupational Health, Attachment I-09, Safety and Health Plan

Applicable Documents:

PWS 2.8, Safety and Occupational Health NPR 8621.1D, NASA Procedural Requirements for Mishap and Close Call Reporting, Investigating, and Recordkeeping NPR 8715.3B, NASA General Safety Program Requirements

Scope: SP initial sequence and reporting for mishap notification and subsequent for investigation purposes

Contents:

A Safety and Health Incident (Anomaly) Report shall be prepared and distributed as noted in the submission frequency section above and shall include but not be limited to:

- Person, Equipment or Systems involved;

- Nature and location of anomaly;

- Number, and, if possible, the names of employees involved and nature of injuries, if any;

- Date, time, probable cause of occurrence and events leading up to anomaly;

- Project, test, or operation involved; the nature and estimated dollar value of damage and estimated

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-32 time the project will be delayed;

- Eyewitness account of anomaly;

- Action to be taken with system after Anomaly Report is completed.

- Persons notified; and

- Photographs, if available.

Remarks: The Safety and Health Incident (Anomaly) Reports contain PII information and shall be stored and handled utilizing the requirements set forth within the Privacy Act of 1974 and NPD 1382.17K, NASA Privacy Policy. NASA policy is to: Protect all forms of controlled unclassified information (CUI), including personal information and to comply with Federal law and regulations governing management of all personal information collected, used, maintained, and disseminated by or on behalf of NASA in electronic or non-electronic form.

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-33

1. DRD Title: NSSC IT Support Disaster Recovery Plan (IT DRP)

2. DRD No.: 2.8-2 3. Data Type: 1 4. OPR: NSSC

Administrative ☒

S&MA ☐

on/Use: Description/Use: The NSSC utilizes the IT Support DRP as a management tool to provide an overview of the strategies, resources, and procedures required to recover from any disaster affecting information technology resources.

11. Distribution: NSSC Electronic Library (NSSC CIO)

Initial Submission: 30 days following the start of contract performance.

Submission Frequency: Shall be reviewed and updated annually.

Format: Microsoft Word

Interrelationship:

PWS Section 2.8.1, Disaster Recovery and Emergency Situations

Applicable Documents:

NSPLN-1280-0002, NSSC Service Recovery Plan NSBCP-1040-0001, NSSC Business Continuity Plan NPR 2810-1F, Security of Information and Information Systems NPR 2830.1A, NASA Enterprise Architecture Procedures

Scope: The recovery strategy for a disaster is dependent upon the systems and facilities that have been damaged or lost.. The Plan serves as a guide to pre-disaster preparedness, structured training, and post-disaster scrutiny of “start-to-finish performance” by all involved.

Contents: The IT Support DRP delivers a structured approach for response to unplanned incidents that threatens NSSC’s IT Support. The content of the IT Support DRP shall include at a minimum:

• Planning, Processes and Procedures

• Organization Roles and Responsibilities

• NSSC Disaster Declarations, Delegations, Delegations of Authority and Succession

• Disaster Recovery Training, Testing and Reporting

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-34

Attachment I-2 NTSS 80NSSC23R0001 Amendment 00002

I-2-35

1. DRD Title: Risk Management Plan

2. DRD No.: 2.9-1 3. Data Type: 1 4. OPR: NSSC

Administrative ☒

S&MA ☐

10. Description/Use: The report will be used as a management tool to help ensure the contracts operational effectiveness and efficiency.

11. Distribution: NSSC Electronic Library (NSSC COR, NSSC ACOR, NSSC CO, Delegates)

Initial Submission: 60 days following the start of contract performance.

Submission Frequency: Annually

Format: Microsoft Word/Converted into PDF for…