GSA_Responses_to_Vendor_Questions_QMAC-KB-160001-D_02-19-16.pdf

February 19, 2016

City Pair Program

FY2017 Requirement for Air Passenger Transportation Services

Solicitation No. QMAC-KB-160001-D

Questions & Answers in Response to Draft Solicitation Issued January 29, 2016

No. Solicitation Reference Question Answer

1. F.7(b) City-Pair Activity Reporting

Item F.7 City-Pair Activity Reporting – We are still very unclear what is actually being requested here? Counting the number of flight segments involved in YCA & _CA purchases is possible, although requires a tapping into a separate database and should not be considered a light-duty request. It doesn’t appear this will be resolved before the solicitation is released later this month - Please remove this item and we can address the true need and deliver a meaningful and consistent data across all stakeholders.

The column titled “Total # of Flights” will be removed from the final version of the RFP, which has yet to be released.

2. C.8 Dissemination of Contract Fares

Item C.8 Dissemination of Contract Fares – We understood from our face-to-face meeting that the language referencing a change in a carrier’s reservation system would result in a waiver of service fees. This area also requires additional clarity, so we appreciate removing this to avoid any unnecessary future challenges.

The language referencing a change in a carrier’s reservation system resulting in a waiver of service fees will be removed from the final version of the RFP, which has yet to be released.

3. M.5(6) Baggage Fee Consideration

Baggage – If we heard correctly, the “Complimentary Checked Baggage” award favoring will be removed. We strongly support this decision as a very small percentage of customers actually pay for checked bags. Active-duty military, Y category fares, Mileage Status amongst other exceptions already exist.

That is incorrect. For FY17, the language for baggage fee consideration remains unchanged and is the sixth price/technical tradeoff factor. GSA will consider reviewing baggage fee and addressing it in the future.

4. N/A Online Transportation Handbook – We would like to provide assistance as needed to place an updated Transportation Handbook online.

We will relay this to our Audits division. If any other carriers are interested in helping out with this, please notify the CPP team by email at citypairprogram@gsa.gov.

5. B.2 Definitions On page 3 of FY17 Contract Changes, B.2 Definitions _CA Fares, “Such codes shall include the letters “-CA” as

Please see the following language, which is found in Section C.8, Dissemination of Contract Fares:

mailto:onthego@gsa.gov

February 19, 2016 the last two characters. What about airport specific fares such as for IAD and DCA? We currently use YCAIAD or YCADCA to designate the airport eligible for the fares. If that cannot be used we may have difficulty in those cities.

Also included may be Houston with IAH and HOU and NYC with EWR and LGA. This is Domestic only.

“The contract carrier shall file contract fares under the “YCA”, “_CA” or “_ CB” designator. Under no circumstances shall the contract carrier use “YCA”, “_CA” or “_CB” designator codes for any market in which the carrier is not the Government contract carrier. Airport codes shall be used in conjunction with “YCA”, “_CA” and “_CB” contract air fare designators where applicable. When two airport codes are required (e.g., YCAJFKDCA), the last character shall be dropped (e.g., YCAJFKDC).”

6. B.4(5)(a) Pricing and Schedule for Group 1 and 2 Markets

On Page 4 B.4(5)(a) Pricing and Schedule for Group 1 and 2 Markets, it says Business Class fares shall be coded as _CB. Business class fares shall be placed above the bottom third of the carrier’s commercial fare classification code structure…Thought this was to be removed. Changes downloaded on Friday do not show a change, still calling for above the bottom third of Business Class

The language referencing business class fares being placed “above the bottom third” will be removed from the final version of the RFP, which has not yet been released.

7. Section C.2(C), Note 3, Exceptions to the mandatory use requirement

Note 3 under Section C.2(C), Exceptions to the mandatory use requirements, seems to be directing the travelers to always purchase the lower, capacity controlled fare. Why is this even in the solicitation for the carriers? We have no control over what the passenger purchases.

The language contained in Section C.2.C is taken from the Federal Travel Regulations and is included in the RFP for consistency.

8. Section J.1 Attachment 1

– Proposal Checklist

How should Blocks 12 and 23/24 be filled out in the

SF1449?

Once the final RFP is released, offerors will be required to fill out Blocks 12, 17a (including DUNS number), 17b if applicable, 30a, 30b, and 30c of the SF1449. Block 12 can be filled out with “N/A” as this refers to prompt payment discount terms and is not applicable to the CPP.