Machine Translation
Department of the Treasury · Internal Revenue Service (IRS)
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
- The output is not presumed to be high-impact and is not used as the principal basis for significant decisions/actions
- Start date
- 2023-09-25 (day precision)Source: 9/25/2023
- Withheld from public reporting
- NoSource: a) No
Mission
- Topic area
- Service Delivery
- Operational functions
- Translation and transcription Derived by keyword rules; see methodology
Problem the AI is intended to solve
To better facilitate and automate content translation efforts at the IRS, a cloud-based commercial off-the-shelf (COTS) solution is being leveraged for use by the Linguistic, Policy, Tools and Services (LPTS) Team. The Machine Translation (MT) application is being assessed and evaluated by the primary users, the Linguistic Policy, Tools and Services (LPTS) organization, through integration with their existing processes. The MT application focuses on translation for existing text and labels into Spanish with the ultimate goal of becoming an enterprise solution for a variety of non-English translations.
Expected benefits
Machine translation is used to translate text and file-based content from and to English, Spanish, Chinese (Traditional, Simplified), Korean and Vietnamese used by MAS/LPTS to speed up responses to taxpayers.
System outputs
The MT application focuses on translation for existing text and labels into Spanish and other languages with the ultimate goal of becoming an enterprise solution for a variety of non-English translations.
Technology
- AI classification
- Classical / predictive MLSource: Classical/Predictive Machine Learning: Models trained on data to make predictions or classifications based on identified patterns or relatio…
- System name(s)
- Not reported
- 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)
- 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
- No
- Privacy Impact Assessment
- Not reported
- Authorization to Operate
- Yes
- Demographic features
- k) None of the above
- Training and evaluation data
- Users can provide custom model to override the vendor-generated default translations. Vendor in turn can learn from the custom models that users provide to improve the model.
- 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