80KSC22NCSDRFP Attachments Portfolio.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

Attachment D-1A, Core Services Estimated Annual Banding Levels 80KSC022NCSDRFP

PWS 4.1.10 NASA

Style and Graphics

Standards: Estimated

Annual Range

(Low/High # of products) Contracts Name/Number Date of Transition

PWS 4.2.1.1 Internal

Communications:

Estimated Annual Range

(Low/High # of products)

20-50 Civil Servants/CATSS Follow-on

- TBD

6/1/2023 24-75 Civil Servant N/A

200-250

Civil servants and contractors

(FILMSS II TBD, COMIT

NNJ16JA52B)

FILMSS II - est 5/1/2024;

COMIT 3/1/2023

150-300

Civil Servants/COMIT

NNJ16JA52B

3/1/2023

260-520 TIALS NNC16CA11C 3/1/2023 104-260

TIALS NNC16CA11C and

Civil Servants

260-520

GSMO-2 NNG17HP02C,

PAAC V 80GSFC20D0001

GSMO-2 6/1/2023; PAAC

V 3/1/2023

700-1000 TRAX 80GSFC17C0010 3/1/2023

500-900 COMIT NNJ16JA52B 3/1/2023 600 - 900 COMIT NNJ16JA52B 3/1/2023

260-520

KIAC 80KSC017C0011 6/1/2023 700-1000 KISS IV 80KSC017D0003 6/1/2023

75-125 LAMPSII 80LARC18C0002 6/1/2023 200-400

LAMPSII 80LARC18C0002;

STARSS NNL16AA05C;

6/1/2023

144-192 SRACES 80MSFC21D0011 10/1/2025 480-700 SRACES 80MSFC21D0011 10/1/2025

52-260 SACOM NNS15AA01C 10/1/2023 52-520 SACOM NNS15AA01C 10/1/2023

N/A Civil Servant N/A N/A Civil Servant/COMIT

PWS 4.2.1.5 Public

Inquiry Responses :

Estimated Annual Range

(Low/High # of products)

PWS 4.2.2.3

Speakers Bureau:

Estimated Annual

Range (Low/High # of products)

24-100 Civil Servants N/A 1-12. Civil Servants N/A

250-500 Civil Servants N/A 75-125 FILMSS II TBD 5/1/2024

1000-1300 TIALS NNC16CA11C 3/1/2023 200-500 TIALS NNC16CA11C 3/1/2023

9600-12000 Civil Servants N/A 72-120 Civil Servants N/A

100-300 Civil Servants N/A 12-60. Civil Servants N/A

104-260

KISS IV 80KSC017D0003 6/1/2023 300-400 KISS IV 80KSC017D0003 6/1/2023

5-15 Civil Servants N/A 50-150

LAMPSII 80LARC18C0002; STARSS

NNL16AA05C

6/1/2023

144-192 SRACES 80MSFC21D0011 10/1/2025 36-168 SRACES 80MSFC21D0011 10/1/2025

12-24 SACOM NNS15AA01C 10/1/2023 52-520 SACOM NNS15AA01C 10/1/2023

120,000-240,012 80HQTR19C0025 3/1/2023 65-250 Civil Servant N/A

PWS 4.3.4 Media and Social Media:

Estimated Annual

Range (Low/High # of products)

Contracts Name/Number

Date of

Transition

PWS 4.4 History and

Archives WYE Annual

Equivalent

225-450 CATSS 6/1/2023 1 Historian CATSS 6/1/2023

2,310-6,570 COMIT NNJ16JA52B 3/1/2023 .8 Archivist Contract FILMSS II TBD 5/1/2024

52-260

TIALS NNC16CA11C, PACE

80TECH21DA001

3/1/2023;

81/2023

1 Historian (currently an

Archivist)

TIALS NNC16CA11C 3/1/2023

5055-5865

GSMO II NNG17HP02C, PAAC

V 80GSFC20D000, SESDA IV

80GSFC17C0003

3/1/2023 N/A Civil Servant N/A

12-6600 Civil Servant and COMIT

3/1/2023 2 Historians COMIT NNJ16JA52B 3/1/2023

5000-7000

Civil Servant, KIAC

80KSC017C0011, KISS IV

80KSC017D0003

6/1/2023 .5 Archivist KIAC 80KSC017C0011 6/1/2023

500-1200

LAMPSII 80LARC18C0002;

NIA NNL13AA08B & NIA

80LARC17C0004

6/1/2023 N/A Civil Servant N/A

590-5950 SRACES 80MSFC21D0011 10/1/2025 1 Archivist SRACES 80MSFC21D0011 10/1/2025

12-1040 SACOM NNS15AA01C 10/1/2023 1 Archivist SACOM NNS15AA01C 10/1/2023

0-68 Civil Servant and COMIT

3/1/2023 2 Archivists , 1 Editor

2 - Archivists HOSS 80HQTR18C0002, 1 editor 80HQTR18A0003

NCS Draft RFP 80KSC22NCSDRFP ATTACHMENT D-2

NASA COMMUNICATION SERVICES (NCS) CONTRACT

ATTACHMENT D-2

CONTRACT DATA REQUIREMENTS LIST

DOCUMENT CHANGE LOG

DRD

No.

DRD Title Revision Date

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 be compatible with Microsoft Office. The preferred native formats include Microsoft Word, Excel, or PowerPoint, as appropriate. The report shall be uploaded the Government-provided Contract Management

Portal (iSite) – Performance Work Statement (PWS) 3.1.19

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

Transmittal

Data shall be transmitted to NASA electronically via the iSiTE system

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)

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

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

No.

Type

DRD Title OPR

001-

QAM

3 Quarterly Headcount Report

Office of

Procurement

(OP)

002-

3 MSFC – On-Site Employee Location Listing OP

003-

OAM

1 Management Plan

Office of

Communications

(OCOMM)

004-

1 Contracts Records Close-Out Plan OP

005-

YTA

1 File Plan OCOMM

006-

YAM

1 Information Technology (IT) Security Management Plan

Office of the

Chief

Information

Officer (OCIO)

007-

MAM

2 Monthly Banding Levels Progress Report OCOMM

008-

MSA

3 Monthly Progress Report OCOMM

009-

MSA

3 On-Site Mishap and Safety Statistics Reports

Office of Safety and Mission

Assurance

(OSMA)

010-IAM 1 Organizational Conflict of Interest (OCI) Plan OP

011-

2 Performance Assessment report OCOMM

012-

1 Phase-Out Plan OCOMM

013-

1 Records Management Program plan OCOMM

014-

2 Re-Procuremnet Data Package OP

015-YSA 1 Safety and Health (S&H) Plan OSMA

016-IAM 3 Environmental Compliance Reports OCOMM

017-IAM 1 Government Property Management Plan (PMP) OCOMM

018-

3 Diversity, Equity, and Inclusion (DEI) Plan OP

019-

KSC – Quarterly Summary of 3rd Step Labor Grievances and

Arbitrations Report

Office of the

Chief Human

Capital Officer

(OCHCO)

020-IAM 3 Advance Notification of Workforce Reductions Report OCHCO

1. DRD Title: Quarterly Headcount Report

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

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: TBD 8. Date Revised: 9. DRD Category:

Technical ☐

Administrative ☒

S&MA ☐

10. Description/Use: To provide the Government with on-site and off-site working data, which is used for workforce reporting requirements

11. Distribution:

CO KSC; CO JSC; CO MSFC; NCS Contracting Officer’s Representatives (COR), Initial Submission: See “Submission Frequency” below.

Submission Frequency: The Contractor shall provide this report no later than 10 calendar days after the close of each reporting period which ends March 31st, June 30th, September

30th, and December 31st. In addition, if deemed necessary by the Contracting Officer, the

Contractor shall submit the data package at times other than stated.

Format:

Refer to Electronic Format instruction

Interrelationship: PWS Para. 3.2.2 (i)

Applicable Documents: N/A

Scope: The reports shall be submitted as shown below.

Report 1: Quarterly Contractor Workforce Report by Sub-Contractor Name by NASA Center

Report 2: Quarterly Contractor Workforce Report by Bargaining Unit

Report 3: A complete organizational chart including all employees by labor classification and

PWS. Contractor format is acceptable.

Definition of Terms

a) On-site – Number of contractor personnel occupying physical space at a NASA Center

b) Off-site – Number and corresponding Zip Code of contractor personnel physically located outside of NASA Center property.

c) Displaced – Number of contractor personnel who would normally occupy physical space on NASA Center (as defined above) but who are located outside of NASA Center (as defined above) due to non-availability of space.

d) Others Off-site – Number of contractor personnel who are intentionally, physically located outside of NASA Center (as defined above).

e) Subcontractors – Number of subcontractor personnel occupying physical space on NASA

Center (as defined above). Include the subcontractor name and a brief description/title of the effort.

Contents: N/A

Remarks: –

Maintenance: N/A

REPORT 1: QUARTERLY CONTRACTOR WORKFORCE REPORT BY

SUBCONTRACTOR

Contract: XXXXXXX

Sample Report for Quarter X – Period Ending XX/XX/XXXX

NASA Center: XXXXXXX

PERSONNEL ON-SITE OFF-SITE

DISPLACED

OFF-SITE

OTHER

TOTAL

TOTAL HEADCOUNT T=A+B T=A+B T=A+B T=A+B

CONTRACTOR HEADCOUNT A A A A

SUBCONTRACTOR

HEADCOUNT

(List each Subcontractor separately)

B

REPORT 2: QUARTERLY CONTRACTOR WORKFORCE REPORT BY

BARGAINING UNIT

Contract: XXXXXXX

Sample Report for Quarter X – Period Ending XX/XX/XXXX

PERSONNEL ON-SITE OFF-SITE TOTAL

TOTAL HEADCOUNT T=A+B T=A+B T=A+B

NON-UNION HEADCOUNT A A A

UNION-REPRESENTATED

HEADCOUNT

B = Sum of

Below

B = Sum of Below B = Sum of Below

BARGAINING UNIT 1 BU1 BU1 BU1

BARGAINING UNIT 2 BU2 BU2 BU2

BARGAINING UNIT 3 BU3 BU3 BU3

BARGAINING UNIT 4 BU4 BU4 BU4

BARGAINING UNIT 5 BU5 BU5 BU5

1. DRD Title: MSFC – On-Site Employee Location Listing

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

5. Solicitation No.: (Insert solicitation number)

7. Date Issued: TBD

8. Date Revised: 9. DRD Category:

10. Description/Use: To assist Marshall Space Flight Center (MSFC) in conducting contractor floor checks.

CO KSC; CO JSC; CO MSFC; NCS COR

Initial Submission: Due within 15 calendar days after contract performance starts.

Submission Frequency: Due quarterly based on the Government fiscal year: Quarter 1 ends December 31st, Quarter

2 ends March 31st, Quarter 3 ends June 30th, Quarter 4 ends September 30th. Reports are due within 15 calendar days of the end of each quarter.

Format: Refer to Electronic Format instruction

Interrelationship: PWS Para. 3.1.20 €

Applicable Documents:

MPR 3200.1 Onsite Location or Relocation of Contractor or Other Government Agency Personnel at MSFC

MPR 8812.2 MSFC Facility Utilization

NPR 8800.15 Real Estate Management Program

Scope: The On-Site Employee Listing shall provide MSFC with a list of all on-site contractor employees (including sub-contractor employees) working under this contract and their designated locations as required in MPR 3200.1, MPR 8812.2, and NPR 8800.15.

Contents: The On-Site Employee Location Listing shall include the following information for each employee:

employee’s name, position, location (building/room number), shift assignment, supervisor’s name, and supervisor’s location (building/room number).

Remarks:

1. DRD Title: Management Plan

2. DRD No.: 003-OAM 3. Data Type: 1 4. OPR: OCOMM

10. Description/Use: To provide a description of the Contractor's overall management system, organization and to provide insight for accomplishing the contract requirements.

10. Distribution:

Initial Submission: No later than 30 calendar days after the effective date of phase-in purchase order.

Submission Frequency: Revise as required

Interrelationship: PWS Para. 3.1.20(a)

Scope: The Management Plan describes the Contractor's management and operational approach for accomplishing the requirements set forth in the contract (e.g., managing and controlling project tasks, management interfaces). The plan shall be in such detail as necessary to convey the Contractor's internal procedures.

Contents: At a minimum, the plan shall include:

a. A description of the Contractor's management concepts, plans, project management approach; organizational approach/supervisory structure (to include connections or associations with divisional organizations, subcontractors, and/or other organizational elements); and planned communication channels/proposed interfaces between the Contractor, Subcontractors, teammates, and the Government (including support service contractors).

This shall include descriptions, flow charts, authority channels (including local level autonomy), schedules, and how the PWS maps to its organization and other documentation necessary to give a comprehensive plan. The plan shall be in such detail as necessary to convey the Contractor's internal procedures.

b. The Contractor's approach for risk assessment and resolution in managing the NCS effort, to include the

Contractor's approach for maintaining schedules; providing early notification to the Government of potential problems; and utilization of management metrics to track progress and trends, to provide deliverables on time, and to maintain ongoing operations in an effective manner.

c. The Contractor's approach to providing complete and timely responses to work order requests and/or indefinite-delivery indefinite-quantity (IDIQ) task order requests.

d. A detailed description of the Contractor's approach to accomplishing each Performance Work Statement (PWS) requirement, down to the third level Work Breakdown Structure (WBS).

e. A description of the Contractor's quality and/or control system(s) to be used in planning, scheduling, integrating, controlling, and successfully completing all PWS requirements.

f. Approach to continuous improvement and innovation.

g. Approach to maintaining flexibility and responsiveness to changing work volume and priorities to include the approach to providing responsive support to multiple customers while balancing customer priorities.

h. Approach to accommodate short notice/quick turn-around requirements.

The approved Management Plan will be incorporated into the contract.

Maintenance: Changes shall be incorporated as required by change page(s) or complete reissue. Changes shall be identified with revision marks.

1. DRD Title: Contract Records Close-Out Plan

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

10. Description/Use: To determine the amount of Government-owned records at each NASA location that will be turned over to the follow-on contract or stored at the NASA Archives.

Initial Submission: The Contractor shall develop a Contract Records Close-Out Plan for each location and submit the plans no later than 120 calendar days prior to the end of the contract, designating the Plans as follows:

- AFRC = D1-AFRC - JSC = D1-JSC

- ARC = D1-ARC - KSC = D1-KSC

- GRC = D1-GRC - LaRC = D1-LaRC

- GSFC = D1-GSFC - MSFC = D1-MSFC

- HQ = D1-HQ - SSC = D1-SSC

Example: Contract Records Close-Out Plan for

Kennedy Space Center (D1-KSC)

Submission Frequency: N/A

Format: Refer to Electronic Format instruction. The Contractor shall submit electronic versions using Microsoft

Excel.

Interrelationship: PWS Para. 3.4 (b) (1); KSC 52.245-90

a. NASA Records Management Program Requirements, NPR 1441.1 (latest version)

b. NASA Record Retention Schedules, NRRS 1441.1 (latest version)

Scope: The Plan shall provide a complete and final record inventory at contract close-out.

Contents: The Contractor shall submit a final inventory of records with volumes updated. The volumes shall be listed in megabytes for records in electronic formats, and in cubic feet for hard copy records. The inventory shall include sufficient technical documentation of all electronic records to permit the agency access and use. The inventory shall include sufficient details and locations documentation of all hard-copy records to permit the Government access and use.

The Contractor shall notify the location’s Records Manager the Plan has been uploaded. After approval of the submitted, modified, or updated Plan, the Contractor will work with each location’s Records Manager to determine where the approved Plan will reside.

Each locations Records Manager will serve as the OPR for their location.

The Contractor shall turn over inactive records to each location’s Records Manager and transition all active records to the next Contractor by the end of the Contract.

1. DRD Title: File Plan

2. DRD No.: 005-YTA 3. Data Type: 1 4. OPR: OCOMM

7. Date Issued: TBD 8. Date Revised: 9. DRD Category:

Technical ☒

Administrative ☐

10. Description/Use: To identify all NASA records being generated in the performance of the contract.

Initial Submission: The Contractor shall submit an initial location specific File Plan to each location’s Records

Manager no later than 120 calendar days after contract start, designating the Plans as follows:

- AFRC = D1-AFRC - JSC = D1-JSC

- ARC = D1-ARC - KSC = D1-KSC

- GRC = D1-GRC - LaRC = D1-LaRC

- GSFC = D1-GSFC - MSFC = D1-MSFC

- HQ = D1-HQ - SSC = D1-SSC

Example: File Plan for

Kennedy Space Center (D1-KSC)

Submission Frequency: The Contractor shall maintain and update each location’s File Plan in accordance with the

Applicable Documents referenced below. The revised plan shall be submitted by December 31st of each year.

Interrelationship: PWS Para. 3.4 b 2

a. NASA Records Management, NASA Policy Directive (NPD) 1440.6 (latest version)

b. NASA Records Management Program Requirements, NASA Procedural Requirement (NPR) 1441.1 (latest version)

c. NASA Record Retention Schedules, NRRS 1441.1 (latest version)

d. NASA Export Control Program, NPD 2190.1 (latest version)

Center Specific Applicable Documents:

a. KSC Records Management, KSC NPR (KNPR) 1440.6 (latest version)

Scope: The File Plan shall identify all NASA records being generated in the performance of the contract and shall include code number, the description of NASA records maintained, the records disposition, and the authority per NPR

1441.1.

a. Code#: NRRS 1441.1.

b. Record Title: Record Series description, a description of the record and its function.

c. Office of Record: Office responsible for retiring the record at the end of lifecycle.

d. Location: Physical location of records.

e. Retention/Disposition: Period of time the record shall be kept, and how it is treated at the end of its active lifecycle.

f. Permanent verses Temporary: Designation of permanent status or temporary status of records.

g. Vital Status: Records identified as necessary for continuing operations immediately following an emergency.

h. Volume: Amount of records.

Remarks: Reports will be approved by the location’s Records Manager. The Contractor shall notify the location’s

Records Manager the Plan has been uploaded. After approval of the submitted, modified, or updated Plan, the

Contractor will work with each location’s Records Manager to determine where the approved Plan will reside.

Each locations Records Manager will serve as the OPR for their location.

Maintenance: Changes to the document shall be identified with comments indicating where the changes have occurred. When an update occurs the revision number of the Plan will be updated.

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

2. DRD No.: 006-YAM 3. Data Type: 1 4. OPR: OCIO

10. Description/Use: To provide Government insight into the Contractor’s methodology for managing all aspects of information security and to ensure appropriate security of IT resources are addressed.

11. Distribution

Initial Submission: The Contractor shall submit the IT Security Management Plan no later than 30 days after the contract start date.

Submission Frequency: The Contractor shall review and update the Plan at least annually and submit by October

30th each year.

Format: The Contractor shall submit electronic versions that are compatible with Microsoft Office.

Interrelationship: PWS Para. 3.1.20(d); NFS 1852.204-76, Security Requirements for Unclassified Information

Technology Resources; NFS 1852.223-75 Alternate I, Major Breach of Safety or Security; NFS 1852.237-72, Access to Sensitive Information; NFS 1852.237-73, Release of Sensitive Information; NFS 1852.239-74, Information

Technology System Supply Chain Risk Assessment (Deviation [15-03D]); FAR 52.204-21, Basic Safeguarding of

Covered Contractor Information Systems

Applicable Documents: Federal Information Security Modernization Act (FISMA); NPD 2800.1, Managing

Information Technology; NPR 2810.1, Security of Information Technology (Revalidated with Change 1, dated May

19, 2011)

Scope: The Information Technology (IT) Security Management Plan shall cover the Contractor’s proposed management approach for meeting and complying with NASA and Federal requirements.

Contents: The plan shall describe the processes and procedures that will be followed to ensure the appropriate security of IT resources that are developed, processed, or used under this contract in accordance with NFS 1852.204-

76 to include but not be limited to:

1. Contractor’s information security POC(s) including roles, responsibilities, and contact information;

2. Process for meeting security authorization requirements, including development and maintenance of IT security plans, implementation and validation of controls, security assessments, remediation, authorization, and continuous monitoring for any corporate owned system processing NASA data

3. Process for meeting security authorization requirements, including development and maintenance of IT security plans, implementation and validation of controls, security assessments, remediation, authorization, and continuous monitoring for any system interfacing with NASA IT systems or for systems provided to

NASA.

4. Process for the use of mobile devices, mobile media, the encryption at rest, marking of media, and sanitization methods employed to protect location/Agency data.

5. Process for information security incident management and response, including coordination with NASA

Security Operations Center (SOC) and location/Agency civil service interfaces.

6. Process for ensuring that Contractor employees meet information security requirements, such as NASA IT security awareness and other required training, and that Contractor employees are knowledgeable of NASA IT security policies and procedures.

Remarks: An IT Systems Security Document Plan is not required due to the Contractor not being responsible for any IT systems.

The approved Plan will be incorporated into the contract.

Maintenance: Changes shall be incorporated as required by change page(s) or complete reissue. Changes shall be

1. DRD Title: Monthly Banding Levels Progress Report

2. DRD No.: 007-MAM 3. Data Type: 2 4. OPR: OCOMM

10. Description/Use: To provide visibility to the Contractor and NASA Management in assessing the cumulative year-to-date banding levels performed, by PWS section, per contract year, for both Mission Services and IDIQ TO efforts (as applicable).

Initial Submission: Due on the 10th calendar day following the end of the first month's performance.

Submission Frequency: Due on the 10th calendar day of each month.

Format: Refer to Electronic Format instruction; Separate reports shall be submitted for the base effort and for each

Task Order. The Contractor shall submit electronic versions in formats that are compatible with Microsoft Office.

Interrelationship: PWS Para. 3.1.20(h)

Scope: The Monthly Banding Levels Progress Report will provide a summary report detailing the cumulative year-to-date banding levels performed, by PWS section, per contract year, in order to provide visibility in assessing banding levels for both Core Services and IDIQ TO efforts (as applicable).

Contents: The Monthly Banding Levels Progress Report shall contain the following information broken out by a summary of estimated annual banding levels performed by each contract year, to include Mission Services efforts and any IDIQ task order banding levels established (as applicable). Each banding level reported shall include the following information:

a. PWS section.

b. Banding title.

c. Estimated annual range (i.e., low and high).

d. Number of banded product(s) or service(s) ordered to date.

e. Number of banded product(s) or service(s) delivered to date.

Remarks: A separate report shall be submitted for Core Services (segregated per Center) and each active indefinite-delivery, IDIQ task order (segregated per requiring organization and a compiled file per Center).

1. DRD Title: Monthly Progress Report

2. DRD No.: 008-MSA 3. Data Type: 3 4. OPR: OCOMM

S&MA ☒

10. Description/Use: To provide visibility to both the Contractor and NASA management of recent actual and/or potential problems satisfying requirements of the contract.

Initial Submission: Due on the 10th calendar day following the end of the first month's performance

Submission Frequency: Due on the 10th calendar day of each month

Format: Refer to Electronic Format instruction; A separate report shall be submitted for Core Services (segregated per Center) and each active IDIQ task order (segregated per requiring organization and a compiled file per Center).

The Contractor shall submit electronic versions in formats that are compatible with Microsoft Office.

Interrelationship: PWS Para. 3.1.20(g); PWS Para. 3.1.20(j); NFS 1852.216-80, Task Ordering Procedure-Alternate

II

Scope: The Progress Report shall provide a comprehensive status on the Core Services and IDIQ task orders in support of the PWS.

Contents: Progress Reports shall include the necessary information to assess status and identify problems that need resolution for accomplishment of contract efforts, including an evaluation of the Contractor’s performance for each of the Performance Requirements identified in Attachment D-4, Performance Requirements Summary, of the contract.

Progress Reports shall include a Technical, Business, and Management section as follows:

a. The Technical section shall contain the following comprehensive information for Core Services requirements as outlined in Attachment D-1, Performance Work Statement, and for each individual IDIQ task order :

1. A summary of the work accomplished for the current reporting period, including a report of technical and schedule performance.

2. A summary of any travel completed for the current reporting period, including the purpose and accomplishments of the travel, the number of people who traveled, the travel destination(s), and the date(s) of travel.

3. A summary of the work and travel planned for the next reporting period.

4. A status of any schedule milestone(s).

5. Identification of each incident failing to meet an Acceptable Performance Level (APL) in accordance with

Section D, Attachment D-4, Performance Requirements Summary. Each incident reported shall include the following information:

1. PRS number.

2. Work Requirement(s).

3. Performance Measure(s) / Standard(s).

4. APL.

5. Deduction (if applicable).

Note: failure to meet any APL shall be reported, regardless if a deduction is realized.

6. Provide insight regarding the nature or cause of each incident that did not satisfy APLs (e.g., rationale regarding Contractor's inability to meet APLs within its control; rationale regarding Contractor's inability to meet APLs not wholly within its control).

7. Provide planned mitigation to alleviate future occurrence(s) of incidents that did not satisfy APLs.

8. Provide insight into any additionally perceived problems or concerns that may require resolution for the successful accomplishment of contractual requirements. This should include proposed corrective action(s), where applicable.

b. The Business section shall contain the following for each Core Services requirement outlined in Attachment D-

1, Performance Work Statement, and for each individual IDIQ task order:

1. Core Services firm-fixed price (FFP) and WYEs per Center and remaining IDIQ Contract Line Item

Number (CLIN) values (current values, ceiling value, and delta value) for the contract period.

2. For FFP Core Services break out the FFP labor by the Attachment D-1, Performance Work Statement, by fourth level PWS section per month and cumulative by contract period.

3. For task orders break out the firm fixed price labor and Other than Direct Costs (ODC) (e.g. travel, training, materials) by the “task order number” per month and cumulative by task order period.

4. For task orders by TLIN, break out the time and material (T&M) actual labor (hours and cost) and ODC (e.g., travel, training, materials) per month and cumulative by contract period. Include an estimate for the remaining months of the task order period.

5. For task orders, break out the firm fixed price level of effort labor and ODC (e.g. travel, training, materials) by the “Task order number” per month and cumulative by contract period. Include an estimate for the remaining months of the task order period

6. A summary of Core Services FFP and IDIQ task order price for each CLIN at the NASA Agency level.

c. The Management section shall contain the following:

1. WYEs for Core Services at the NASA center level.

2. WYEs per task order under each IDIQ.

3. WYEs summarized at the CLIN level.

4. Total WYE by each subcontractor.

5. Core Services and task order vacancies status.

6. Data deliverables status.

1. DRD Title: On-Site Mishap and Safety Statistics Reports

2. DRD No.: 009-MSA 3. Data Type: 3 4. OPR: OSMA

10. Description/Use: To provide information on mishaps and close calls affecting the Contractor’s safety and Health performance.

11. Distribution: CO KSC; CO JSC; CO MSFC; NCS COR

Initial Submission: Due no later than 30 days after contract start.

Submission Frequency: Due on the 15th of each month after the initial submission.

Format: Refer to Electronic Format instruction; The Contractor shall also submit each Centers report as specified in

JSC Form JF288, “Statistical Information – Contractor Safety and Health Program”

Interrelationship: PWS Para. 3.1.20(j); PWS Para. 3.3.2; NFS 1852.223-70

Applicable Documents: KSC-PLN-2807; MCP 8621.1, SPLN-8621-0003; NPR 8621.1;

Scope: Information on mishaps and close calls as specified in appropriate center form.

Contents: See appropriate center forms (e.g. JSC Form JF288)

Maintenance: None

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

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

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: Distribution shall be as instructed by the contracting officer.

CO: KSC, JSC, MSFC

NCS COR

Initial Submission: Plan shall be submitted with the initial proposal. The final OCI Plan shall be submitted within five (5) business days after the effective date of the phase-in purchase order.

Submission Frequency: As needed.

Interrelationship: PWS Para. 3.1.20(c), 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.

1. DRD Title: Performance Assessment Report

2. DRD No.: 011-QAM 3. Data Type: 2 4. OPR: OCOMM

10. Description/Use: To be used in assessing NCS Contractor performance.

11. Distribution: CO KSC; CO JSC; CO MSFC; NCS COR

Initial Submission: Due on the 15th calendar day following the end of the first six months of contract performance.

Submission Frequency: Due on the 15th day of the month following the end of each six months of additional contract performance

Interrelationship: PWS Para. 3.1.20(i)

Scope: The Contractor shall prepare a semi-annual report of NCS activities. The purpose of the report is to provide a basis for discussion of contract status and contract activity with NASA senior management and to identify potential or actual systemic problems meeting PWS requirements, summarizing where acceptable quality levels (APL) were not met in accordance with Section D, Attachment D-4, Performance Requirements Summary (PRS), during the previous six months of contract activity.

Contents: The report will be in the form of briefing charts (due within fifteen calendar days after the end of the semi-annual period) and a briefing (delivered after the briefing charts are submitted) that address contract highlights and activities for the previous semi-annual period being reported.

As a minimum, the report shall include the following information for Mission Services and for each individual task order:

a. Highlights, activities, and operational successes by PWS section.

b. Summary of all reoccurring incidents that failed to meet an APL during two or more monthly evaluation periods, in accordance with Section D, Attachment D-4, Performance Requirements Summary.

c. Insight regarding failure for previously planned mitigation efforts at being successful (i.e., why did incidents continue to fail to meet the same APL?).

d. Planned mitigation to alleviate future occurrence(s) of repetitive evaluation incidents that did not satisfy

APLs (i.e., mitigation for potential or actual systemic problems satisfying APLs).

e. Insight into any unresolved problems or concerns that require resolution for the successful accomplishment of contractual requirements. This should include proposed corrective action(s) to eliminate potential or actual systemic problems satisfying APLs.

f. A discussion of planned versus actual costs for Fixed Price Level of Effort and Time and Materials efforts and any actions proposed to ensure performance to the estimated plan.

Maintenance: None

1. DRD Title: Phase-Out Plan

2. DRD No.: 012-OAM 3. Data Type: 1 4. OPR: OCOMM

10. Description/Use: To ensure the Contractor has an efficient approach during the phase-out period to facilitate transition of services from the Contractor to the successor contractor at the end of the performance period.

Initial Submission: The Contractor shall submit a draft Phase-Out Plan 6 months prior to the contract performance end date. The Contractor shall incorporate Government comments on the Plan and deliver a final Phase-Out Plan within 30 calendar days of receipt of the Government comments.

Submission Frequency: N/A

Interrelationship: PWS Para. 3.2.1(e)

Scope: The Contractor’s Phase-Out Plan shall include sufficient information to address the Contractor’s approach to implement transitioning services and support from the Contractor to the successor contractor, including sharing of contract applicable information.

Contents: At a minimum, the plan shall include the Contractor’s approach to:

1. Maintain high quality standards for contract requirements through contract expiration

2. Schedule of transition activities for Mission Services and each IDIQ task order

3. Transition Government-owned data such as records, procedures and reports to be accessible to the successor contract

4. Identify and extract Government-owned data from Contractor’s IT systems

5. Communicate with workforce on key milestones and expectations for contract transition activities

1. DRD Title: Records Management Program Plan

2. DRD No.: 013-OAM 3. Data Type: 3 4. OPR: OCOMM

10. Description/Use: To describe the overall approach to the Records Management Program.

CO: KSC, JSC, MSFC; NCS COR

Initial Submission: Within 60 calendar days after contract effective date.

Submission Frequency: As needed

Interrelationship: PWS Para. 3.4

1. NASA Procedural Document (NPD) 1440.6, NASA Records Management,

2. NASA Procedural Requirement (NPR) 1441.1, NASA Records Management Program Requirements

3. NASA Records Retention Schedules (NRRS) 1441.1, NASA Records Retention Schedules (as revised)

4. Kennedy NASA Procedural Requirement (KNPR) 1440.6, KSC Records Management

5. NPD 2190.1B, Export Control Program

6. 44 U.S.C. Chapters 29, 31, 33.

7. 44 U.S.C. 3501 et seq., Paperwork Reduction Act.

8. 36 CFR Parts 1220-1238.

9. Executive Order 12656, Assignment of Emergency Preparedness Responsibilities, Sections 201, 202, 1901, and

2001 (November

10, 1988), as amended.

10. Federal Acquisition Regulation 52.227-14 and 52.227-16

11. KSC Clause 52.245-90 and 52.245-97

Scope:

The Records Management Program Plan (RMPP) shall describe the implementation of a records management program in accordance with the documents referenced in this DRD. The RMPP shall provide sufficient detail to demonstrate an understanding of the compliance requirements including the following areas:

Contents:

I. Program Management

a. Program Authorization and Organization

b. Guidance and training

c. Internal Evaluations

d. Procedures and Processes

II. Records Creation/Recordkeeping Requirements

a. Creation of records/adequacy of documentation

b. Contractor Records

III. Records Maintenance (General)

a. General

b. Paper-based Records

c. Electronic Records

d. Legacy Records

IV. Maintenance of Special Records

a. Electronic Records

b. Audiovisual Records

c. Cartographic and Architectural Records

d. Micrographic Record

V. Records Disposition

a. Records Disposition Schedule Implementation

VI. Vital Records

The following definitions are provided for clarification purposes:

1. Government Records

a. Except as provided in 2. of this requirement, all records acquired, generated or maintained by the contractor in its performance of this contract including, but not limited to, documentation of those actions, policies, decisions, operations, reviews, and activities necessary to perform or continue the work performed under the contract, shall be the property of the Government and shall be delivered to the Government or otherwise disposed of by the contractor either as the Contracting Officer or the Kennedy Space Center (KSC) Records Manager may from time to time direct or, as the Contracting Officer shall direct upon completion or termination of the contract. This sub-paragraph (a) shall not apply to documents owned by third parties that are in the possession of the contractor (e.g. documents containing trade secrets of third parties).

b. To the extent Government records are in the possession of the contractor (e.g., Government-owned, contractor-held), the Government shall have full and prompt access to the same. (The Government’s full and prompt access to data or records generated, or otherwise produced or prepared at, by, or for KSC irrespective of form or medium of the data; apply to all such data or records without regard to the date or origination of such data or records, and without regard to ownership.)

c. The Government shall have unlimited rights in information incidental to contract administration including administrative and management information created under the contract by the contractor and specified for delivery to

National Aeronautics and Space Administration (NASA) in performance of the contract, expressly excluding confidential contractor financial…