Revised Contracts

Changes to a contract rule may include one or more of the following:

· Changing Record 2 control data

· Adding/removing/renumbering Record 2 sequences within an existing category

· Adding/removing Record 3 table numbers datafrom a sequence

· Adding/removing Alt GENs from a sequence

· Adding/removing the sequences of an STRs

ID	Requirement	Notes
2.8.1.	The document reader shall revise existing contract rules according to the directions on the carrier’s instruction.
2.8.2.	The document reader shall compare the revised information to the existing data and make the applicable changes.
2.8.3.	Revised data only shall be included in the upload file submitted to ATPCO.
2.8.4.	The document reader shall do a FareManager “Cancel/Add” if: · Existing sequences need to be reordered or · A sequence’s relational indicators need to be changed or · The order of tables in a sequence need to be changed
2.8.5.	The document reader shall do a FareManager “Update” if no changes are required to: · The order of existing sequences or · A sequence’s relational indicators or · The order of tables in a sequence
2.8.6.	The document reader shall do a FareManager “Update” if changes are required to: · Agencies authorized to sell tickets · Travel dates · Ticket dates · Discount levels · Fare amounts · Account codes · Base fares · Override dates · Record 2 control data
2.8.7.	The document reader shall do a FareManager “Update” if: · A Record 2 sequence is added with no change to the order of the other sequences · An existing Alt GEN is replaced with a different one in the same sequence · An existing source tariff/rule is replaced with a different one in the same category
2.8.8.	Contract change requests shall be submitted to Volaro through the same process as original contracts.
2.8.9.	The details of contract changes shall be listed on a form provided by the carrier. See Appendix B – Change Request Form.

Дата добавления: 2015-09-01