Upload files

ID	Requirement	Notes
2.9.1.	Once a contract rule has been created, the document reader shall create an upload file and transmit it to a designated FTP server using a carrier-specific ID provided by ATPCO.	ATPCO parking lot: individual FTP login for each carrier or just one?
2.9.2.	Upload files shall adhere to the requirements outlined in the documentation provided to Volaro.	ATPCO parking lot: upload requirements to be provided to Volaro
2.9.3.	If an upload fails, Volaro shall correct the errors per details provided in an ATPCO error message.	ATPCO parking lot: error conditions for uploads, corrections to make, ATPCO error messages
2.9.4.	Volaro shall create four notification records for each upload file · Identifier of Volaro as the transmitting organization (maximum three alphanumeric characters) and the carrier whose rule was created (maximum three alphanumeric characters). Example: N VOLAA. · Email notification to the carrier email address provided in the instructions · Email notification to a designated ATPCO address · Email notification to Volaro (optional)	ATPCO parking lot: ATPCO email address
2.9.5.	The email notifications shall provide the following information: · List of each category that was coded and its source of information (contract artifact or STR or Alt GEN)	ATPCO parking lot: email notification requirements

Appendix A – Supplemental Information Form

Carrier Code:
Contract Rule:
STRs and Alt GENs
Contract Tariff	Contract Category	Source Tariff	Source Rule	Source Category

Appendix B -– Change Request Form

Carrier Code:	Contract Tariff:	Contract Rule:
<carrier fill in>	<carrier fill in>	<carrier fill in>
Type of Change	Information to Add	Information to Remove
Authorized sellers of tickets	<carrier fill in>	<carrier fill in>
Travel dates	<carrier fill in>	<carrier fill in>
Ticket dates	<carrier fill in>	<carrier fill in>
Discount levels	<carrier fill in>	<carrier fill in>
Fare amounts	<carrier fill in>	<carrier fill in>
Account codes	<carrier fill in>	<carrier fill in>
Base fares (Anne Q: is this the same as fare amount?)	<carrier fill in>	<carrier fill in>
Override dates	<carrier fill in>	<carrier fill in>
Record 2 control data for existing sequence	Category: <carrier fill in> Field: <carrier fill in> Sequence number: <carrier fill in> Value to add: <carrier fill in>	Category: <carrier fill in> Field: <carrier fill in> Sequence number: <carrier fill in> Value to remove: <carrier fill in>
Alt GEN in existing sequence	Category: <carrier fill in> Sequence number: <carrier fill in> Alt GEN tariff to add: <carrier fill in> Alt GEN rule to add: <carrier fill in>	Category: <carrier fill in> Sequence number: <carrier fill in> Alt GEN tariff to remove: <carrier fill in> Alt GEN rule to remove: <carrier fill in>
Source tariff/rule Note: All of the sequences in the source tariff/rule will be added/removed from the category	Category: <carrier fill in> Source tariff to add: <carrier fill in> Source rule to add: <carrier fill in>	Category: <carrier fill in> Source tariff to remove: <carrier fill in> Source rule to remove: <carrier fill in>
Other: <Carrier list here>	<carrier fill in>	<carrier fill in>

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