I 34 service constraints for route parts (fare model)

I-34: service constraints for route parts (fare model)

Description

Service constraints (e.g. Ferry) might apply to a part of a route only. In the old 108.1 data this has been faked by some railways using stations named "Ferry" in the route.

Owner

• Sören Mayer (DB)

Business Value

Enables the sale of NRTs with different proces depending on the route service constraint.

Business Outcomes

The route description is more accurate and allows to have separate routes (e.g. direct ferry and longer train route) depending on the constraint.

Leading Indicators

Nonfunctional Requirements

the conversion to the legacy data should be possible

Need

Analysis

In the data structure for ViaStation (the generic route part object) inculding a ServiceConstarint (online) or referencing a serviceConstraint (offline) must be possible.

The serviceConstraint must include a legacy code for the conversion to 108.1 data format (offline only).

Out of Scope

Specification Effort: SMALL