Attachment D2 Data Requirements List (Base).pdf

Attachment D-2

California Regional Center and Administrative and Technical Support Services (CATSS III)

Contract Data Requirements List

National Aeronautics and Space Administration Armstrong Flight Research Center

October 7, 2022

Attachment D-2 80AFRC22R0002

DOCUMENT CHANGE LOG

Revision Number Date Brief Summary of Changes Baseline 10/7/2022

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.

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

Transmittal

Data shall be transmitted to NASA by email or other electronic system (i.e. BOX, SharePoint, etc.) 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.

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.

CDRL/DRD MAINTENANCE PROCEDURES

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.

Contract Data Requirements List Table

DRD

No.

DRD

Type DRD Title OPR

1 1 Management Plan Procurement

2 1 Safety and Occupational Health and Environmental Plan

(SHEMP) (AFRC & ARC)

Safety & Mission Assurance (S&MA)

3a 3 Contractor Monthly Accident Report (AFRC) Safety & Mission Assurance (S&MA)

3b 3 Contractor Monthly Accident Report (ARC) Safety & Mission Assurance (S&MA)

4 3 Listing of Current Employees Procurement

5 1 Organizational Conflicts of Interest (OCI) Plan Procurement

6 1 Information Technology (IT) Security Management Plan Center Information Security Office (CISO)

7 3 Monthly Task Order Progress Reports Procurement

8 1 Property Management Plan Industrial Property Officer (IPO)

9 1 Diversity, Equity, Inclusion Plan Procurement

10 3 Contract Performance Self-Assessment Procurement

11 1 Contract Phase-Out Plan Procurement

Data Requirements Description (DRD)

1. DRD Title: Management Plan

2. DRD No.: DRD-01 3. Data Type: 1 4. OPR: Procurement

5. Solicitation No.: 80AFRC22R0002

6. Contract No.: TBD

7. Date Issued: January 3, 2022

8. Date Revised: 9. DRD Category:

Technical ☒Administrative ☐

S&MA ☐

10. Description/Use: The Management Plan will be used to document the Contractor’s overall and detailed planning and operations for satisfying the contract requirements.

11. Distribution: Contracting Officer (CO); Contracting Officer Representative (COR)

Initial Submission: With submission of Proposal; CO will retain the approved plan in the contract file.

Submission Frequency: To be updated as required, thereafter

Format: Contractor Format

Interrelationship: Performance Work Statement (PWS) Section 6.0

Applicable Documents: PWS

Scope: The Management Plan shall describe the contractor’s management approach, organization, and processes. It 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 PWS, as well as those systems and procedures that are to be set in place by the contractor to adhere to regulations and the requirements set forth in the solicitation.

Contents:

A. The overall management approach to satisfying the contract requirements, including at a minimum:

1. The program management functions;

2. The management policies and procedures;

3. The strategies and goals to provide effective and efficient implementation of the PWS;

4. Innovations and efficiencies to be gained through the proposed approach to manage the contract, including rationale to substantiate these innovations and efficiencies;

5. Methods and techniques to be used in planning, scheduling, integrating, processing, controlling, and completing the PWS requirements. Include any other methods and techniques the Contractor feels is critical to successful performance of contract requirements;

6. The methods to supervise, support, mentor, and verify the successful performance of employees are geographically distributed, both at Government and non-Government locations.

B. A description of the organization including:

1. Description of proposed organizational structure;

2. An organization chart identifying roles of all organizational elements and reporting relationships;

3. Clear internal and external lines of authority;

4. Outline procedures to ensure effective communication and collaboration across the organization;

5. The relationship of the local contract management to the parent company, as well as the management of any proposed subcontractors, team members, or join venture partners;

6. Associations with other companies or organizations utilized to provide effective and efficient implementation of the PWS;

7. The Contractor’s relationship with other NASA contractors;

8. The management functions, roles, and responsibilities, and the method for integrating operation plans for all primary functional work areas;

9. The Contractor’s management interface with NASA.

C. Include the following information for the Contractor’s Key Personnel:

1. Resumes of Key Personnel;

2. The level of commitment of any Key Personnel who will not be 100% dedicated to this contract.

D. A description of how each function will be filled, including:

1. Recruitment, retention, and employment methods and policies;

2. Staffing strategies;

3. The minimum qualification standards to satisfy the Skill Labor Category guidelines;

4. Strategy to ensure personnel will maintain the minimum qualifications standards described in the Skill

Labor Category guidelines;

5. Approach to providing flexible workforce planning. Include discussion on recruiting, retention of personnel, and effects on management, subcontractors, continuity and quality of services, and other factors resulting from changes in staffing levels.

E. The overall management approach to creating an effective and efficient interface to the Government concerning the implementation of the PWS requirements and communication of activities related to these efforts.

F. The proposed quality control system, including:

1. A Performance Evaluation Summary the Contractor will use to ensure excellent services are provided for each PWS element;

2. Methods to ensure timely delivery of quality services;

3. Procedures, techniques, and tracking for early identification of potential problems, implementation of preventative action, and proactive and timely resolution.

G. The timekeeping process and procedures, including:

1. Management oversight of employee daily work hours, ensuring compliance with customer requirements;

2. How deviations of a person’s prescribed daily schedule are communicated to the NASA organizational representative;

3. How source data is validated;

4. Methods to validate timely and accurate recording, including time for remote or teleworking employees;

5. Approval process for employee non-productive hours (sick leave, vacation leave, or other administrative leave).

Remarks: N/A

Maintenance: Changes shall be issued by complete reissue

Data Requirements Description (DRD)

1. DRD Title: Safety and Occupational Health and Environmental Plan (SHEMP) (AFRC & ARC)

2. DRD No.: DRD-02 3. Data Type: 1 4. OPR: Safety & Mission Assurance Office

Technical ☐Administrative ☐

S&MA ☒

10. Description/Use: Ensure safety and occupational health of Contractor, the exposed public, NASA employees, associates, and property in performance of the contract throughout the duration of the contract.

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR), Safety and Mission Assurance (S&MA) Office

Initial Submission: First Day of Contract Phase-in

Submission Frequency: S&MA Approved Plan will become an Attachment to the contract

Format: Microsoft Word

Interrelationship: N/A

Applicable Documents: FAR 52.236-13 and Alt I, NFS 1852-223-70

Scope: Establishes Center Specific Safety, Occupational Health, and Environmental Plan Note: Plan must address both AFRC and ARC

Contents:

A. In accordance with the contract, the Contractor shall maintain a Safety and Health Plan detailing discussion of the policies, procedures, and techniques that will be used to ensure the safety and occupational health of Contractor employees over the duration of the contract.

B. The Contractor’s Safety and Health Plan shall address how the contract requirements will be met and shall address how the Contractor shall comply with all applicable federal, NASA/AFRC, Edwards Air Force Base, State and Local occupational safety and health requirements and standards

C. The Safety and Health Plan shall include at a minimum:

1. Title, contract number, preparer, approver(s), NASA concurrence signatures, revision with date, page numbers, index

2. Contract and subcontract management, including requirement review and execution of Safety and Health requirements.

3. Organizational chart showing responsibilities and authorizations as well as limits to authority, if any.

4. Identification and tailoring, if any, of policies, procedures, and techniques that will be used to ensure the safety and occupational health of Contractor employees, as well as public, NASA employees, associates, property, and other contractors peripherally associated with Contractor performance of contract tasks.

5. Periodic checks, audits, training, or other means to assure safety of all working conditions throughout the performance of the contract.

6. Role of Contractor supervision in oversight or directly assuring the safe execution of contract tasks.

7. Describing alternative approaches for compliance to contract requirements regarding Safety and

Occupational Health, as authorized only by written approval of the Contracting Officer before implementation.

8. Description for what the Contractor shall do to effect accident prevention including method to identify risks, hazards and their appropriate mitigations, eliminate injuries, damage to property, close calls, immediate reporting of mishaps, and loss of time accidents and monthly report content to CO and Safety Office.

D. The Safety and Health Plan and its revisions may be transmitted electronically, Word format for editing purposes and PDF for signed, approved Plans, unless the COR requires otherwise. Government will provide email addresses. Submit the Safety & Health Plan and revisions via email with subject line leading with CATSS DRD-02 Safety and Occupational Health and Environmental Plan (SHEMP)” to:

1. Contracting Officer

2. Contracting Officer’s Representative

3. Safety & Mission Assurance Office

Note: The Contractor can expect at least 10 working days for review to conclude in either approval or disapproval.

AFRC and ARC reserve the right to disapprove the Safety and Health Plan(s) and/or associated processes utilized in performance of the contract, if either fails to comply with requirements or exhibits significant adverse trends in product/service quality, conflicts with, or does not otherwise conform with all applicable federal, NASA/AFRC, NASA/ARC, Edwards Air Force Base, Moffett Air Field, State and Local occupational safety and health requirements and standards or can cause/has caused safety issues or injury, death, damage, or loss of resources to public or NASA or Contractor including employees. The Contractor shall furnish all resources to ensure continuous implementation of the Safety and Health Plan as approved.

Data Requirements Description (DRD)

1. DRD Title: Contractor Monthly Accident Report (AFRC)

2. DRD No.: DRD-03a (AFRC) 3. Data Type: 3 4. OPR: Safety and Mission

S&MA ☒

10. Description/Use: Establishes monthly compliance for Contractors providing support to NASA

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR), Safety and Mission Assurance (S&MA) Office

Initial Submission: 30 days after contract award

Submission Frequency: Monthly submission due the 10th of every month

Format: AFRC Form 80034

Interrelationship: PWS Section 5.1

Applicable Documents: NPR 8715.3C, NASA General Safety Program Requirements, PWS

Scope: Provide safety reporting metrics to the Center

Contents:

a. Average number of employees for the month

b. Number of work hours worked for the month

c. Number of injuries for the month

d. Number of lost time injuries for the month

e. Lost time days for the month

f. Total work hours worked year-to-date

g. Total lost time occurrences year-to-date

h. Total lost time days year-to-date

Maintenance: New form shall be submitted each month. File shall be named in the following format:

YEARMO_Monthly_Accident_Report_CATSS (e.g. 202211_Monthly_Accident_Report_CATSS)

Data Requirements Description (DRD)

1. DRD Title: Contractor Monthly Accident Report (ARC)

2. DRD No.: DRD-03b (ARC) 3. Data Type: 3 4. OPR: Safety and Mission

S&MA ☒

10. Description/Use: Establishes monthly compliance for Contractors providing support to NASA

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR), Safety and Mission Assurance (S&MA) Office (via database)

Initial Submission: 30 days after contract award

Submission Frequency: Monthly submission due the 15th of every month

Format: Contractor Monthly Accident Report (CMAR) web-based database system.

Interrelationship: PWS Section 5.1

Applicable Documents: NPR 8715.3C, NASA General Safety Program Requirements, PWS

Scope: Provide safety reporting metrics to the Center

Contents:

a. Average number of employees for the month

b. Number of work hours worked for the month

c. Number of injuries for the month

d. Number of lost time injuries for the month

e. Lost time days for the month

f. Total work hours worked year-to-date

g. Total lost time occurrences year-to-date

h. Total lost time days year-to-date

Maintenance: New form shall be submitted each month. File shall be submitted in CMAR database.

Data Requirements Description (DRD)

1. DRD Title: Listing of Current Employees

2. DRD No.: DRD-04 3. Data Type: 3 4. OPR: Procurement

Technical ☐Administrative ☒

S&MA ☐

10. Description/Use: This report shall be used to list all contractor personnel assigned to the contract with their assigned functional area

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR)

Initial Submission: First day of contract performance

Submission Frequency: To be updated when changes occur to listing

Format: Excel Spreadsheet

Interrelationship: Performance Work Statement (PWS) Section 5.1

Applicable Documents:

Scope: The employee listing provides a listing of all contractor employees working on this contract and their designated locations at the Center.

Contents:

a. Employee name

b. Employee phone number

c. Employee location

d. Employee Functional Area

e. Position Title, ate and Associated Task Order Number

f. Employee start date

g. NASA Primary and Alternate Task Monitor

h. Changes table

Data Requirements Description (DRD)

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

2. DRD No.: DRD-05 3. Data Type: 1 4.OPR: Procurement

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: Contracting Officer (CO), Contracting Officer’s Representative (COR)

Initial Submission: Plan shall be submitted on the first day of the contract phase-in

Submission Frequency: As needed

Format: Contractor’s format is acceptable. The electronic format shall be compatible with 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.

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 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 at this time, if applicable. Provide a list of all of the prime’s and subcontractor’s NASA contracts and subcontracts, which would provide the CO a better understanding of other NASA work performed 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. The Plan demonstrates an understanding of the definition of “sensitive information”.

14. 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 mandatory protections of sensitive information.

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

16. 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.)

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.

Data Requirements Description (DRD)

1. DRD Title: Information Technology (IT) Security Management Plan

2. DRD No.: DRD-06 3. Data Type: 1 4. OPR: Center Information Security Office

S&MA ☐

10. Description/Use: Ensure compliance to Information Technology (IT) Security as defined and required by NASA and the United States Government is managed by Contractor and its agents, e.g. employees and subcontractors.

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR), Center Information Security Officer (CISO)

Initial Submission: First day of contract phase-in. CISO approved plan will become a contract attachment.

Submission Frequency: As necessary

Format: NASA Template

Applicable Documents: NFS 1852.204-76, NPR 2810.1A - Security of Information Technology; AFPD-2800.2-001 - Managing Information Technology, NIST SP 800-64 – Security Considerations in Information System Development Life Cycle, OMB Circular A-130, Appendix III - Security of Federal Automated Information Resources

Scope: In accordance with NFS 1852.204-76 Security Requirements for Unclassified Information Technology Resources, the Contractor shall develop and deliver an IT Security Management Plan.

Contents:

A. In accordance with the contract the Contractor shall maintain an IT Security Management Plan describing and addressing how the Contractor will manage personnel and processes associated with IT Security requirements related to the performance of the contract.

B. The IT Security Management Plan shall address how the contract requirements will be met and shall address at a minimum:

1. Title, contract number, preparer, NASA concurrence signatures, approver(s), revision with date, page numbers, table of contents, list of applicable definitions, revision history, introduction, scope.

2. Contract and subcontract management, including requirement review and execution.

3. Supplier control - flow down of contract requirements to subcontractors/suppliers, with necessary means to assure compliance over the duration of the contract.

4. Compliance with AFRC and NASA Information Technology related purchase supply chain risk assessment process.

5. Description of the method to periodically demonstrate that the Contractor IT Security system, strategy and measures are effective and compliant with contract requirements.

6. Employee security clearance process, assurance for meeting Public Trust Position (ref SF Form 85).

7. Compliance with NASA required annual, role-based and employee remedial training requirements.

8. Access and control of NASA and Government electronic assets, data bases, websites, email system, and accounts.

9. Description of how the Contractor shall ensure currency and effectiveness of its IT Security system. (The Contractor shall, anticipate and upon discovery, identify conflicts with contract requirements, then immediately provide recommended solutions in writing to the COR and IT Security Office. Recommendations can include suggestions to improve the AFRC governing system, processes, and policies).

10. Description of resolving a discrepancy/issue, the strategy for timely implementation for effective corrective actions coordinated with NASA and report method to the COR, Contractor staff and AFC IT Security Office (typically the TOM).

11. Description of data management strategy; contractor shall comply with all NASA data being stored and managed using AFRC or NASA authorized services.

12. Shall document compliance with NASA Policy regarding use of unauthorized devices, e.g. personal computers, cell phones, watches, scanners, USB or other connecting devices, video/cameras, memory devices, broadcast, recording, and “cloud” products and privately-owned software applications.

13. Reference (NPR 2810.1, Security of Information Technology) - The Contractor shall employ, and demonstrate compliance with the following Federal Security documents:

a. NIST 800 series documents

b. Federal Information Security Management Act (FISMA)

c. FIPS 200 Minimum Security Requirements for Federal Information and Information systems

d. FIPS 199, Standards for Security Categorization of Federal Information and Information systems

14. Handling of customer supplied material, product, and equipment.

15. Description of how the approved IT Security Management Plan and all revisions are fully implemented upon approval and will serve as a focal point for IT Security related matters to the COR and AFRC IT Security Office.

C. Description of how the Contractor shall support the Government audit/surveillance of Contractor plans, procedures and processes when deemed necessary by the Government.

D. The IT Security Management Plan shall describe how the Contractor shall manage and provide a documented IT Security and related records system for all tasks defined in contract subordinate to the AFRC IT Security system, processes, policies, and management. (The document(s), processes, and procedures including revisions are subject to AFRC approval/acceptance prior to start of work or implementation.

E. The IT Security Management Plan may be transmitted electronically, PDF (signed) and Word formats, unless COR requires otherwise. Government will provide email addresses. Submit the IT Security Management Plan and revisions via encrypted email to:

1. Contracting Officer (CO)

2. Contracting Officer’s Representative (COR)

3. IT Security Office, Code 640

Note: The Contractor can expect at least 10 business days for review to conclude in either approval or rejection.

AFRC and ARC reserve the right to reject or disapprove the IT Security Management Plan and/or associated processes utilized in performance of the contract, if either fails to comply with requirements or exhibits significant adverse trends in product/service quality, conflicts with, or does not otherwise conform with contract, compromises security, degrades protection (or results in loss) of intellectual property, or can cause/has caused safety issues or injury, death, damage, or loss of resources to public or NASA or Contractor including employees. The Contractor shall furnish all resources to ensure continuous implementation of the IT Security Management Plan as approved.

Maintenance: Changes shall be incorporated by complete reissue.

Data Requirements Description (DRD)

1. DRD Title: Monthly Task Order Progress Reports

2. DRD No.: DRD-07 3. Data Type: 3 4. OPR: Procurement

S&MA ☐

10. Description/Use: Provides the information required pursuant to NFS 1852.216-80 Task Ordering Procedure, Alt I

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR), Resource Analyst (RA)

Initial Submission: 30 days after performance period begins

Submission Frequency: Due the 10th working day of each month

Format: Excel Spreadsheet

Interrelationship: N/A

Applicable Documents: NFS 1852.216-80 Task Ordering Procedure, Alt I

Scope: In accordance with NFS 1852.216-80 Task Ordering Procedure, Alt I, the Contractor shall prepare and submit monthly task order progress reports.

Contents:

At a minimum, the reports shall contain the following information:

1. Contract number, task order number, and date of the order.

2. Task ceiling price.

3. Cost and hours incurred to date for each issued task.

4. Costs and hours estimated to complete each issued task.

5. Significant issues/problems associated with a task.

6. Cost summary of the status of all tasks issued under the contract.

Maintenance: The deliverable should be added to monthly.

Data Requirements Description (DRD)

1. DRD Title: Property Management Plan

2. DRD No.: DRD-08 3. Data Type: 1 4. OPR: Industrial Property Officer

S&MA ☐

10. Description/Use: Identify and evaluate the industry leading or voluntary consensus standards, and/or the industry leading practices, that the Contractor intends to employ for the management of Government property.

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR), Center Industrial Property Officer (IPO)

Initial Submission: First day of contract phase-in, IPO approved plan will become a contract attachment

Submission Frequency: As necessary

Format: The plan shall be prepared in accordance with FAR 52.245-1 -Government Property, FAR 45.105 – Contractor’s Property Management System Compliance, and NFS 1852.245-80 – Government Property Management Information, in the case where Government Furnished Property (GFP) as outlined in the cited FAR and NFS requirements.

Interrelationship: N/A

Applicable Documents: FAR 52.245-1 Government Property, FAR 45.105 Contractor Property Management System Compliance, and NFS 1852.245-80 Government Property Management Information.

Scope: To ensure contractor is compliant with all Government Furnished Property requirements

Contents:

The plan should include the contractor’s proposed systems, standards, and practices for the management of Government property.

Maintenance: Changes shall be incorporated by complete reissue of the deliverable.

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

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

7. Date Issued: April 4, 2022 8. Date Revised: 9. DRD Category:

Technical ☐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: Distribution shall be as instructed by the Contracting Officer.

Initial Submission: Plan shall be submitted within 30 days after contract award.

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

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.

Data Requirements Description (DRD)

1. DRD Title: Contract Performance Self-Assessment

2. DRD No.: DRD-10 3. Data Type: 3 4. OPR: Procurement

S&MA ☐

10. Description/Use: To facilitate in the assistance of NASA personnel in completing annual contract performance assessment for the Contractor Performance Assessment Reports Systems (CPARS)

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR)

Initial Submission: Two (2) weeks after completion of the contract’s basic period of performance

Submission Frequency: Annually, two (2) weeks after completion of the contract’s period of performance, either basic period, or exercised option periods.

Format: Contractor Format

Interrelationship: N/A

Applicable Documents: FAR 42.1502(b)

Scope: The contractor shall provide a self-assessment of their performance of the requirements of the PWS for the 12-month evaluation period.

Contents:

The self-assessment shall include a summary of significant accomplishments and evaluation of the following areas of contract performance:

a. Quality of Services performed

b. Schedule, including any variances, if applicable

c. Cost Control, including any variances, if applicable

d. Management

e. Utilization of Small Business, if applicable

f. Regulatory Compliance

g. Other Areas for Consideration

Remarks: The contractor’s self-assessment will be just one resource used by Government personnel to provide an assessment of the contractor’s performance. The Government may utilize portions of the self-assessment in the CPARS evaluation or may not use any portion of the contractor’s self-assessment.

Maintenance: N/A

Data Requirements Description (DRD)

1. DRD Title: Contract Phase-Out Plan

2. DRD No.: DRD-11 3. Data Type: 1 4. OPR: Procurement

7. Date Issued: April 8, 2022

S&MA ☐

10. Description/Use: Provides the documented approach to phase-out the contract to ensure orderly transfer of duties and records to the incoming contractor.

11. Distribution: Contracting Officer (CO), Contracting Officer’s Representative (COR)

Initial Submission: 30 days after the fourth year performance period begins

Submission Frequency: One time submittal

Format: Contractor Format

Interrelationship: N/A

Applicable Documents: N/A

Scope: The phase-out plan shall address the plan and approach to ensure complete and orderly transfer of duties and records to the incoming contractor.

Contents:

At a minimum, the plan shall thoroughly address the plan and approach to ensure a complete and orderly transfer of duties and records to the incoming contractor. The plan shall address issues pertinent to the continuation of operations for all areas of responsibility under the contract. Additionally, the plan shall address any collective bargaining agreements (CBA), if applicable, and timing and information that will be provided regarding the incumbent’s non-key personnel employees to the incoming contractor (i.e., employee name, position title, functional area covered).

Maintenance: One time submittal