Surface Report Classifiier (SCM/Auto-Class)

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

2019-01-01 (day precision)Source: 01/01/2019 12:00:00 AM

Withheld from public reporting

NoSource: a) No

Mission

Topic area

Transportation

Operational functions

No function tag matched Derived by keyword rules; see methodology

Problem the AI is intended to solve

To classify surface Mandatory Occurrence Reports (MORs) to reduce the amount of manual event review.

Expected benefits

Not reported

System outputs

Classes - runway excursion, runway incursion, surface incident.

Technology

AI classification

Other

System name(s)

Not reported

Custom-developed code

No

Public source code

Not reported

Sourcing

How it was built

Developed in-houseSource: b) Developed in-house

Vendor (as reported)

Not reported

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

Not reported

Privacy Impact Assessment

No

Authorization to Operate

Yes

Demographic features

Not reported

Training and evaluation data

Manually curated dataset for surface events

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