Flight Deck Collaborative Decision Making Phase III.pdf

PERFORMANCE WORK STATEMENT

Flight Deck Collaborative Decision Making (CDM) Research Project

Phase III

1. Background The purpose of the Flight Deck Collaborative Decision Making (CDM) Research Project is to improve aircraft surface movement by creating a seamless flow of data to stakeholders to support effective decision making. This will increase operational efficiency by reducing repetitive taxi instructions and open the door to delivering more innovative applications leveraging Electronic Flight Bags (EFB). This requirement will be for the NASA Ames Research Center. Phase 1 work looked at feasibility of using vendor off the shelf (baseline) speech to text models and compute performance metrics (word error rate) across different baseline models. The current Phase 2 included services that collected extensive taxi audio and build a custom speech to text model. The current Phase 2 work includes automated speech to text transcription of taxi audio, extraction of taxi instructions from the transcript (text) and conversion of text taxi instructions to digital taxi instructions in a format that is accepted by the EFB app. The end-to-end pipeline is being made available on APPDAT - a NASA approved IT cloud infrastructure.

2. Objective/Requirements

The goal of Flight Deck CDM exploratory project is to: (1) digitize the analog Very High Frequency (VHF) Taxi-to commands, (2) live translate with a custom Google Speech-to- Text model, (3) publish that digital taxi instruction to the pilot via their EFB and Air Traffic Control (ATC) via an Enterprise Agreement for Public Sector Subscription access to all Google Cloud Platform Solutions (9A92-40AE-8D00).

The work is being accomplished in phases as feasibility and direction are assessed. This next phase III of work seeks to refine the accuracy of the model and improve the interface for EFB usability.

Requirements:

Part Number Description Quantity CP-PROF-SVC-CREDITS ARC Flight Deck Collaborative

Decision Making (CDM) Research Project - Google Cloud Platform (GCP) Professional Services - Part

III

3. Characteristics, Scope, and Specs

The Contractor shall provide the following services (ANC-PROF-SVC-PWK):

A. Strategic Program Enablement

1. Engage with key program stakeholders (kick-off meeting, bi-weekly status meetings) to define goals, gather requirements, and establish expected outcomes of the program reflected in a Program Charter.

2. Conduct and lead regular program status meetings with NASA to assess progress against program timelines and identify key risks and issues to be addressed, along with any decisions or change requests that need to be made.

3. Provide a high-level word or ppt document of deployment activities to be completed based on vendor’s leading practice methodology and team input.

4. Provide a single view into the Customer Workspace and Cloud Platform projects, acting as a primary focal point for cloud strategy.

5. Identify, track and report on appropriate milestones and Key Performance Indicators (KPIs) in meetings to measure success and to further refine the Customer’s cloud strategy.

6. Identify and coordinate resolution of risks and issues during the engagement by actively engaging with stakeholders in meetings to support removal of potential blockers and mitigate impacts to program timelines.

7. Identify Customer product needs and advocate for feature requests with vendor product management and engineering teams.

8. Conduct detailed, use-case specific reviews as requested (ppts for quarterly meetings) along with vendor’s subject matter experts of architecture designs to address technical inquiries and advise on speech-to-text leading practices.

9. Coordinate program resources to help ensure the right engagement at the right time from the teams and individuals who will contribute to the project’s success.

10. Run an end-of-program review and document in a report successes and improvements.

B. Phase III

1. Contractor shall provide professional services to further refine the proof-of-concept model:

a. Continue to participate in bi-weekly and status review meetings as required.

b. Continue to consolidate, ingest, and prepare data to prepare for design review.

c. Continue to refine custom speech-to-text language model by training on transcribed audio datasets from KTPA and other airport locations.

d. Continue to refine DTI model that converts text containing single valid taxi instruction to digital format that can be ingested by BCI

e. Participate in TBD Readiness Review at FAA location.

f. Participate in TBD Design Review Test/HITL Demonstration at FAA location.

i. STT API will process 3-5 live spoken taxi instructions, convert to digital format, send to BCI to verify instruction validity, and display on map.

g. Document in report (word report and/or ppt) all prototype functionalities, design and technical challenges, test results, including measurement criteria, and lessons learned and recommendations for real world implementation.

2. Contractor shall provide access to a cloud computing environment where data is to be stored and computed.

a. Continue to participate in kick-off, bi-weekly, and status review meetings as required. Document (word or ppt) status and plans as required.

b. Includes possible setup and deployment of data collection at new airport location(s) TBD by customer, including necessary hardware.

c. Includes collecting audio samples, building data pipelines to ingest data into

Google Cloud Platform.

d. Includes custom modeling for creating language and DTI models,

e. Includes further testing validation and documentation.

3. Contractor shall provide access to a cloud computing environment where data is to be stored and computed.

4. Contractor shall participate and prepare for demonstrations as required.

5. Contractor shall document (word and/or ppt) assessment of demonstrations.

4. Deliverables

Deliverable Reference Description/Acceptance Criteria

Date

Phase III Deliverable 1

B.1.a Bi-weekly Status Reports (word and/or ppt) to include progress against program timelines, key risks and issues to be addressed, decisions or change requests, and progress on milestones and KPIs

Bi-weekly

Phase III Deliverable 2

B.1.e Readiness Review: Participate in meeting with stakeholders to plan and prepare for HITL Demonstration. Travel for 2 persons (Technical Lead and Customer Engagement Lead).

TBD

Phase III Deliverable 3

B.1.f At Design Review #2, HITL Demonstration, which will be used a benchmark for the Proof of Concept, we will need to convert either prerecorded clean instructions or live vocal commands to a DTI string.

Criteria for measuring completeness and accuracy of conversion must be determined and show higher level of completeness, accuracy, and ability to handle complexity.

Travel for 2 persons (Technical

TBD

5. Travel Travel is based on actuals only and reimbursement will only be allowed per the GSA/Market/Per diem rates. Phase III: Travel to Daytona beach, FL will be required for 2 persons (Technical Lead and Customer Engagement Lead) to attend the Readiness Review on TBD and HITL demonstration in March TBD.

6. Place of Performance

Ames Research Center Moffett Field, CA 94035 USA

7. Period of Performance The period of performance shall be for 4 months from the effective award date of TBD. Delivery is expected on or before TBD.

Lead and Customer Engagement Lead).

Phase III Deliverable 4

B.1.g Technical Design Document (word and/or ppts) all prototype functionalities, design and technical challenges, test results, including measurement criteria, and lessons learned and recommendations for real world implementation.

TBD