Skip to content

Create README for the anvil phase with use cases - #84

Open
edwinvandenbelt wants to merge 1 commit into
mainfrom
Anvil---description
Open

Create README for the anvil phase with use cases#84
edwinvandenbelt wants to merge 1 commit into
mainfrom
Anvil---description

Conversation

@edwinvandenbelt

Copy link
Copy Markdown
Collaborator

Added detailed descriptions of the anvil phase, including business use cases and their respective objectives and processes.

Added detailed descriptions of the anvil phase, including business use cases and their respective objectives and processes.
After 'the Forge', this is re-scoped to:

Only enlisting financial elements that have to be communicated between the Distributor and the Retailer.
The financial clearing is a responsibility of the Retailer.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Usually the billing is initiated by the distributor side. Involving financial clearing houses is a different topic outside of EUDIT and usually done between railways only.

After 'the Forge', this is re-scoped to:

retrieve Travel Documents (tickets), taking into account tickets distribution by retailer, or distributor

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add ticket activation (creating tickets for travel days based on a purchased pass or multi journey package)?

After 'the Forge', this is re-scoped to:

(partial) cancellation
(partial) exchange (also used for upselling)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

upselling is often not implemeted as a exchange but in a simpler way by adding produts (e.g. add an upgrade from first to second calls and keep the original 2nd calls ticket).

acheive reservation process => moved in BUC C
After 'the Forge', this is re-scoped to:

retrieve Travel Documents (tickets), taking into account tickets distribution by retailer, or distributor

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs to cover aother documents as well (receipts, vouchers, infos)

### G. Validation – inspection / In-trip (services and aftersales)

sale/pay on tap
inspection durng travel

@CGantert345 CGantert345 Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is not in EUDIT scope, in scope is oly providing travel documents as to support inspection.


sale/pay on tap
inspection durng travel
trip modification (traveler request or operator disruption)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The flows will be different. This should be separated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants