80JSC020R0018-SASS-Attachment J-2 DRL-DRD's.pdf

JSC Form 2323 01/15 (1.0)

JSC DATA REQUIREMENTS LIST (DRL)

(See last page for instructions)

Based on JSC-STD-123

a. Title of Contract, Project, SOW, etc.

Simulation & Advanced Software Services (SASS)

b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Contract Management Plan

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

AR

5. As-of-date

See Box 9

6.1st subm. date

With Proposal

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR

9. Remarks Initial submission with proposal in accordance with Section L of the solicitation. Subsequent revision(s), as necessary.

a. Title of Contract, Project, SOW, etc.

Simulation & Advanced Software Services 9SASS)

b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Information Technology (IT) Security Program Plan and Reports

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

AN

5. As-of-date

See Box 9

6.1st subm. date

See Box 9

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) Initial: BH/Contracting Officer, ER/COR, OCSO, JSC CISO Subsequent: BH/Contracting Officer, ER/COR, OCSO

9. Remarks Initial submission 30 days prior to contract start. Subsequent revision(s), as necessary.

a. Title of Contract, Project, SOW, etc.

Simulation & Advanced Software Services (SASS)

b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Information Technology (IT) Capital Planning and Investment Control (CPIC)

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

See Box 9

5. As-of-date

See Box 9

6.1st subm. date

See Box 9

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR, OCSO

9. Remarks Frequency: twice annually, as part of the Government’s CPIC and PPBE reporting cycle (in February and August of each calendar year)

(See last page for instructions)

Based on JSC-STD-123

a. Title of Contract, Project, SOW, etc. b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Data and Records Management Plan

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

AN

5. As-of-date

See Box 9

6.1st subm. date

See box 9

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR

9. Remarks Initial submission 30 days after contract award. Subsequent revision(s), as necessary.

a. Title of Contract, Project, SOW, etc. b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Government Property Management Plan (PMP)

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

AR

5. As-of-date

See Box 9

6.1st subm. date

See Box 9

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR

9. Remarks Initial submission in accordance with Section L of the solicitation.

Subsequent revision(s), as necessary.

a. Title of Contract, Project, SOW, etc. b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Administrative Safety and Health Plan

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

AN

5. As-of-date

See Box 9

6.1st subm. date

See Box 9

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR, NS S&T OD, JSC OHO, JSC EPO

9. Remarks Submit after Contract Award to ensure approval before Contract Start. Subsequent revision(s), as necessary.

(See last page for instructions)

Based on JSC-STD-123

a. Title of Contract, Project, SOW, etc.

Simulation & Advanced Software Services (SASS)

b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Organizational Conflicts of Interest (OCI) Plan

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

AN

5. As-of-date

See Box 9

6.1st subm. date

With Proposal

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR

9. Remarks Initial submission in accordance with Section L of the solicitation.

Subsequent revision(s), as necessary.

a. Title of Contract, Project, SOW, etc.

Simulation & Advanced Software Services (SASS)

b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Re-procurement Data Package

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

AD

5. As-of-date

N/A

6.1st subm. date

AD

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer

9. Remarks

a. Title of Contract, Project, SOW, etc.

Simulation & Advanced Software Services (SASS)

b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date 11/13/2019

1. Line item no.

2. DRD Title Monthly Status Reports

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

MO

5. As-of-date

N/A

6.1st subm. date

TBD

7. Copies

a. Type

ES

b. Number N/A

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR

9. Remarks

(See last page for instructions)

Based on JSC-STD-123

a. Title of Contract, Project, SOW, etc.

Simulation & Advanced Software Services (SASS)

b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date

1. Line item no.

2. DRD Title NASA Contractor Financial Management Reports

(NF 533)

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

MO

5. As-of-date

N/A

6.1st subm. date 7. Copies

a. Type

EM

b. Number

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR, LE/ Budget Analyst

9. Remarks

a. Title of Contract, Project, SOW, etc.

Simulation & Advanced Software Services (SASS)

b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date

1. Line item no.

2. DRD Title Phase- In Plan

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

RT

5. As-of-date

N/A

6.1st subm. date

With Proposal

7. Copies

a. Type

EM

b. Number

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR

9. Remarks

a. Title of Contract, Project, SOW, etc. b. Contract/RFP No.

80JSC020R0018

c. DRL Date/Mod Date

1. Line item no.

2. DRD Title The NASA Advisory and GIDEP Problem Data Sharing and Utilization Program Documentation a

3. Data type:

(1) Written approval

(2) Mandatory Submittal

(3) Submitted upon request

4. Frequency

RT

5. As-of-date

N/A

6.1st subm. date

AD

7. Copies

a. Type

EM

b. Number

8. Distribution (Continue on a blank sheet if needed) BH/Contracting Officer, ER/COR, NS S&T OD, JSC OHO, JSC EPO, JSC GIDEP

9. Remarks

Short Form Instructions for Completing JSC Form 2323 & 2323A For more detailed instruction, see JSC-STD-123.

DRL IDENTIFICATION

a. Title - Enter nomenclature descriptive of activity to which the DRL pertains, such as project, contract, statement of work, or request for proposal.

b. Contract/RFP Number - Enter contract number or RFP number, if applicable.

c. Date - Enter DRL preparation date as follows: Month-Day-Year. Subsequent modification dates may also be entered in this block.

LINE ITEM IDENTIFICATION 1.

1. Line Item No. - Number line items sequentially, 1 through 999.

2. DRD Title - Enter DRD title from block 1 of JSC Form 2341.

3. Data Type - Check the appropriate data type. Additional detail needed to clarify types or define subtypes may be added in block 9, REMARKS.

(1) Written Approval - Data requiring written approval by the NASA OPR before implementation into procurement or development program.

(2) Mandatory Submittal - Data submitted to NASA for coordination, information, review, and/or management control.

(3) Submittal upon Request - Data prepared and retained by respondent to be made available to requiring organization upon request.

4. Frequency - Enter frequency of submittal code as follows:

Code Description Code Description Code Description

AD As Directed DA Daily RD As Released AN Annually DD Deferred Delivery RT One Time and Revisions AR As Required MO Monthly SA Semiannually BE Biennially (Every other yr.) OT One Time TY Three Per Year BM Bimonthly (Every other mo.) PV Per Vehicle UR Upon Request BW Biweekly (Every other week) QU Quarterly WK Weekly

5. As-Of Date - If reports are of a recurring nature, give as-of date (cutoff date and due date: e.g., 15/1 indicated cutoff date on 15th and due date on 1st). Amplify in Remarks, Item 9, if necessary.

6. First Submittal - Enter Month/Day/Year of initial submittal. If calendar date is not scheduled, enter number of days preceding or following event to which data requirement is related (e.g., 90 days prior to launch). Amplify in Remarks, Item 9, if necessary.

7. Copies - Complete 7a and 7b as specified below:

a. Type - Enter code as follows:

Code Definition Code Definition PRINT Printed Copies MICRO Microfilm Aperture Cards REPRO Reproducible Copy OTHER Explain in Remarks, Item 9

b. Number - Enter number of copies required opposite each type of copy furnished.

8. DISTRIBUTION - List current codes or addresses and names of organizations which are to receive copies of documents generated under the DRD. If more than one copy is required, so indicate in parenthesis by recipient's name. Continue on a blank sheet if necessary.

9. REMARKS - Enter in this space:

a. Reference to specific work statement paragraph as applicable to explain relationship of data to task.

b. Additional submittal information, if necessary.

c. Comments which explain an entry made in any block of the DRL.

d. OPR for a specific DRD, if different from contract COR.

1. DRD Title 2. Date of current version

3. DRL Line Item No.

RFP/Contract No.

Contract Management Plan 09/05/2019 01 80JSC020R0018

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one) To describe the contractor's management organization, approach, and systems and how they will be utilized to support the Simulation & Advanced Software Services (SASS) contract.

Technical Administrative

SR&QA

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

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

A. SCOPE

The Contract Management Plan (CMP) shall be an umbrella document, which encompasses and integrates all contract management activities necessary to successfully accomplish the contract requirements. The CMP shall describe the contractor’s organizational structure, contract management approach, including staffing and workforce management, and management systems that will be used to ensure technical, schedule, and cost performance. The plan shall be comprehensive in nature, providing management systems for planning, organization, control, and reporting of all activities required by this contract for the purpose of accomplishing technical and schedule requirements and meeting cost objectives, and integrating all management systems of the prime, teaming partners, and subcontractors.

The contractor shall implement technical management processes commensurate to the technical product or service being provided in accordance with contract provisions. The contractor shall provide technical discipline expertise, independent assessment, engineering analysis, technical insight, technology assessment and development, and programmatic support, as required to assure the highest degree of technical accuracy and quality. The contractor shall interface with, but remain distinctly independent from, all other contractors supporting NASA programs.

B. CONTENT

The plan shall include the elements listed below, as a minimum. The contractor may include any additional elements as needed or desired to ensure that the plan fully and optimally addresses essential processes and systems to manage the contract.

1. Management Approach

The contractor shall describe the overall contract management approach, strategies, policies, processes for work planning, subcontract management, organizational structure, indirect cost management including any efficiencies proposed.

a. Include an organizational chart (including teaming partners, subcontractors, or joint venture partners and their reporting relationship) that illustrates the proposed organizational and management structure of the local contract.

b. If applicable, describe the unique benefits, capabilities, and rationale of your approach to subcontracting or teaming.

c. If applicable, describe your method for effectively managing teaming partner’s or subcontractor’s contribution to the contract.

d. If your approach is a joint venture, provide details of the nature of the joint venture and discuss your schedule for the Small Business Administration review and approval of the joint venture plan.

e. Discuss management of span of control (i.e. ratio of supervisory personnel to staff), and autonomy in decision making.

f. Describe the approach and rationale for identifying, filling, and retaining Key Personnel positions (including Key Personnel positions of teaming partners and subcontractors, if proposed). Address the Key Personnel positions listed/proposed in Clause 1852.235-71, Key Personnel and Facilities, and the responsibilities associated with these positions. For the Government identified Key Personnel positions listed in Clause 1852.235-71, the proposed Program Manager shall map to the Program Manager in Attachment J-03, Standard Labor Categories. The Advanced Software Lead and Simulation and Graphics Lead shall map, at a minimum, to the Senior Engineer 1 in Attachment J-03, Standard Labor Categories. The Advanced Software Lead provides technical oversight for Section 3.2 Advanced Software Services scope of the SASS SOW. The Simulation and Graphics Lead provides technical oversight for Section 3.1 Simulations Services scope of the SASS SOW. The contractor may propose the same individual for any combination or all of these key positions. Provide the basis for identifying the proposed Key Personnel positions and the basis for selection of individuals to fill Key Personnel positions, to include a summary of the qualifications to fill those positions including education, training, certifications, and type and length of experience. Describe the qualification standards you will use to replace Key Personnel, if required, during the term of the contract.

Provide this information for each key position. Describe how you will ensure key personnel will maintain the minimum qualification standards.

g. Describe the management relationships between the contractor’s key personnel and associated NASA personnel, including communication channels, lines of authority (including the line of succession if Program Manager is unavailable), reporting relationships, and responsibilities of all organizational elements.

h. Discuss how your proposed approach will facilitate and encourage free and open communication and problem resolution at the lowest level.

2. Staffing and Recruiting

a. Provide a narrative that describes the overall staffing approach.

b. Describe staffing of the proposed organizational structure including proposed teaming partners and subcontractor personnel, including the numbers and types of personnel.

c. Discuss your proposed recruitment and employment methods to staff the contract initially and during the contract performance period.

d. Provide the anticipated percentage of total workforce that will be recruited initially from incumbent’s workforce, outside recruitment, and from the offeror’s company to ensure continuity of operations.

e. Identify how you will mitigate the risk of losing valuable incumbent local knowledge and skills.

f. Describe your processes for work planning and corporate reach-back.

g. Discuss your plans for enhancing the health, welfare and morale of employees, including retention of high-performing employees.

h. Describe plans for staffing flexibility to accommodate changes in requirements, fluctuation in workload and unexpected attrition including how staffing will be managed for newly authorized work.

3. Workforce Management

a. Discuss the risk of single-point failures and how you will mitigate the risk.

b. Identify all critical skills across the contract and explain how and to what level those critical skills will be maintained. Also include how the loss of a critical skill will be mitigated.

c. Describe plans for cross-training personnel.

d. Discuss how you will promote professional growth and knowledge of your employees.

e. Discuss how you will ensure that employees maintain technical proficiency and training to perform effectively.

f. Discuss strategy to ensure personnel will maintain the minimum qualification standards described in the

Standard Labor Category guidelines.

g. Describe how resources will be managed to support peaks and valleys in the workload.

h. Describe your company policy with regard to the use of employees participating in the Super-Flex schedule. For example, if your company permits employees to participate in the Super-Flex schedule, how will your company maintain contract services and manage the use of overtime pay?

4. Management Systems

Provide a discussion on your management policies and procedures that will be implemented to provide high quality services that meet customer expectations, including the following:

a. Discuss the timeline and process/procedure associated with providing Task Order (TO) estimates to NASA once a TO has been received from NASA.

b. Describe the contractor’s approach to managing multiple and concurrent TOs.

c. Demonstrate your understanding of the scope and nature of work described in the Statement of Work by identifying technical, cost, schedule and management risks to JSC associated with performance of the contract and your plan to mitigate those risks.

d. Describe your proposed quality control and corrective action processes to monitor performance and fix identified problems, whether those problems are identified by the contractor, the Contracting Officer’s Representative, or others.

e. Describe the methods to ensure timely delivery of quality services.

f. Identify any internal metrics that might be used to ensure successful performance of the contract.

g. Discuss your approach to establishing and maintaining effective working relationships with other contractors and other JSC organizations.

h. Describe the staffing location plans, including lease arrangements, for the contractor’s off-site facilities, including a discussion of the on-site and off-site approach. Discuss any other issues related to logistics management.

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

C. SUBMISSION

• Initial: With the initial proposal

• Final: Upon contract award, the Contractor’s CMP will be incorporated into the final contract

• Updates: As required. Submit revisions for Government approval after any major change in management organization and approach.

D. DISTRIBUTION

• Initial: As specified in the Proposal Instructions

• Final: Contracting Officer (CO) and Contracting Officer’s Representative (COR)

• Updates: CO and COR

E. MAINTENANCE

The contractor may revise the CMP at any time or at the direction of the Contracting Officer. Revisions to the CMP are subject to Contracting Officer review and approval. Changes shall be incorporated as required by complete reissue.

3. DRL Line Item No.

RFP/Contract No. (Procurement completes)

Information Technology (IT) Security Program Plan and Reports

09/05/2019 02 80JSC020R0018

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one) To ensure that IT security reporting requirements are met for all IT systems utilized during work associated with this contract.

Technical Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) FAR 52.204-21: Basic Safeguarding of Covered Contractor Information Systems NFS 1852.204-76: Security Requirements for Unclassified IT Resources NFS 1852.223-75: Major Breach of Safety or Security NFS 1852.237-72: Access to Sensitive Information NFS 1852.237-73L Release of Sensitive Information NPR 2810.1(series): Security of Information Technology.

OMB Circular A-130: Management of Federal Information Resources

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

A. SCOPE

All contracts that purchase, lease, network to, or otherwise utilize Government-funded IT (as defined by the Clinger-Cohen Act of 1996 and referenced by OMB Circular A-130) must comply with NASA IT Security Requirements. The contractor shall provide technical data management to ensure secure communication between NASA computer systems and contractor computer systems as needed to perform the work associated with this contract.

B. CONTENT

1. IT SECURITY MANAGEMENT PROGRAM PLAN:

The Contractor shall submit an IT Security Management Program Plan for its unclassified technology information resources. This program plan shall describe the policy, processes, and procedures that will be followed to ensure appropriate security of IT resources that are developed, processed, or used under this contact. The Contractor’s IT Security Management Program Plan shall be compliant with the IT security requirements in accordance with Federal and NASA policies as referenced in OMB Circular A-130 and NPR2810.1 (series).

2. IT SECURITY PLAN:

The Contractor shall have Information Systems Security Officer (ISSO) who is responsible for the contractor’s system(s) in accordance with the definitions set forth in NPR2810.1 (series). The IT security plan shall be kept up to date as changes to the baseline configuration of the system occur and shall be documented in the IT Security Plan.

Note: An IT Security Plan is specific to a system or group of systems, while an IT Security Management Program Plan is defined as the elements a contractor has outlined to meet the IT Security requirements for interfacing with other contractors and NASA, training requirements and meeting the requirements in NPR 2810.1(series).

3. IT SECURITY AWARENESS TRAINING:

Employees subject to this contract shall complete the NASA approved IT Security Awareness Training annually. The contractor shall provide evidence that periodic IT security awareness training has been met for all employees subject on this contract. The contractor shall submit periodic reports (as required by the CO) detailing the overall status of the annual training program. The annual training program is defined as the period from October 1st through September 30th.

4. IT SECURITY ROLE BASED TRAINING:

Employees subject to this contract shall complete NASA approved IT Security Training annually related to the following Role Based functions:

• IT Security Manager

• Information System Owner (ISO)

• Information Systems Security Officer (ISSO)

• Organizational Computer Security Official – Representative (OCSO-R)

The Contractor shall provide evidence that periodic IT security training has been met for all employees subject on this contract. Contractor provided IT security awareness training may be substituted but must be approved annually by the Government (via the JSC Center IT Security Officer [CISO]) as an acceptable substitute. The Contractor shall submit periodic reports (as required by the CO) detailing the overall status of the annual training program. The annual training program is defined as the period from October 1st through September 30th.

5. INFORMATION ON EMPLOYEES IN SENSITIVE POSITIONS/ASSIGNMENTS REPORT:

The Information on Employees is Sensitive. ITS Positions/Assignments Report shall provide information annually for personnel screening as required by NPR 2810.1(series), and NPR 1600.1 on position risk.

6. IT POINT OF CONTACT:

The contractor shall identify a point of contact that NASA may reach in its attempt to address IT and IT Security issues. The point of contact shall have the authority to ensure appropriate actions occur.

A list of all lead system administrators shall be updated by September 30 of each year. This list will be used to ensure the Contractor, as outlined in PN 04-03, has met the system administrator certification requirements.

C. SUBMISSION

1. IT Security Program Management Plan

• Initial: 30 days prior to contract start

• Approval: upon contract start

• Frequency: Annually by September 30

2. IT Security Plan(s)

• Initial: assume maintenance of existing plans (for Government-owned and Contractor-managed systems) at Contract start;

• IT Security Plan(s) for contractor-owned systems due 30 days prior to contract start.

• Approval: upon contract start

• Frequency: shall be kept up-to-date as changes to the baseline configuration of the system(s) occur

3. Others as stated in this DRD

D. FORMAT

Unless otherwise directed, the data requested in this DRD shall be delivered to the Government in soft-copy via an electronic transfer mechanism (e.g., electronic mail, flash drive, or file transfer protocol) in a format readable by a Government device utilizing the standards in NASA-STD-2804, Minimum Interoperability Software Suite.

See Data Requirements List (DRL).

F. DISTRIBUTION

Data Requirements List (DRL).

• Initial approval: Contract COR, CO, Contracting Organization’s OCSO, and JSC CISO

• Annual approval: Contract COR, CO, and Contracting Organization’s OCSO

3. DRL Line Item No.

4. RFP/Contract No.

Information Technology (IT) Capital Planning and Investment Control (CPIC)

03 80JSC020R0018

4 Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category (check one) To document the Contractor's compliance with Federal and NASA IT CPIC Planning and Reporting regulations and reporting requirements

Technical Administrative

SR&QA

6. References (Optional) 7. Interrelationships (e.g., with other DRDs) (Optional) OMB Circular A-11 and A-130

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

A. SCOPE

Information Technology (as defined in the Clinger-Cohen Act) is subject to certain scrutiny and reporting requirements as set forth in Legislative actions and Executive and Agency mandates, and directives. The Office of Management and Budget (OMB) Circular A-130 establishes the foundation for CPIC. OMB Circular A-11 establishes the guidelines and requirements for reporting to the Executive Branch. The Contractor shall prepare a report of all IT expenditures consistent with the Agency’s annual guidelines for the annual data call. Any additional reporting requirements associated with the CPIC data collection and reporting process will be covered by this DRD.

In conformance with CPIC processes, all contractors shall participate in data collection and reporting efforts. All contractors shall furnish the data needed for the Agency to comply with Office of Management and Budget reporting requirements including but not limited to those documented in OMB Circular A-11. Accurate and complete data submissions are to be made in a manner consistent with the reporting structure, and within the timeframes established for the Center.

B. CONTENT

All contractors shall submit their Fiscal Year spending plans for IT equipment for review and approval by the Johnson Space Center (JSC) Chief Information Officer (CIO), or designee, prior to the beginning of the Fiscal Year (October). Changes to spending plans during the Fiscal Year shall be approved by the JSC CIO, or designee, before implementation. Formats and reporting processes and procedures will be provided annually based upon Center and Agency requirements.

Examples of documentation, formats, processes, procedures and structures will be provided annually in support of the data call. This is a dynamic process, and formats, processes, procedures and structures are subject to change. The reporting requirement is defined by OMB annually. Each year, OMB may request varying levels of reporting across varying levels of technologies and labor, depending on their focus.

C. SUBMISSION

Frequency: twice annually, as part of the Government’s CPIC and PPBE reporting cycle (in February and August of each calendar year) as defined in DRL.

3. DRL

Item No.

RFP/Contract No.

Data and Records Management Plan 5/30/2018 04 80JSC020R0018

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one) To describe the contractor’s plan to store, provide access to, and transition at contract end, all data and records generated by and transitioned to the contract at contract start.

This includes fulfilling any reporting requirements throughout the contract period of performance.

Technical Administrative

SR&QA

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

• GEIA 859

• NPR 1441.1E NASA Records Management Program Requirements

ANSI/EIA Standard 649, Configuration Management (or what is the most current version)

• EIA Standard 836, Configuration Management Data Interchange and Interoperability.

All data and records stored on the contractor’s IT systems within scope of this contract that are acquired, generated, controlled, archived, and transitioned at contract end. Data and records include any source code developed in support of the contract. Proprietary information technology systems, applications, or protocols that fail to meet NASA information technology standards shall not be utilized without prior NASA contractual authorization.

B. CONTENT

The Data and Records Management Plan shall define the scope and depth of the Contractor’s efforts including management, organization, planning, and implementation. The plan shall include the following elements:

1) data and records identification

2) data and records control

3) data and records status accounting

4) data and records acquisition

5) data and records management and verification

6) data and records management organization

7) data and records storage and retrieval procedures

8) subcontractor procedures

9) special restrictions

10) process to transition data and records at contract end

11) NASA Records Management training for personnel responsible for managing records

The plan shall include a preliminary data submittal schedule for fulfilling submission of data in the specific quantities, media, and due dates required. The Contractor shall verify and validate their data and records management system through an internal audit process.

C. FORMAT

The data and records management plan shall be delivered in native format and be compatible with JSC standard software loads.

D. MAINTENANCE

Revision required with major scope change.

E. DISTRIBUTION

Distribution shall be in accordance with the DRL.

F. INITIAL SUBMISSION

Due 30 days after contract award.

G. SUBMISSION FREQUENCY

Annually or as directed by the CO

3. DRL Line Item No.

RFP/Contract No.

Government Property Management Plan (PMP) 11/17/2017 05 80JSC020R0018

4. Use (Define need for, intended use of, and/or anticipated results of data) 5. DRD Category: (check one) To describe the method of administering and controlling Government personal property and submitting proposed property manager qualifications.

S&MA

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

• Federal Acquisition Regulation (FAR) 52.245-1

• Government Property Clause

The Government Property Management Plan defines the Contractor's use, maintenance, repair, protection, and preservation of Government personal property. It shall describe the Contractor's approach to receiving, handling, stocking, maintaining, protecting and issuing Government property (equipment and material). The Plan should include interaction and Department/ Office responsibilities. The Contractor shall submit to the delegated Government Property Administrator (GPA) detailed supplemental property procedures, which are separate from the Property Management Plan, within 60 days after the contract start date.

The Contractors submitting an initial Property Management Plan as part of their reply to the Request for Proposal in accordance with Contracting Officer direction, will also submit proposed property manager qualifications and experience as specified below.

B. CONTENT

This plan shall reference those policies and procedures which are part of the Contractor's Property Management System and shall include at a minimum, but not limited to, the following functions/outcomes/activities:

1. Property Management

a) Voluntary consensus standards, industry-leading practices and standards, customary commercial practices

b) Periodic internal reviews, surveillances, self-assessments, and audits

c) Written procedures

2. Acquisition of Property

a) Acquisition authority

b) Classification of property

3. Receipt of Government Property

a) Receiving

b) Identification

4. Records of Government Property

5. Physical Inventory

6. Subcontractor Control

Flow down of property clauses to subcontractors

7. Reports

a) Loss, Theft, Damage, Destruction reports

b) Physical Inventory reports

c) Audits and self-assessment reports

d) Corrective Action reports

8. Relief of Stewardship Responsibility and Liability

a) Loss, Theft, Damage, Destruction of property

b) Consumed property

c) Delivered property

d) Contractor Inventory Disposal of property

i. In-house screening of excess

ii. Disclosure of excess

e) Abandonment of Government property (if directed by the Government)

9. Utilizing Government Property

a) Utilization

b) Consumption

c) Movement

d) Storage

10. Maintenance

a) Preventive maintenance

b) Rehabilitation

c) Calibration

11. Property Closeout

a) Screening for further use

b) Final physical inventory

c) Transfers off the contract

d) Final NASA Form 1018

12. Reconcile Contractor Records with NASA Financial Property Records [NASA Form 1018 and the Contractor-Held Asset

Tracking System (CHATS) if applicable]

13. JSC-Unique Considerations (as they arise or known now)

C. MANAGEMENT QUALIFICATIONS/EXPERIENCE

1. The Offeror/Contractor shall specify the name and the qualifications of the proposed property manager.

a) List the Federal agencies or departments supported in managing Government property and the corresponding number of years of experience.

b) List completed personal property management training courses.

c) Specify the level of professional property management certification obtained by the proposed property manager.

d) List professional personal property management organizations in which the proposed property manager has an active current membership.

2. This qualification data shall be a one-time submittal from the Offerors with their initial Property Management Plan (PMP) when the plan is requested by the Contracting Officer. Insert that data as a separate tab after that PMP. This qualification data shall be excluded from the final PMP from the awarded Contractor.

D. FORMAT

The Contractor’s format is acceptable.

E. MAINTENANCE

Changes to the PMP shall be incorporated by change pages or complete reissue after coordination with the Government

PA.

3. DRL Line Item No.

RFP/Contract No.

Administrative Safety and Health Plan 10/2018 06 80JSC020R0018

4. Use (Define need for, intended use of, and/or anticipated results of 5. DRD Category: (check one) Establishes Safety and Health Plan for Contractors providing support to JSC organizations. The Office of Primary Responsibility for this DRD is the JSC Safety and Test Operations Division

Technical Administrative

S&MA

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

• OSHA CSP 03-01-003, Voluntary Protection Program (VPP): Policies and Procedures Manual

• JPR 1700.1 JSC Safety and Health Requirements

• JPR 1040.4, JSC Emergency Preparedness Plan

• NPR 8621, NASA Procedural Requirements for Mishap and Close Call

Reporting, Investigating, and Recordkeeping

• JPR 2310.1, JSC Organizational Learning Program

Establishes Safety and Health Plan for Contractors providing support to JSC organizations. The Office of Primary Responsibility for this DRD is the JSC Safety and Test Operations Division.

B. CONTENT

The plan must include instructions for submitting the deliverables in Table 1 below to the Government and represent contractual commitments by the Contractor to provide this information. Include copies to the Contracting Officer and Contracting Officer’s Representative.

Table 1, Safety and Health Deliverables

Deliverable Frequency DRD ¶ Comments Identity of key safety and health personnel:

• Company Physician/ Occupational

Injury/illness case manager

• Designated Safety Official

• Safety Representative

• Building Fire Wardens (Roster)

Within 15 days of contract start and updated with changes

1.5 Include in plan or

attachment to plan

Safety and Health Self Evaluation Report Yearly by Sept 30 1.8 Send to Safety and Test Operations Division

Roster of Terminated Employees Yearly, 30 days after the end of the contract year

1.9.1 Send to the Occupational

Health Branch

Material Safety Data Sheets (MSDS)/ Safety Data Sheets (SDS)

When you introduce a new hazardous material

1.9.2 Send to the Occupational

Health Branch See JPR 1700.1, Chapters 9.1 & 9.2

Hazardous Materials Inventory Yearly or when quantities or locations change significantly. Some products require quarterly updates

1.9.3 Send to the Occupational

Health Branch See JPR 1700.1, Chapter 9.2

Inspection results entered in Building Inspection Tracking System (BITS)

10 working days after completing inspection

2.4

On-site close calls forwarded to JSC close call tracking system

Within 3 working days of receipt

2.6 Send to Safety and Test

Operations Division Required only for contractor close call systems

Deliverable Frequency DRD ¶ Comments Mishap reporting Immediate and follow-up as required in JPR 1700.1

2.7.1 See Chapter 2.6 of JPR

1700.1

Lessons Learned Report Enter data into the JSC LLDB or NASA LLIS:

• Within 30 days of a triggering event;

• Within 30 days of a program milestone, mishap investigation, or hazard or other engineering analysis / evaluation is completed; or

• 30 days before end of contract evaluation period or 45 days before end of contract, whichever is applicable.

2.7.1.7 Database entry with 1

electronic copy to the Contracting Officer’s Representative

JSC Form 288, “Statistical Information - Contractor Safety and Health Program”

Monthly by the 10th of the month

2.7.2. a Send to JSC-Safety- Report-Submittals <JSC-Safety-Report- Submittals@mail.nasa.

gov>

OSHA logs Yearly by Feb 15 and within 30 days of contract end

2.7.2.b Send to Safety and Test Operations Division OSHA 300 & 300A with names removed. Equivalent forms from contractor database are acceptable.

SHETrack Within 5 working days of discovery

3.1, 3.11 Applies to hazards not corrected within 3days

Interim and Final Abatement Plans Within 5 working days of discovery

3.11.2 Updates for hazards

entered into HATS

Details: Address the following items in your plan:

MANAGEMENT LEADERSHIP AND EMPLOYEE PARTICIPATION

Management and employees work together as a team to provide a safe and healthful workplace. Management and employee synergies often must work together across contractual lines.

1.1 Policy: Provide the Contractor’s safety and health compliance policy statement with the plan. Compare the Contractor’s policy statement with those of NASA and OSHA and discuss any differences.

1.2 Goals and Objectives. Describe your approach to the following:

1.2.1 Specific annual safety and health goals and objectives to be met. Include innovative employee input systems and management approaches that produce a measurable rate of improvement in employee participation. These goals and objectives may or may not be quantifiable. Explain how you will evaluate your accomplishment of these goals and objectives.

1.2.2 Methods to be used, if any, to improve on the Days Away Case Rate (DACR), the Total Recordable Injury Rate (TRIR), and the total Days Away plus Restricted Duty plus Job Transfer (DART).

1.3 Management Leadership. Describe how management will demonstrate its commitment to safety and health compliance through visible management activities and fulfill its line management responsibilities for safety and health. Describe specific processes and techniques for implementation in all Contract and subcontract activities and products. Include a statement from the project manager or designated safety official indicating that the plan will be implemented as approved and that the project manager will take personal responsibility for its implementation.

mailto:Submittals@mail.nasa

1.4 Employee Involvement. Describe procedures to promote, implement, and sustain employee (non- supervisory) involvement in safety and health compliance program development, implementation and decision- making from all areas of the contract.

1.5 Assignment of Responsibility. Describe line and staff responsibilities for safety and health program implementation.

Identify any other personnel or organizations that provide safety services or exercises any form of control or assurance in these areas. As a minimum, the plan will identify the following:

1.5.1 Safety Representative - identify by title, the individual who will be responsive to Center-wide safety, health and fire protection concerns and goals, and who will participate in various joint meetings, forums, and other activities related to the JSC Safety and Health program.

1.5.2 Company Physician/Occupational Injury/illness case manager - identify a point of contact who is responsible for the transfer or receipt of company medical data and who will be the primary contact for the company in the event any employee suffers a work related injury or illness by name, address, and telephone number to the JSC Clinic, mail code SD32. This will facilitate communication of medical data to Contractor management. Promptly notify the JSC Clinic of any changes that occur in the point of contact.

1.5.3 Building Fire Wardens - provide a roster of fire wardens at the start of each Contract year (their names, telephone numbers and pagers, and mail codes). Contractor fire wardens facilitate the JSC fire safety program, including coordination of related issues with NASA facility managers and emergency planning and response officials and their representatives. Fire wardens will be trained per JPR 1700.1. Update the Roster by letter to the JSC Safety and Test Operations Division, mail code NS2, with copies to the Contracting Officer and the COR. Provide the initial letter to the Government not later than 15 days after contract start.

1.5.4 Designated Safety and Health Official - identify by title the official(s) responsible for implementation of this plan and all formal contacts with regulatory agencies and with NASA.

1.6 Provision of Authority. Describe your approach to maintain consistency of this plan throughout the life of the contract with applicable NASA and JSC requirements and contractual direction as well as applicable Federal, State, and Local regulations.

1.7 Accountability. Describe procedures for ensuring that management and employees will be held accountable for implementing their tasks in a safe, healthful, and environmentally compliant manner.

1.8 Safety and Health Program Self Evaluation. Describe your approach to safety and health program evaluation. The program evaluation consists of providing a written self-evaluation report once per year that assesses your safety and health program effectiveness during the report period. The self-evaluation shall:

a. Follow the VPP program evaluation report format found in OSHA CSP 03-01-003, Voluntary Protection Program (VPP): Policies and Procedures Manual, Appendix C, “Format for Annual Submissions”, as mandated by the cognizant OSHA regional office.

b. Assess the elements of the approved safety and health plan as a minimum.

c. Include safety and health concerns and resolutions relating to JSC operations which may have been identified during the report period.

d. Include unresolved safety and health concerns relating to JSC operations which the Contractor feels merit attention of JSC safety and health management.

e. Include action plans with schedule for periodic progress reports to the Government on a frequency agreed to by the Government and the Contractor for each problem area.

f. Establish goals and objectives of the Contractor safety and health program for the next report period.

Note: Contractors who have submitted a written self-evaluation as a VPP site may submit their original report to NASA in lieu of writing a new self-evaluation provided that all action plans and status are updated.

Note: This self-evaluation is not the same as the Contractor performance self-evaluation but may be used for that purpose if specifically required by the contract.

1.9 Miscellaneous Deliverables. The Contractor will acknowledge the following as standing requests of the Government and to be handled as described below.

1.9.1 Roster of Terminated Employees. Identify personnel terminated by the contractor. At the contractor’s discretion, the report may include personnel changes during the previous year or cumulated for all years. Information required:

a. Date of report, Contractor identity, and Contract number.

b. For each person listed, provide name, social security number, and date of termination.

c. Name, address, and telephone number of Contractor representative to be contacted for questions or other information.

1.9.2 Material Safety Data Sheets (MSDS)/Safety Data Sheets (SDS). Prepare or deliver MSDSs/SDSs for hazardous materials brought onto Government property or included in products delivered to the Government as required in chapters 9.1 and 9.2 of JPR 1700.1.

1.9.3 Hazardous Materials Inventory. Compile an inventory report of all hazardous materials it has located on Government property quarterly as required by chapter 9.2 of JPR 1700.1, and which is within the scope of 29 CFR 1910.1200, “Hazard Communication”; and Federal Standard 313 (or FED-STD-313), “Material Safety Data, Transportation Data and Disposal Data for Hazardous Materials Furnished to Government Activities”, as revised.

1.10 Government Access to Safety and Health Program Documentation. Include a statement that you will make all safety and health documentation (including relevant personnel records and medical records) available without impediment for inspection or audit to Government safety and health professionals and their representatives. Electronic access by the Government to this data is acceptable as long as Privacy Act and information security requirements are met. For the purpose of this plan, safety and health documentation includes but is not limited to: logs, records, minutes, procedures, checklists, statistics, reports, analyses, notes, or other written or electronic document which contains in whole or in part any subject matter pertinent to safety, health, or emergency preparedness.

1.11 Review and Modification of Safety Requirements. Recognize in the plan that you may be requested to participate in reviewing and modifying safety requirements that are to be implemented by the Government. This review activity will be implemented at the direction of the COR per established contractual procedures.

1.12 Procurement. Identify procedures used to assure that procurements are reviewed for safety and health compliance considerations and that subcontracts contain appropriate safety criteria and instructions. Include authority and responsibility to assure that NASA safety requirements and tasks are clearly stated (flowed down) in subcontracts.

1.13 Certified Professional Resources. Discuss your access to certified professional resources for safety and health protection and discuss their roles in your safety and health program.

WORKSITE ANALYSIS

Worksite analysis identifies hazards and other safety and health threats to employees and valuable assets. As a minimum, analysis will include primarily the following: developing job hazard analyses for its employees; provisions to protect is employees from hazards in their work areas; inspections of the workplace; investigations of mishaps and close calls; and the submission of safety and health data to the Government.

2.1 ANALYSIS OF Worksite Hazards. . Describe how you will rank, process, and mitigate hazards identified by any of the techniques identified per JPR 1700.1 and ensure that all hazards on NASA property, which are immediately dangerous to life or health, are reported immediately to the Safety and Test Operations Division. For administrative contracts, this is covered by a Job Hazard Analysis for office workers. JSC recommends that the Contractor use the office job hazard analysis at https://jsc-sma-missp.jsc.nasa.gov/sites/safety/SH%20%20Hazards/OfficeJHA.pdf to establish its office safety program. The template may be amended as need; Review the Office JHA periodically with contract personnel and update it as needed. Document and track the reviews so that each contract employee’s review is fully demonstrated.

2.1.1 Hazards from nearby operations not in the Contractor’s control. Describe how you will assess nearby hazardous operations for potential threats to its employees and establish controls for their mitigation.

2.2 Industrial Hygiene. Describe your industrial hygiene program and how it will be coordinated with the JSC authorities responsible for industrial hygiene at JSC-administered installations. If you use corporate resources to determine workplace exposures, provide copies of all monitoring data to JSC Occupational Health Branch within 15 days of receipt of results.

2.3 Hazard Identification. Describe the procedures and techniques to compile an inventory of hazards associated with the work to be performed on this Contract to include operations and work environments in the vicinity or in close proximity to Contract operations. Report the results to the Government in a manner suitable for inclusion in facilities baseline documentation as a permanent record of the facility. Specific techniques to be considered include:

a. Comprehensive Survey - A “wall to wall”…