MUAS for HC RFP Attachment J-17 Performance Standards.pdf

J-17 Page 1 of 4

Attachment J-17

Performance Standards, Metrics, and Surveillance for the Maritime Unmanned Aircraft System

(MUAS) for Host Cutter

The Contractor must satisfactorily perform service in all eight of the performance dimension categories listed in Attachment J-16 Quality Assurance Surveillance Plan (QASP), Enclosure (2) ISR Service

Performance Standards listed below:

1. System Installation

2. Testing

3. UAS Operations

4. Launch Reliability

5. ISR Data

6. Data Entry

7. Sustainment Support

8. System Deinstallation

Amplifying information on performance standards, metrics, and surveillance is below.

PERFORMANCE DIMENSIONS

1. System Installation: No further guidance; review other contract documents as appropriate.

2. Testing: No further guidance; review other contract documents as appropriate.

3. UAS Operations: The Mission Reliability Rate (MRR) (CDRL A001) performance standard will be used to determine whether an acceptable quality level has been achieved for the Intelligence, Surveillance, and Reconnaissance (ISR) service. MRR must be calculated daily by the Contractor for each individual host cutter’s deployment and provided to the Contracting Officer’s Representative

(COR) monthly and at the end of each individual cutter’s deployment for validation and incorporation into the Contractor Performance Assessment Reporting System (CPARS). MRR is the only performance standard that will be used to determine Contractor payment. See the Attachment J-16

QASP, Enclosure 2 ISR Service Performance Standards, Section 2 Performance Requirement for

Payment.

The UAS must be fully mission capable (FMC) at all times and available for host cutter tasking. Any system degradation status, partially mission capable (PMC) status, and not mission capable (NMC) status, will be reflected on the Monthly Surveillance Activity Checklist listed in the Attachment J-16

QASP, Enclosure 3, Surveillance Activity Checklist. All flights scheduled or unscheduled count towards MRR.

For deployment days where ISR flight time is requested by the Government, the following equation must be used by the Contractor to calculate the daily MRR:

𝑀𝑅𝑅(%) =

𝐴

(𝐵−𝐶) *100

A = total ISR flight time performed

B = total ISR flight time requested by the Government

J-17 Page 2 of 4

C = total ISR flight time cancelled or aborted by the Government in accordance with the event status listed in Enclosure (1) Table A, Unsuccessful Dispatch.

For deployment days where ISR flight time is not requested by the Government, the daily MRR will be 100% for an FMC system and 0% for an NMC system. Depending on the nature of the PMC status, it may affect MRR if ISR services are negatively impacted. The Government will not make changes to the ISR flight schedule based on the Contractor’s system status.

The Contractor must be in constant contact with host cutter representatives and the COR to keep them informed of MRR-related problems/concerns and to resolve issues as they arise. Any disputes between the Contractor and the host cutter representatives will be addressed by the COR and/or LNO.

An MRR report must be submitted to the COR monthly and at the completion of each individual cutter’s deployment.

Flight recommendations will be taken from the Contractor; however, the Government has the sole authority to cancel or delay missions.

4. Launch Reliability: The On-time Flight Rate (OFR) (CDRL A001) performance standard will be used to determine whether an acceptable quality level has been achieved for the ISR service. A flight is considered delayed if it launches more than 15 minutes after the Government’s assigned takeoff time, as documented within Asset Logistics Management Information System (ALMIS). OFR must be calculated daily by the Contractor for each individual host cutter’s deployment and provided to the

COR monthly and at the end of each individual cutter’s deployment for validation and incorporation into the CPARS. The following equation must be used by the Contractor to calculate the OFR for the

ISR service performed:

𝑂𝐹𝑅 (%) =

(𝐷−𝐸)

𝐷 *100

D = total number of ISR flights performed

E = total number of ISR flights delayed by the Contractor in accordance with the event status listed in

Enclosure (1) Table A, Unsuccessful Dispatch

The Contractor must be in constant contact with host cutter representatives and the COR to keep them informed of OFR-related problems/concerns and to resolve issues as they arise. Any disputes between the Contractor and the host cutter representatives will be addressed by the COR and/or LNO.

The OFR metric must be submitted to the COR monthly and at the completion of each individual cutter’s deployment.

5. ISR Data: No further guidance; review other contract documents as appropriate.

6. Data Entry: ISR flight time must be recorded by the Contractor within the Government’s Electronic

Asset Logbook (EAL) within ALMIS for the ALMIS Records performance standard. The Contractor is responsible for accurately logging all ISR mission event status to include properly filling out the required pre-flight and post-flight entries. Information entered into ALMIS must be an accurate report of actual operations. ISR flight time must be logged by the Contractor in ALMIS as soon as possible.

The Government is responsible for reviewing / approving all EAL mission events.

J-17 Page 3 of 4

Electronic logs must be provided to the Government to allow for independent verification if requested.

The Contractor must be in constant contact with host cutter representatives and the COR to keep them informed of data entry-related problems/concerns and to resolve issues as they arise. Any disputes between the Contractor and the host cutter representatives will be addressed by the COR and/or LNO.

7. Sustainment Support: No further guidance; review other contract documents as appropriate.

8. System Deinstallation: No further guidance; review other contract documents as appropriate.

J-17 Page 4 of 4

Enclosure (1) Unsuccessful Dispatch

Missions can be canceled, aborted, or delayed for the reasons listed in Table A, Unsuccessful Dispatch below. When a flight is canceled or aborted, and the event status reason is both the responsibility of

Government and the responsibility of the Contractor, the Contractor’s reason takes precedence, and there must be no impact to the denominator of the MRR calculation. The Contractor must be in constant contact with host cutter representatives and the COR to keep them informed of Unsuccessful Dispatch-related problems/concerns and to resolve issues as they arise. Any disputes between the Contractor and the host cutter representatives will be addressed by the COR and/or LNO.

Table A: Unsuccessful Dispatch

Event Status Reason Responsibility of

Government

Responsibility of

Contractor

Cancelled Delayed Aborted

Air Traffic Control X X X X X

Aircraft X X X X

Aircraft (ditched / unrecoverable)

X X

ALMIS (Kiosk) X X

ALMIS – SWIII X X

Cutter X X X X

LRE / GCS X X X X

Maintenance X X X X

Mission Change X X X X

Operations Other X X X X

Pilots X X X X

Training X X X X

Weather X X X X