RFP J.1.(a).3 Data Requirements Descriptions (DRD) Amd01.docx

80ARC023R0006 Attachment J.1.(a).3

DATA REQUIREMENTS DELIVERABLES (DRD)

Attachment J.1.(a).3

CONTRACT DATA REQUIREMENTS LIST

National Aeronautics and Space Administration AMES Research Center

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.

4 - The Government will evaluate the Offeror’s initial submission of the Safety and Health (S&H) Plan for acceptability in accordance with the RFP. If a plan is determined to be acceptable and Code QH functionally approves it then it shall be incorporated into the contract as a Section J Attachment at time of contract award. For subsequent submissions of the S&H Plan during contract performance, the submittal shall be considered to be functionally approved if the Contractor does not receive a notification that the plan is unacceptable or an extension request from NASA within 45 calendar days of the submission date of the plan.

5 – Code QH will review the Offeror’s initial submission of the Safety and Health (S&H) Plan for acceptability and provide functional approval of the S&H Plan. The plan shall not be incorporated into the contract. For subsequent submissions of the S&H Plan during contract performance, the submittal shall be considered to be functionally approved if the Contractor does not receive a notification that the plan is unacceptable or an extension request from NASA within 45 calendar days of the submission date of the plan.

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.

STATEMENT OF GENERAL REQUIREMENTS

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

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

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

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

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

Transmittal Data shall be transmitted to NASA by email or other mechanism agreed to by the Contracting Officer (CO), Contracting Officer’s Representative (COR), and project representatives who are responsible to receive, index, and store the data deliverables.

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

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

1. Data Requirements Description (DRD) number

2. DRD data type

3. Submission date or milestone being satisfied

4. Document number and revision

5. Document title

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

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

Final: within 3 months after the end of contract

See DRD

Final: 1 week prior to the end of the contract

1. DRD Title: Initial Financial Management Report (NF 533I)

6. Date Issued: Insert the date the baseline was issued.

S&MA ☐

9. Description/Use: The initial report provided by the contractor shall reflect the original Task Order (TO) value detailed by negotiated reporting categories and be the original TO baseline plan. This plan, plus authorized changes, is subsequently used in columns 7b and 7d of the NF 533 M for comparison of actual to planned cost. The NASA Contracting Officer may require additional detail, such as quarterly or semiannual phasing over the life of the TO, inclusion of unexercised options, or an initial report whenever options are exercised.

10. Distribution: Electronic submittal to:

Initial Submission: The contractor shall submit an initial financial management report in the NASA Form 533Q format in accordance with NPR 9501.2E within 30 working days after TO initiation. Initial reports shall be generated for each individual TO.

Submission Frequency: Once

Format: NASA Form 533Q computer generated version in accordance with the instructions on the reverse side of the form and NASA Procedural Requirements (NPR) 9501.2E. Reporting categories will be specified by the CO at time of award of each individual TO.

Interrelationship: PWS 2.1.1, NFS 1852.242-73 NASA Contractor Financial Management Reporting

Applicable Documents: NPD 9501.1I, NASA Contractor Financial Management Reporting System; NPR 9501.2E, NASA Contractor Financial Management Reporting

Scope: Provides accounting and break out of actual and planned costs for initial TO(s)

OPR: CP

Contents: Reporting categories shall be elements of cost including direct labor hours; direct labor costs; overhead; other direct costs (ODCs), G&A; total costs; fee; total cost-plus fee. ODCs shall be delineated in separate categories for travel, conference registration, training, material purchases, and each subcontract. All of the above data is to be submitted for the reporting period, the cumulative periods, the Government Fiscal Year cumulative, and the estimated costs to completion. Specific levels of reporting shall be identified for each task order. Formats will be specified by the Contracting Officer.

Remarks: NA

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

1. DRD Title: Monthly Financial Management Report (NF 533M)

6. Date Issued: Insert the date the baseline was issued.

S&MA ☐

9. Description/Use: The NF 533M is a report which provides monthly data on actual and planned costs and labor hours, short-term cost projections, estimates to complete, and contract values.

Reporting categories shall be elements of cost including direct labor hours; direct labor costs; overhead; other direct costs (ODCs), G&A; total costs; fee; total cost-plus fee. ODCs shall be delineated in separate categories for travel, conference registration, training, material purchases, and each subcontract. All of the above data is to be submitted for the reporting period, the cumulative periods, the Government Fiscal Year cumulative, and the estimated costs to completion. Specific levels of reporting shall be identified for each task order.

Initial Submission: One month after initiation of initial TO(s)

Submission Frequency: Monthly- no later than the 10th business day after each full month of service or prior to submitting a voucher for the corresponding period.

Format: NASA Form 533M computer generated version in accordance with the instructions on the reverse side of the form and NASA Procedural Requirements (NPR) 9501.2E. Reporting categories will be specified by the CO at time of award of each individual TO and may require further breakout by organization or subtask (project).

Interrelationship: PWS 2.1.1, NFS 1852.242-73 NASA Contractor Financial Management Reporting

Applicable Documents: NPD 9501.1I, NASA Contractor Financial Management Reporting System; NPR 9501.2E, NASA Contractor Financial Management Reporting, at URL http://nodis3.gsfc.nasa.gov/npg_img/N_PR_9501_002E_/N_PR_9501_002E_.pdf

Scope: Provides accounting and break out of actual and planned costs for each CTO and projects supported by the TOs.

OPR: CP

Contents: Reporting categories shall be elements of cost including direct labor hours; direct labor costs; overhead; other direct costs (ODCs), G&A; total costs; fee; total cost-plus fee. ODCs shall be delineated in separate categories for travel, conference registration, training, material purchases, and each subcontract. All of the above data is to be submitted for the reporting period, the cumulative periods, the Government Fiscal Year cumulative, and the estimated costs to completion. Specific levels of reporting shall be identified for each task order. Formats will be specified by the Contracting Officer.

Remarks: Variances under and exceeding 5 percent between planned dollars and actual dollars for each reporting category (at the total contract level only) shall be explained. (Reasonable variance explanation includes the issue, monthly and/or total impacts, corrective actions and dates.)

1. DRD Title: Quarterly Financial Management Report (NF 533Q)

6. Date Issued: Insert the date the baseline was issued.

S&MA ☐

9. Description/Use: The NF 533Q is a report which provides quarterly time-phased cost and labor hour estimates.

**NOTE- NF 533Q reporting may be waived by the NASA Contracting Officer, with concurrence by the Center Chief Financial Officer and cognizant Project Manager, when NF 533 M reports and other data are sufficient to ensure accurate monthly cost accruals, track the contractors' actual cost against plans, and forecast resource requirements. Waivers will be determined at the TO level.

10. Distribution: Electronic submission to:

Initial Submission: End of first quarter of TO performance

Submission Frequency: Quarterly- not later than the 15th day of the month preceding the quarter being projected.

Format: NASA Form 533Q computer generated version in accordance with the instructions on the reverse side of the form and NASA Procedural Requirements (NPR) 9501.2E. Reporting categories will be specified by the CO at time of award of each individual TO and may require further breakout by organization or subtask (project).

Interrelationship: PWS 2.1.1, NFS 1852.242-73 NASA Contractor Financial Management Reporting

Applicable Documents: NPD 9501.1I, NASA Contractor Financial Management Reporting System; NPR 9501.2E, NASA Contractor Financial Management Reporting

Scope: Provides quarterly accounting and breakout of TO and project costs.

OPR: CP

Contents: Reporting categories shall be elements of cost including direct labor hours; direct labor costs; overhead; other direct costs (ODCs), G&A; total costs; fee; total cost-plus fee. ODCs shall be delineated in separate categories for travel, conference registration, training, material purchases, and each subcontract. All of the above data is to be submitted for the reporting period, the cumulative periods, the Government Fiscal Year cumulative, and the estimated costs to completion. Specific levels of reporting shall be identified for each task order. Formats will be specified by the Contracting Officer.

Remarks: Variances more than +/- 5 percent between planned dollars and actual dollars for each reporting category (at the total contract level only and at the TO level only) shall be explained. (Reasonable variance explanation includes the issue, monthly and/or total impacts, corrective actions and dates.).

1. DRD Title: Monthly and Final Technical Reports

6. Date Issued: Insert the date the baseline was issued.

S&MA ☐

9. Description/Use: The Contractor shall submit separate monthly progress reports for each Task Order of all work accomplished during each month of contract performance, and a final report at the conclusion of the work for contract management and each task order. Reports shall be in narrative form. The Contractor shall submit the reports no later than the 15th calendar day of the month following the month to be reported. The monthly progress reports should discuss business, management, and technical aspects. No monthly report need be submitted for the final month of the contract effort since that month will be covered in the final report. The final reports shall be submitted within 15 calendar days after the completion of each Task Order under the contract.

10. Distribution: Electronic submittal to:

Initial Submission: 15th calendar day after the 1st month after phase in

Submission Frequency: Monthly Report: NLT the 15th calendar day of the following month to be reported Final Report: 15 calendar days after the completion of each Option Period or the completion of a TO

Format: The reports shall contain at a minimum the following:

(1) a status summary in narrative form;

(2) changes in cost or schedule;

(3) any current or anticipated issues or problems which may impede performance, and recommended actions to resolve these for both the Government and the Contractor;

(4) monthly staffing data:

a) Changing staffing levels

b) Long- or short-term absences

c) Unfilled positions and durations

d) Contractor and Subcontractor employee name, which TO the employee is working under (for Identity Management & Account Exchange (ldMAX) system validation purposes)

(5) a schedule of all personnel with on-call support responsibilities, including phone number and email address, along with their dates of assignment. The schedule shall be updated and submitted to the CO and the COR within 1 working day after any subsequent changes.

(6) Status of deliverables and milestone schedules and list of deliverables not delivered in compliance with contractual requirements with proposed corrective action; and

(7) any other Information required by reference documents.

Interrelationship: PWS 2.1.1

Applicable Documents: NA

Scope: The document will provide a formal record of monthly technical status.

OPR: JA

Contents: See “Format”

1. DRD Title: IT Security Management Plan

4. Solicitation No.: 80ARC023R0006

5. Contract No.: TBD

6. Date Issued: Insert the date the baseline was issued.

S&MA ☐

9. Description/Use: The Contractor shall prepare and submit an IT Security Plan for Government approval in accordance with NFS clause 1852.204-76 within 30 days after contract award. The Contractor shall submit the IT Security Management Plan to the CO and COR for review and approval, and incorporation into the contract, any updates to this plan necessary during the performance of the contract shall require approval by the CO prior to implementation.

10. Distribution: Electronic submittal to:

Initial Submission: Within 30 days after contract award.

Submission Frequency: See item 9

Format: Plan shall be submitted in Microsoft Word Format

Interrelationship: PWS 2.1.1; Section I, NFS 1852.204-76 Security Requirements for Unclassified Information Technology Resources.

Applicable Documents: Section I, NFS 1852.204-76 Security Requirements for Unclassified Information Technology Resources.

Scope: Critical to assuring the security of NASA IT systems.

OPR: I

Contents: See Item 9. Contractor Format acceptable.

1. DRD Title: IT Security Training Progress Report

4. Solicitation No.: 80ARC023R0006

5. Contract No.: TBD

6. Date Issued: Insert the date the baseline was issued.

S&MA ☐

9. Description/Use: On the final day of each month, the Contractor shall provide a monthly listing of contractor employees who have completed the Information Technology (IT) security training during that fiscal year, which is mandatory for all federal employees, contractors, students and associates who use NASA Federal IT assets and information.

10. Distribution: Electronic submittal to:

Initial Submission: 90 days after Contract Award

Submission Frequency: Monthly

Format: Plan shall be submitted as an Excel document listing status and due dates for training for each individual.

Interrelationship: PWS 2.1.1; NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources

Applicable Documents: NFS 1852.204-76, Security Requirements for Unclassified Information Technology Resources

Scope: Provides up to date list of employee status as regards IT security training, which is critical to assuring continued access to IT resources by contractor employees.

OPR: I

Contents:

The report shall include a listing of personnel who still require the training and the due dates for each individual. This applies to both supervisory and non-supervisory personnel and is available through the System for Administration, Training, and Educational Resources for NASA (SATERN) at https://satern.nasa.gov.

Remarks: An individual’s failure to meet the training deadline will result in his or her computer system’s being disconnected from the network.

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

6. Date Issued: Insert the date the baseline was issued.

S&MA ☐

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

10. Distribution: Electronic submission to:

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

Submission Frequency: Update annually

Format: Contractor’s format is acceptable.

Interrelationship: PWS 2.1.1

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

Scope: In support of the Executive Order 13985, Advancing Racial Equity and Support for Underserved Communities Through the Federal Government, NASA is seeking to advance equity or remove barriers for members of underserved communities to access procurement opportunities. Underserved communities refer to populations sharing a particular characteristic, as well as geographic communities, that have been systematically denied a full opportunity to participate in aspects of economic, social, and civic life. Underserved Communities include Black, Latino, Indigenous, Native American, Asian Americans and Pacific Islanders and other persons of color; members of religious minorities; lesbian, gay, bisexual, transgender, and queer (LGBTQ+) persons; persons with disabilities;

persons who live in rural areas; and persons otherwise adversely affected by persistent poverty or inequality.

OPR: JA

Contents:

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

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

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

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

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

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

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

2. How will underserved communities be leveraged?

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

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

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

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

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

Remarks: N/A

1. DRD Title: Phase-Out Plan

4. Solicitation No.: 80ARC023R0006

5. Contract No.: TBD

6. Date Issued: Insert the date the baseline was issued.

S&MA ☐

9. Description/Use: At the end of the period of performance of this contract, the Contractor is responsible for the orderly transfer of all Government Furnished Property, duties, and records to NASA. This shall be accomplished in an expeditious manner, consistent with the phase-in schedule of the successor Contractor, while precluding interruption to the scheduled requirements in the CLINs and TOs.

10. Distribution: Electronic submittal to:

Initial Submission: The Contractor shall submit a phase-out plan no later than 60 days before the end of the contract for government review and approval.

Submission Frequency: One submission only. The Contractor shall submit a phase-out plan no later than 60 days before the end of the contract for government review and approval.

Format: Word document with any required records to be transferred

Interrelationship: PWS 2.1.1, FAR 52.237-3 Continuity of Services

Applicable Documents: N/A

Scope: Critical to continuity of work at the end of the contract.

OPR: JA

Contents:

The Plan shall address issues pertinent to the continuation of safe operations for all areas of responsibility under the contract. All standard operating procedures and documentation developed during this contract that are needed to successfully operate systems, perform job functions, and complete tasks in progress on the contract, shall be provided as part of the phase out plan.

1. DRD Title: Safety and Health Plan

4. Solicitation No.: 80ARC023R0006

5. Contract No.: TBD

6. Date Issued: Insert the date the baseline was issued.

S&MA ☒

9. Description/Use: The detailed Safety and Health (S&H) Plan shall state how the contractor intends to protect the life, health, and well-being of the public, and NASA and contractor employees as well as property and equipment. The contractor shall abide by the approved Safety and Health Plan in performance of contractual requirements conducted completely or partly on a Federally controlled facility. S&H Plan shall be consistent with the proposed technical approach, cost/price, and contractual requirements.

10. Distribution: Electronic submittal to:

Initial Submission: The initial submission shall be 15 calendar days after the effective date of the contract.

Submission Frequency: Contractor shall review annually and revise as necessary if contractual requirements, processes used by the contractor, or conditions change that warrant a change to the S&H Plan Format: Word document

Interrelationship: PWS 2.1.1, Safety and Health Plan, NFS 1852.223-70 Safety and Health Plan

Applicable Documents: APR 8715.1 Ames Health and Safety Manual

Scope: The contractor will develop and subsequently implement a safety and health program based on the approved S&H Plan and applicable requirements in the PWS that will include policies and procedures for compliance with pertinent NASA policies and requirements, and Federal, State and local regulations for safety, health, environmental protection, and fire protection. The contractor's Safety and Health Program will be used to assure integration of the contractor as a full participant in the Center's Safety and Health Program.

OPR: Q

Contents:

Title: Safety and Health Plan for the ASSESS Contract

1.0 INTRODUCTION

List the work activities to provide context for the essential elements of an effective safety program by checking all of the following that apply to the proposed work:

☐ Office work ☐ Hazardous chemical use ☐ Hazardous noise exposure ☐ Use of biohazardous materials ☐ Use of nanomaterials ☐ Use of explosives or propellants ☐ Use of radioactive materials ☐ Use of high energy lasers ☐ Field work in extreme environments ☐ Use of pressure systems ☐ Use of lifting devices ☐ Use of aircraft (including UAVs) ☐ Construction of buildings or research facilities

2.0 MANAGEMENT LEADERSHIP AND EMPLOYEE PARTICIPATION

2.1 Office Safety

2.1.1 Policy: Provide the contractor's corporate safety policy statement.

2.1.2 Management Leadership: Describe the process and procedures for implementing management commitments to safety and health through visible activities and initiatives.

2.1.3 Employee Involvement: Describe procedures to implement and promote employee (e.g., non-supervisory) involvement in safety and health program development, implementation, and decision making.

2.1.4 Assignment of Responsibility: Describe the line and staff responsibilities for safety and health program implementation.

2.1.4.1. Designated Safety Official: Identify, by title, the official(s) responsible for implementing the proposed Safety and Health Plan. This individual will be the official designated as the company representative for all formal contacts with regulatory agencies that concern the company’s employees.

2.1.5 Accountability: Describe the procedures for ensuring that management and employees will be held accountable for implementing their tasks in a safe and healthful manner. The use of traditional and/or innovative personnel management methods (including discipline, motivational techniques, or any other technique that ensures accountability) should be referenced, as a minimum, and described, as appropriate.

2.2 Labs, shops, and research facility support:

For contracts that include work with hazards beyond those found in an office setting, include the following information in addition to the topics covered in section 2.1. If this section does not apply to this section, insert N/A and an explanation of why it does not apply.

2.2.1 Program Evaluation: Describe the method to be used for internal program reviews and evaluations. Consider using OSHA guidance at OSHA CSP 03-01-005, Voluntary Protection Program (VPP): Policies and Procedures Manual.

2.2.2 Program Documentation. Describe the approach to be taken to document its safety and health program performance and maintain records required by OSHA.

2.2.3 Procurement: Describe how safety and health requirements will be stated in subcontracts. Describe methods that will be used to assure that specifications for purchases of equipment contain appropriate safety criteria and instructions. Describe procedures for purchases of hazardous materials. Identify procedures used to comply with the requirement in APR8715.1 Chapter 24, Hazard Communication, to assure that the contractor's hazardous material purchases are reviewed by a competent person for safety considerations.

2.2.4. Safety Data Sheets and Hazardous Chemical Inventory: Prepare a written program as required by OSHA 29 CFR 1910.1200 and include it as an appendix to this safety and health plan if any hazardous materials will be acquired under this contract. Describe the procedure to be used by the contractor to maintain a hazardous material inventory and make Safety Data Sheets available to employees for hazardous materials brought onto NASA Ames Research Center (ARC) or included in products delivered to the Government.

3.0 WORKPLACE ANALYSIS

3.1 Office Safety:

3.1.1 Inspections: This section should include the procedures and frequency for regular inspections and evaluations of work area hazards and who will be accountable for implementing corrective measures.

3.1.2 Employee Reports of Hazards: Identify the methods to be used to encourage employees to report hazardous conditions (e.g., close calls) and analyze/abate hazards. Describe steps to be taken to create reprisal-free employee reporting with emphasis on management support for employees.

3.2 Labs, Shops, and Research Facility Support:

For contracts that include work with hazards beyond those found in an office setting, include the following information in addition to the topics covered in section 3.1.

3.2.1 Hazard Identification: Describe the procedures and techniques to be used to identify hazards associated with the work to be performed on this contract. Consider the work specified in the contract as well as the hazards associated with operations and work environments in close proximity to contract operations. Describe the information collection process including a combination of surveys, analyses, inspections of the workplace, investigations of mishaps and close calls, and the collection and trend analysis of safety and health data such as records of occupational injuries and illnesses; findings and observations from preventive maintenance activities; reports of spills and inadvertent releases to the environment; facilities-related incidents related to partial or full loss of systems functions; and employee reports of hazard.

3.2.2 Hazards addressed in the Ames Safety and Health Manual: Evaluate the applicability of chapters in the Ames Safety and Health Manual (APR 8715.1) to the anticipated work activities under the contract. Include the table below that has been completed for the Contractor’s proposed approach as an Appendix to the S&H Plan.

*Applicable, Yes or No?

*Note: Contractor/Offeror to state “yes” or “no” based on whether or not the relevant chapter of APR 8715.1 is applicable to the safety and health program, stated in the S&H Plan, it proposes to use in performance of the contractual requirements.

3.2.4 Systems Safety: Identify all safety engineering products, which address operations, equipment, and other aspects of safety engineering, on Federally-controlled facilities that will be developed/used under this contract. (Note: All safety engineering products, which address operations, equipment, and other aspects of safety engineering, on NASA property will be subject to the review and concurrence of the ARC Safety Office unless otherwise specified in the approved safety and health plan.)

4.0 MISHAP INVESTIGATION AND RECORD ANALYSIS

4.1 Mishap Investigation and Reporting: Identify the methods to assure that the investigations and reporting of mishaps including corrective actions to be implemented to prevent recurrence. Describe procedures for implementing the NASA mishap investigation and reporting requirements for electronic reporting in the Contractor Monthly Accident Reporting data system and the NASA Mishap Information System, in accordance with NFS Clause 1852.223-70.