Turning fragmented asset evidence into a consistent, defensible renewal priority

An Amtrak-specific decision brief based on publicly available information

Amtrak's challenge is not a lack of asset information. It is determining—consistently and defensibly—which assets require attention first. The evidence needed to make that decision is distributed across asset records, condition data, inspection findings, engineering reports, maintenance histories and the knowledge of field personnel. When those sources are incomplete or do not align, comparing asset needs becomes slower, less consistent and harder to defend.

The Amtrak Office of Inspector General has identified several obstacles:

• Amtrak's two primary asset-tracking systems do not fully align.
• Assets may appear in one system but not the other.
• Retired assets can remain in the systems while active assets may be missing.
• Condition-data improvements are not yet complete.
• Prioritization can depend heavily on asset age and the institutional knowledge of field personnel.

Older but functional assets may therefore be prioritized ahead of newer assets in worse condition.

This creates more than a data-quality problem. It makes it harder to compare asset needs consistently, coordinate decisions across departments and demonstrate why one investment should take priority over another.

A large, time-sensitive challenge

$47B Amtrak's estimated infrastructure state-of-good-repair backlog

2040 Amtrak's target for eliminating the backlog

$5.5B+ Amtrak's FY2025 capital expenditures

~500 Capital projects currently underway

The Amtrak OIG has also concluded that Amtrak cannot yet reasonably demonstrate how the federal funds it receives will reduce the state-of-good-repair backlog or the timeline for eliminating it.

The issue is therefore not simply whether Amtrak has information. It is whether the relevant evidence can be assembled, evaluated and translated into a priority that engineering, asset management, capital planning and leadership can review and defend.

Introducing Geminos PathWay™ for Rail

Geminos PathWay is a complete, purpose-built solution for a specific operational problem.

It is not a packaged asset-management product that Amtrak would have to adapt its processes to, nor is it an AI toolkit Amtrak would have to configure and assemble. Geminos builds the application specifically around the customer's use case, delivers it as a working solution and provides ongoing support.

For Amtrak, Geminos would build the PathWay solution around this decision:

Based on the available condition evidence, engineering knowledge, operational
risk, asset dependencies and approved renewal criteria, which assets should
receive attention first—and why?

The application would bring together structured data from asset-management systems, inspection databases, maintenance systems and operational records with unstructured information contained in engineering reports, inspection notes, maintenance histories, policies and other documents.

PathWay would connect this information, identify missing or conflicting evidence, apply Amtrak-approved prioritization criteria and produce a review-ready recommendation with the supporting evidence and reasoning attached.

Geminos would build the application, Amtrak would license it and Geminos would provide ongoing support. It would work with Amtrak's existing systems and documents rather than replacing its systems of record, engineering expertise, governance or approval authority.

HOW PATHWAY WOULD SUPPORT THE DECISION

From scattered evidence to an explained recommendation

Existing asset systems are valuable for storing and managing information. But the work required to reach a renewal decision can still involve searching across systems, locating documents, reconciling conflicting records, applying criteria and manually preparing the rationale.

PathWay is designed to perform that decision-support work in one focused application.

1. Connect the evidence

PathWay would bring together asset records, condition information, inspection findings, engineering notes, maintenance histories, policies and renewal criteria.

Instead of treating each source separately, it would connect structured records and unstructured information that describe the same asset, location, system, dependency or condition issue.

2. Reconcile the information

PathWay would match records across sources and identify information that is:

• Missing or unmatched
• Stale or potentially obsolete
• Inconsistent with another source
• Unsupported by the available evidence
• In need of validation before a recommendation can be completed

This makes uncertainty visible before it becomes embedded in a renewal priority.

3. Apply Amtrak's criteria

PathWay would apply the combination of criteria Amtrak determines is appropriate, potentially including:

• Verified asset condition
• Safety and operational exposure
• Asset criticality
• Dependencies on other assets or systems
• Failure consequences
• Maintenance and lifecycle history
• Renewal policies and minimum investment requirements

Explicit rules can be handled through deterministic software and encoded business logic. AI is used where interpretation, evidence assembly or analysis is required.

4. Produce a review-ready priority

The application would present a proposed renewal priority together with:

• The evidence considered
• Missing or conflicting information
• The criteria applied
• The reasoning behind the recommendation
• Alternative considerations
• The record of human review and approval

Amtrak's engineers and asset leaders would retain decision authority. PathWay would make the work leading to that decision faster, more consistent and easier to defend.

What makes PathWay different

Built around one operational decision

PathWay begins with the operational decision Amtrak needs to improve. It is not a broad technology implementation searching for a use case.

More than search or summarization

A search tool can find information. A language model can summarize a document. A dashboard can display asset metrics.

PathWay goes further. It connects structured and unstructured evidence, evaluates that evidence against Amtrak's criteria and produces a proposed priority with the supporting rationale attached.

The right technology for each part of the problem

Each PathWay solution is built on Geminos ArchWay™, an enterprise AI architecture that combines enterprise knowledge graphs, causal AI, large language models, agents, deterministic software and business rules in the proportions appropriate for the problem.
The knowledge graph provides a structured representation of the assets, evidence, terminology, relationships and rules involved in the decision. This allows information extracted from unstructured documents to be understood in the context of Amtrak's structured operational data—not treated as isolated text.

Human-governed

PathWay produces evidence-backed recommendations for review. Amtrak personnel retain authority over engineering, maintenance, capital and safety decisions.

A complete solution—not a toolkit

Geminos builds the application, the customer licenses it and Geminos supports it. Amtrak would receive a working operational solution rather than a collection of technologies its internal teams would have to assemble.

Proven in a live rail environment

At Great Western Railway, Geminos PathWay for Rail is in production for delay attribution.

The application brings together structured operational information and unstructured rail narratives, interprets the evidence within specialized rail terminology and rules, and produces a transparent recommendation with an audit trail.

It reduced the delay-attribution process from around eight days to approximately 10 minutes while maintaining the rigor and auditability required for the process. Asset-renewal prioritization is a different use case, so the GWR result is not an estimate of the result Amtrak would achieve. Its relevance is the operating pattern:

• Evidence distributed across multiple sources
• Important knowledge contained in unstructured reports and narratives
• Specialized rail terminology, relationships and rules
• Incomplete or conflicting information
• A recommendation that must be understood, reviewed and defended

GWR demonstrates that Geminos can turn this type of evidence-intensive rail process into a working production application.

THE VALUE FOR AMTRAK

Reach a defensible renewal decision faster

The proposed Amtrak PathWay solution would be an operational asset-renewal prioritization application designed to shorten the path from scattered evidence to a review-ready recommendation.

The intended result is:

Bring together the complete body of structured and unstructured evidence, identify what requires attention, apply Amtrak's approved criteria and produce a renewal priority that decision-makers can review, understand and defend.

PathWay would allow asset leaders and engineers to spend less time assembling and reconciling information—and more time evaluating risk, comparing alternatives and applying engineering judgment.

What Amtrak could evaluate

The goal of the PathWay solution would be to improve the asset-renewal prioritization decision. Its operational value could then be evaluated using measures such as:

MEASURE	WHY IT MATTERS
Time from initiating a prioritization review to producing a review-ready recommendation	Measures the complete decision cycle
Staff time spent locating and assembling evidence	Shows how much effort is consumed before analysis can begin
Staff time spent reconciling conflicting or incomplete records	Identifies data-quality friction
Number of review or rework cycles	Shows whether better evidence reduces repeated analysis
Time required to compare alternative priorities	Measures responsiveness when budgets, conditions or requirements change
Percentage of recommendations supported by complete evidence	Measures decision readiness
Percentage of recommendations with a traceable rationale	Measures whether priorities can be reviewed and defended

 

During discovery, Geminos can use Amtrak's current process, decision volume and baseline time to develop a realistic estimate of the potential improvement. This avoids relying on arbitrary industry averages or unsupported financial assumptions.
Measurement would demonstrate the value of the operational solution; it would not be the purpose of the solution.

One solution, with a focused production scope

The proposed deliverable is one PathWay solution for Amtrak's asset-renewal prioritization process.

To create a clearly defined and operationally useful production scope, the solution would initially be built around one selected infrastructure asset class where:

• Renewal decisions occur regularly
• Condition and supporting evidence come from multiple sources
• Data conflicts or gaps are visible
• Comparing priorities requires meaningful engineering judgment
• The consequences of prioritization are material

This does not mean Amtrak would need a separate PathWay application for every asset class. The solution would be built around the asset-renewal prioritization decision and could be extended to additional asset classes if Amtrak later chooses.

Beginning with one asset class allows Geminos to build a complete, usable solution around a well-defined body of evidence, decision criteria and operational workflow. It is a focused production scope—not a preliminary measurement application or an incomplete pilot.

See the working application before committing to production

Geminos does not begin by asking Amtrak to commit to a lengthy integration project based on a presentation, generic demonstration or proposed architecture.

Geminos builds the working application first.

1. Define the decision

Geminos and Amtrak begin with a structured discovery conversation to define:

• The asset-renewal decision the application must support
• The people involved in reaching and approving that decision
• The systems and documents containing the relevant evidence
• The condition, risk, criticality, dependency and lifecycle criteria that must be considered
• What a useful, review-ready recommendation must contain
• What success would look like for the selected scope

The objective is to understand the real operational decision before determining the precise combination of technologies required.

2. Research the problem and synthesize representative data

Geminos researches the selected asset class, decision process, terminology, evidence and applicable rules.

It then creates synthesized data representative of the real information environment. For this use case, that could include realistic asset records, condition assessments, inspection findings, engineering reports, maintenance histories, missing information and conflicting evidence.

This allows Geminos to build a meaningful application without requiring Amtrak to provide or integrate production data at the outset.

3. Build the purpose-built application

Using Geminos ArchWay, Geminos builds the complete decision workflow around the synthesized data. This includes:

• Connecting representative structured records and unstructured documents
• Building the use-case-specific enterprise knowledge graph
• Representing the relevant assets, evidence, relationships, terminology and rules
• Encoding explicit prioritization criteria and business logic
• Creating the evidence-reconciliation and prioritization workflow
• Building the interface through which users review the evidence and proposed priority
• Producing a traceable rationale for the recommendation

Geminos uses the appropriate combination of enterprise knowledge graphs, causal AI, large language models, agents, deterministic software and business rules. The architecture is selected for the problem rather than forcing the entire solution into one type of AI.

4. Deliver the working alpha in days

Amtrak receives a functioning version of its asset-renewal prioritization application running on the synthesized data.

The alpha is not a generic product demonstration, slide presentation or technical proof of concept. It is a working application built specifically around Amtrak's proposed use case.

Amtrak can interact with the application and assess:

• Whether the correct evidence is being assembled
• Whether structured records and unstructured documents are being connected appropriately
• Whether missing and conflicting information is identified
• Whether the appropriate prioritization criteria are represented
• Whether the proposed recommendation and rationale are useful
• Whether the application reflects how Amtrak needs the decision to work

Amtrak can therefore see what the solution would do before committing to production integration.

5. Decide whether to proceed

After seeing and interacting with the working application, Amtrak decides whether it wants to move forward.

At this point, Amtrak is evaluating an application built around its asset-renewal decision—not a proposal describing what might eventually be built.

6. Integrate Amtrak's data and deliver the production solution

If Amtrak chooses to proceed, Geminos scopes the production delivery, integrates the required real data and adapts the application to Amtrak's systems, security requirements, governance and operating environment.

Geminos then delivers the licensed, supported production solution. Production delivery is typically completed within weeks, although timing depends on the agreed scope, system access, data availability and quality, security requirements, governance and approvals.

As Amtrak's information, requirements or decision process evolve, Geminos can support and evolve the solution over time.

The result

Geminos PathWay for Rail offers Amtrak a focused way to improve an important asset-renewal decision without replacing its existing systems or beginning with a long, open-ended software project.

The objective is clear:

Bring the relevant evidence together, identify what requires attention, apply Amtrak's approved criteria and produce a renewal priority that decision-makers can review, understand and defend.

Amtrak does not have to imagine what Geminos intends to build. It sees the purpose-built application working first and then decides whether to move forward.

Sources

1 Amtrak OIG: Incomplete governance framework and data weaknesses limit Amtrak's ability to manage its state-of-good-repair backlog, April 14, 2026
2 Amtrak OIG: Top management and performance challenges for fiscal years 2026 and 2027, July 22, 2026
3 Amtrak: Senior Manager, Engineering—Asset Policy & Renewal role
4 Geminos: GWR and Geminos—Introducing PathWay for Rail Delay Attribution
5 Geminos: Published GWR delay-attribution result
6 Geminos: PathWay launch and delivery approach

This unsolicited Geminos brief is provided for discussion purposes only. It is based on publicly available information and does not imply Amtrak's endorsement of Geminos or its products.