ATTACHMENT I_SDS PWS-20210303_vFinalDraft.pdf

PERFORMANCE WORK

STATEMENT (PWS)

Electronic Safety Datasheet System (eSDS)

March 3, 2021

I eSDS Performance Work Statement

, 2018

Table of Contents

1 Introduction

1.1 Introduction

1.2 Background

1.3 Objectives

1.4 Scope of Work

2 Task Requirements

2.1 Task 1 – Program Management Support

2.1.1 Subtask 1.1 – Monthly Invoicing (CDRL A001)

2.1.2 Subtask 1.2– Monthly Operational Activity Report (CDRL A002)

2.2 Task 2 – Software Licenses

2.3 Task 3 – Software Maintenance

3 End Results/Deliverables

4 Period of Performance

5 Transition/Close Out Plan

6 Service Summary

6.1 Service Summary

6.1.1 Contractor performance:

6.1.2 Surveillance Methods:

6.1.3 Contractor Performance Evaluation:

A-3

1 Introduction

1.1 Introduction

Flight Program Operations, Aircraft Maintenance and Engineering (AME) supports maintenance and engineering for Federal Aviation Administration (FAA) flight operations and other governmental agencies that operate aircraft across the U.S. and abroad. Hazardous Material is stored and used in the course of these activities. AME is pursuing tools to improve available to manage the SDS documentation.

1.2 Background

The Program is currently using a manual process to maintain the current Safety Data Sheet (SDS).

This cumbersome process is no longer efficient, and is difficult to sustain. FAA is pursuing an

“Electronic Safety Datasheet System (eSDS). An automated solution that complies with industry standards and provides a platform to properly, and effectively document regulatory compliance.

AME is currently dependent on the paper SDS system to keep their employees safe while using chemicals during aircraft maintenance functions. There is a requirement to replace the legacy paper SDS system with an electronic system in order to continue operations without interruptions to services.

1.3 Objectives

The objective of this PWS is to outline the requirements for the Commercial Off –The-Self

(COTS) application. The solution must meet the business and operational requirements associated with managing a chemical inventory in accordance with applicable regulations.

1.4 Scope of Work

This PWS describes the scope of work required by the Contract. The Government requires at a minimum, the Contractor must:

Provide software licenses for the solution - Software as a Service (SaaS)

Provide various digital platform access (Web-based, Android, iOS)

Provide for a range of 75 to 150 users with no additional costs to ramp users on or off

Provide a solution that meets the objective of the PWS.

Provide a Deployment Plan for the transition within 30 days of award

Applicable Regulations and Guidance include but are not limited to:

A-4

• CFR14 FAR Part 135

• CFR14 FAR Part 145

• 40 CFR Code of Federal Regulations: Protection of Environment

• 49 CFR Code of Federal Regulations: Hazardous Material Regulations as required by US Department of Transportation (DOT)

• HAZMAT (Transportation by ground) FAA Order 3900.21

• IATA International Air Transport Association – Dangerous Goods Regulation

(HAZMAT Transportation by Air)

• JO 1050.1 Flight Program Environmental Program document

• JO 3900.1 Flight Program Occupational Safety and Health Program

2 Task Requirements

Provide the capability to manage hazardous chemicals, in multiple locations.

Provide the capability to track hazardous chemical entry and removal and must maintain an archive.

Provide user and system administration training. Methods of training may be online or class-room environment.

Provide General HAZCOM training annually as prescribed by applicable Federal regulations.

Methods of training may be online or class-room environment.

Provide the ability or method to highlight emergency procedures at the top/initial chemical splash screen or other method to draw attention to the emergency procedure.

Provide various platforms for access (Web-based, Android, iOS)

Notify AME the same day when updates/deletions are made to the hazardous chemical list, and allow for notification within the homepage of the platform for users

Provide the ability to download SDS documents to desktop or mobile device.

Provide the ability to show chemical list by office location

Provide a method to maintain a backup of all chemicals used by AME.

Provide AME an archived backup copy annually.

Ensure AME meets all paperless requirements and the hazardous chemical archiving requirements.

A-5

Requests for information initiated by the Government or Contractor shall be in writing and submitted electronically via e-mail.

2.1 Task 1 – Program Management Support

The Contractor must provide the Project/ Contract Management required to enable status reports and contract management.

2.1.1 Subtask 1.1 – Monthly Invoicing (CDRL A001)

The Contractor must provide a Monthly Invoice/Financial Report.

2.1.2 Subtask 1.2– Monthly Operational Activity Report (CDRL A002)

A monthly Hazardous Material Activity Report is required. Exact report formatting is negotiable, provided it contains the data needed to monitor workload activity. The COR will review the report format proposed prior to approval. The Government requires at a minimum that the following items be included:

Date Range of reporting period

Hazardous Chemicals added/removed

Date when chemical was added/removed

Date AME Hazardous Chemical list was archived

2.2 Task 2 – Software Licenses

The Contractor shall provide user licenses for the application.

2.3 Task 3 – Software Maintenance

The Contractor will provide the required software maintenance/updates and installation.

Solution must meet industry standard security requirements.

3 End Results/Deliverables

CDRL Deliverables Due Date Acceptance Criteria

A001 Program Management

Support: Monthly

Invoicing

10th business day of the following month

The Monthly Financial Reports (invoicing) compliant with AMS Clause 3.11-28 Contractor’s Invoices.

Deliver reports to COR for acceptance and approval/disapproval.

A-6

A002 Monthly

Operational

Activity Report

10th business day of the following month

COR will evaluate report for approval

Software as a

Service (SaaS) Contract Deployment

Plan

Software solution that meets PWS requirements.

4 Period of Performance

The Period of Performance will consist of one base year and four one-year option periods.

5 Transition/Close Out Plan

Approximately four weeks prior to the Contract end date, the FAA will require the Contractor to provide the following:

All documentation as of the most recent version

A final status report that includes a projection of activities for the remainder of the Contract

A closeout meeting with the FAA (details and participants to be determined by the FAA)

6 Service Summary

6.1 Service Summary

6.1.1 Contractor performance:

Contractor performance shall be measured and assessed, using the Performance Requirements listed in

Table 6-1. The Contractor service requirements are summarized into performance requirements that relate directly to the mission essential items. The performance threshold requirements describe the minimum acceptable levels of service for each requirement. In the event the performance requirement is not met, the Contractor shall be given time after notification to correct the unacceptable performance, if such correction is possible. The Contractor shall immediately take corrective action in accordance with the performance threshold(s). In cases where the Contractor fails to implement corrective action, the PCO will take appropriate measures.

6.1.2 Surveillance Methods:

The PMS/COR and PCO will exercise surveillance over the performance requirements. The absence of any contract requirement from the SS shall not detract from this enforceability nor limit the rights or remedies of the Government under any other provision of the contract. The Contractor shall support the

PMS/COR, and PCO surveillance methods as identified below:

Periodic Inspection of Process or Output

Random Sampling of Recurring Service Output

A-7

100 Percent Inspection of Output

Customer Observation or Compliance

6-1 SERVICE SUMMARY TABLE

Performance Requirements

PWS

Para

Performance Threshold

Requirements

SS-1. All requests for information initiated by the Government or Contractor shall be in writing and submitted electronically via e-mail.

Par. 2 Emergency – respond within 1 business days

Urgent Requests – respond within 3 business days

Routine Requests – respond within 5 business days

SS-2. Each end-item identified as usable shall be delivered to the Government error free.

Par. 2 100% of all end items shall be delivered to the

Government; error free, in useful condition, and in accordance with required standards.

SS-3. Furnish Data requirements that are specified in the Contract Data

Requirements List(s)

Par.

2.1.1

2.1.2

95% of all data provided on time and accurate per the

CDRL.

SS-4. The Contractor shall meet the contractual delivery schedule.

Par. 4 100% of all data sheets are available to the Government

IAW the delivery schedule. All

SS-5. The Contractor shall perform 100% inspection of data sheets and shall report

100% of discrepancies incident to provisions.

Par. 2 100% of inspection of data sheets and report 100% of discrepancies incident to provisioning.

6.1.3 Contractor Performance Evaluation:

The Contractor shall understand that the evaluation of performance will occur when the

PMS/COR evaluates the service of the Contractor to determine whether it meets the performance measures of the contract.

SS-1through SS-5: The Contractor’s failure to meet the requirement for this item may result in an unsatisfactory or marginal rating under the Contractor Performance Assessment Review (CPAR).