AI-Powered Enterprise Standard Portfolio (ESP) for End-to-End Technology Lifecycle
Department of the Treasury · Internal Revenue Service (IRS)
Overview
- Development stage
- In development or acquisitionSource: a) Pre-deployment – The use case is in a development or acquisition status.
- 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
- Not reported
- Withheld from public reporting
- NoSource: a) No
Mission
- Topic area
- Information Technology
- Operational functions
- Chatbot or virtual assistant, Summarization, Procurement and acquisition Derived by keyword rules; see methodology
Problem the AI is intended to solve
The core problem the AI is intended to solve lies in the fragmented and highly manual nature of how commercial off-the-shelf technologies are managed throughout their life cycle. Today, users submit requests for new software or hardware, but determining whether the request duplicates existing tools, whether the technology is still supported, or whether it fits enterprise standards often depends on tribal knowledge, scattered documentation, or siloed teams. This leads to long cycle times, inconsistent risk evaluations, and limited visibility into how many licenses or subscriptions are actually in use. Organizations struggle to manage active and inactive instances across both on-premise and cloud-based environments, making it difficult to optimize costs or ensure that end-of-life and upgrade paths are handled consistently. The lack of seamless hand-offs across cataloging, approval, procurement, deployment, and monitoring workflows contributes further to inefficiency and risk.
Expected benefits
The expected benefits of introducing AI into this process are significant. By providing automated triage and context-aware answers to common questions about request procedures and timelines, AI can shorten decision cycles and improve user satisfaction. Automated checks against enterprise standards and authoritative catalogs ensure duplication and compliance issues are caught early, while lifecycle and vulnerability monitoring reduces the chance of security exposures. Cost efficiency improves as AI correlates license usage data with actual activity, identifying inactive instances and recommending right-sizing actions. Standardized analyses and automatically generated approval packets improve auditability, while consistent tracking of end-of-life timelines and upgrade requirements reduces the likelihood of unexpected outages. Ultimately, the mission outcome is better: users gain timely access to the technologies they need, while the organization maintains governance, security, and fiscal responsibility.
System outputs
The outputs of the AI system take several forms. On the conversational side, it delivers plain-language guidance about processes, expected timelines, and relevant policies. On the analytical side, it generates recommendations about whether a request is a new product, an upgrade, or already covered by an existing enterprise standard. It produces risk and readiness scores that summarize vulnerabilities, lifecycle status, duplication concerns, and cost implications. The system also generates structured artifacts such as intake forms, change analysis documents, evaluation plans, and procurement justifications that can flow directly into existing approval or tracking systems. In operations, it outputs monitoring dashboards and alerts that highlight unused licenses, upcoming end-of-life dates, or pending upgrades. Each of these outputs is designed to be human-reviewable, with citations and evidence provided to support trust and transparency.
Technology
- AI classification
- Generative AISource: Generative AI: AI that generates new or synthetic content (e.g., images, videos, audio, text, code).
- System name(s)
- Not reported
- Custom-developed code
- Not reported
- Public source code
- Not reported
Sourcing
- How it was built
- Not reported
- 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
- Not reported
- Authorization to Operate
- Not reported
- Demographic features
- Not reported
- Training and evaluation data
- Not reported
- 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