NextGen Data Analytics: Letters of Agreement

Overview

Development stage

DeployedSource: c) Deployed – The use case is being actively authorized or utilized to support the functions or mission of an agency.

High-impact designation

Not high-impactSource: c) Not high-impact

Impact justification

Not reported

Start date

Not reported

Withheld from public reporting

NoSource: a) No

Mission

Topic area

Transportation

Operational functions

Document processing and extraction Derived by keyword rules; see methodology

Problem the AI is intended to solve

Today, operation constraints are documented via Standard Operating Procedures (SOP) and Letters of Agreement (LOA) and are not made available to the public in a consistent manner. SOPs are specific to an air traffic control facility and specify the procedures necessary for safe operation in the sector. LOA outline agreements establishing procedures and responsibilities between two parties (including crossing restrictions, holding patters, emergency procedure coordination, etc.) The LOA/SOPs are published internally as scanned PDFs and are the responsibility of the facility to maintain. To reduce the manual effort of tagging the documents for ease of reference, there is an opportunity to use modern data analytics and machine learning to produce and disseminate constraints in a standardized manner.

Expected benefits

Providing LOAs or SOPs to stakeholders will enable flight planners (pilots and vendors) to study or ingest this information and thereby plan flight trajectories that remain consistent with air traffic constraints. It is also fundamental to Next Gen capabilities to share accurate data for purposes of creating new noise abatement procedures; improve NAS information for common situational awareness and alignment to implement new tools to assist in future time-based flow management.

System outputs

Test-based digitized SOPs and LOAs.

Technology

AI classification

Natural language processingSource: Natural Language Processing: AI that processes, interprets, and shares information in human language.

System name(s)

Operated in an approved enclave

Custom-developed code

Yes

Public source code

Not reported

Sourcing

How it was built

Contract and in-houseSource: c) Developed with both contracting and in-house resources

Vendor (as reported)

FAA

Vendors (standardized)

None on the standard list

A vendor is the supplier named by the agency. It does not identify the underlying model or AI technology.

Data and privacy

Involves PII

No

Privacy Impact Assessment

Not reported

Authorization to Operate

Yes

Demographic features

Not reported

Training and evaluation data

documents

Federal Data Catalog

Not reported

Governance

0 of 8 minimum-practice questions answered. A blank answer means the agency reported nothing; it does not mean the practice is absent.

Potential impacts and how they were identified

Not reported