15-PSC-MK-NOI-00001.odt

The Department of Health and Human Services (DHHS), Program Support Center (PSC) on behalf of the Department of Defense (DoD), Defense Travel Management Office (DTMO) intends to negotiate and award a sole source bridge contract to CW Government Travel, Inc. doing business as: CWTSatoTravel, 4300 Wilson Blvd., Ste 500, Arlington, VA 22203-4178 on a sole source basis under the authority of FAR 6.302-1(a)(2)(iii).

The Intended procurement is classified under NAICS code 561510 with a Size Standard of $20.5 million.

The resultant contract will include all applicable provisions and clauses in effect through the Federal Acquisition Circular (FAC) 2005-78 (effective December 26, 2014).

This acquisition is conducted under the procedures as prescribed in FAR 13—Simplified Acquisitions.

Description The Defense Travel Management Office (DTMO) requires continued support by the incumbent – CW Government Travel with providing official travel management services for Defense Travel Area 5 (DTA 5), U.S. Air Force (AF) CONUS locations.

Purpose and Objectives The DTMO requires the continuation of official travel management and related additional services on a point of sale basis for Department of Defense (DoD) travelers assigned to DTA 5 sites. These CTO services are to support official travel activities of authorized DoD travelers who are under the authority of the referenced locations. Official travel is travel (e.g., TDY, PCS, evacuation, travel by Reserve Component members, and civilians on invitational travel orders) in connection with official business of the United States Government and performed under orders at the expense of federal appropriated funds. These CTO services shall be provided using both traditional methods using the Defense Travel System (DTS) web portal, and automated methods using the Defense Travel System (DTS) web portal. In accordance with the original Performance Work Statement (PWS) attached.

Period of Performance Base period of one (1) year, March 17, 2015 – March 16, 2016, with up to three (3), four (4) month options from March 17, 2016 – March 16, 2017.

This notice of intent to award a sole source bridge contract is not a request for competitive proposals. However, in accordance with FAR 5.207(c)(15)(ii), all responsible sources that feel they can meet the Government’s requirements detailed above and in the attached Performance Work Statement (PWS) may submit a capability statement which shall be considered by the agency. Capability Statements should be tailored to show the Government the offeror is able to meet the specialized requirements of DTMO Commercial Travel services, and applicable regulations. Responses to this notice shall contain sufficient information to establish the interested parties’ bona-fide capabilities for fulfilling the requirements within the PWS, and include: the Dun & Bradstreet Number (DUNS), and the Taxpayer Identification Number (TIN).

All offerors must have an active registration in the System for Award Management (SAM) www.sam.gov.”

A determination by the Government not to compete this proposed contract based upon responses to this notice is solely within the discretion of the Government. The information received will be retained as Market Research.

All responses must be received by 3:00pm EDT on Monday, March 2, 2015 and must reference number 15-PSC-MK-NOI-00001. Responses may be submitted electronically to Margo Katzper via email at Margo.Katzper@psc.hhs.gov, or by U.S. mail to U.S. Department of Health & Human Services, Program Support Center, Acquisition Management Services, Twinbrook Place, Suite 400, 12501 Ardennes Avenue, Rockville, MD 20857, Attention: Margo Katzper. Fax responses will not be accepted.

SECTION 3 – PERFORMANCE WORK STATEMENT

SCOPE OF WORK

1.1. The Contractor shall provide all personnel, equipment, material, supervision and other items or services necessary to perform the management and operation of Contracted Commercial Travel Offices (CTOs), as defined in this Performance Work Statement (PWS). Performance shall be in support of all designated facilities throughout the Department of Defense (DoD) worldwide, to include other Government facilities as specified.

GENERAL

1.2.1. This PWS is for the acquisition of CTO and related services to support official travel activities of authorized DoD travelers. Official travel includes Temporary Duty (TDY), Permanent Change of Station (PCS), Leisure in Conjunction with Official Travel (LICWO), evacuation; and travel by Reserve Component/National Guard members. Official travel also includes travel by civilians on invitational travel authorizations in connection with official business of the United States Government and performed under orders at the expense of federal appropriated and non-appropriated funds, with the exclusion of LICWO.

1.2.2. The Contractor shall provide travel management services (i.e., DTS, air/rail CTO Assist, and non-air/rail CTO Assist) as requested by the Government and as necessary to meet all DoD travel management needs during each phase of Defense Travel System (DTS) deployment and implementation. Sites not yet converted to DTS will be serviced via electronic methods, email, fax, telephone, or walk-in until the fully automated system is deployed. Even after DTS is fully deployed at a particular location, the Contractor shall be prepared to provide air/rail and non-air CTO Assist services to ensure DoD travel is supported.

QUALITY CONTROL PLAN

1.3.1. The Contractor shall complete and implement a Quality Control Plan (QCP) that addresses all aspects of customer service and other provisions required by the contract. The Contractor shall submit this plan to the Contracting Officer within 30 calendar days after the Task Order award date. Upon the request of the Contracting Officer, the Contractor shall update its QCP annually and submit it for Government review and approval. The QCP shall include details concerning processes proposed to ensure contract quality assurance.

1.3.2. The plan shall include the following:

A quantitative method for measuring the Contractor’s service required in the PWS;

An inspection system covering all services required in this PWS specifying the areas to be inspected on

An active program and strategy for improving quality over the life of this contract;

Method of providing security of documents, records, and Privacy Act information of customers during and after normal business hours;

Method for collecting customer feedback, initiating corrective action if needed, and method for sharing consolidated feedback to the Government;

Method for providing required management information reports on schedule and for ensuring validity of the data;

Method for ensuring quality levels for subcontractors as applicable;

Method for implementing the QCP;

Contingency plan that describes Awardees approach to ensure uninterrupted travel services in the event of a unforeseen disaster or emergency and;

Method for monitoring telephone services in accordance with the requirements specified in the PWS at paragraph 11.12

1.3.3. Quality Control Plan Report. The Contractor shall submit a monthly QCP Report. At a minimum, the Contractor’s QCP Report shall document the results of Quality Control actions, as measured within the format of the QCP. The Contracting Officer or the Contracting Officer’s Representative (COR) may forward the QCP and QCP Report to other Government designated personnel.

1.3.4. The Contractor’s Quality Control Plan shall include procedures to ensure compliance with Government/DoD/Agency regulations and policy (See Para 12).

1.3.5. Surveillance of Contractor performance may be conducted through random sampling (e.g., Management Information Systems (MIS) and QCP Reports), and/or customer feedback provided to the Contracting Officer’s Representative (COR), Contracting Officer’s Technical Representative (COTR), Quality Assurance Evaluator (QAE), or Lead Quality Assurance Evaluator (LQAE) quarterly reports or by any other means necessary to ensure compliance with the Government’s Quality Assurance Surveillance Plan (QASP).

1.3.6. The COR may hold quality assurance conferences/meetings on an annual basis (as a minimum) to meet with the COTRs, QAEs, and LQAEs from each site under their area of responsibility. The purpose of these conferences/meetings will be to discuss/resolve systemic issues of concern, performance trends, and to share relevant information regarding the CTO program. The CTO may be required to participate in the quality assurance conferences/meetings annually.

1.3.7. The CTO may be required to participate in monthly CTO telephonic outreach discussions. The purpose of these conferences/meetings will be to discuss/resolve systemic issues of concern, performance trends, and to share relevant information regarding the CTO program.

PERSONNEL

1.4.1. All Contractor personnel shall be capable of and qualified in providing Government-sponsored travel for DoD personnel. Contractor’s personnel shall be knowledgeable of DoD and Service travel policies and ensure that these policies are complied with in the performance of their duties.

1.4.2. All services provided under this contract must be performed by Contractor personnel fluent in written and spoken English and who shall conduct themselves in a professional manner.

1.4.3. DoD 5500.7-R requires that certain DoD employees obtain written supervisory approval before engaging in outside employment or business activities. See DoD 5500.7-R, Para 3-306. Regulations issued by other Agencies may contain a similar requirement. Before the Contractor employs Government personnel (civilian and military) on this contract, the Contractor shall ensure that the employee has complied with any applicable requirement for supervisory approval, and shall forward a copy of the written approval to the COR.

1.4.4. The Contractor shall provide personnel capable of obtaining, at a minimum, a secret security clearance in accordance with the DD Form 254 (Attachment 4) if required by the Government. Appropriately cleared personnel shall be provided at the location requested within 120 calendar days of the Contractor’s receipt of a written Government request, or at a later date following receipt of security clearance approvals from the Defense Investigative Security Office. The contractor shall not be limited to hiring only U.S. citizens; however, if the policy for a particular location requires only U.S. citizens to be hired the contractor shall adhere to the policy. The Government will provide security clearances at no expense to the Contractor.

1.4.5. Staffing levels for CTO services may be adjusted as a result of variations between the estimated percentage of DTS and air/rail CTO Assist transactions. Staffing levels may also be adjusted based on variations in the workload data provided. Equitable adjustments shall be in accordance with PWS subparagraph 14.1. During Task Order competitions, awardees shall identify in their proposal(s) a formula for making staffing level adjustments. The awardee may make adjustments to staffing levels at the contractor’s discretion upon a 30-day notification to the Contracting Officer. The notification of staffing level adjustments shall be identified in a revised Staffing Plan.

CUSTOMER SERVICE

1.5.1. The Contractor shall provide 24-hour, 7-days per week courteous and responsive service, to include providing services to travelers after normal duty hours. The Contractor shall, via the itinerary, list telephone numbers for normal and after-normal duty hours; and stipulate that the “after-normal duty hours” phone number shall only be used for emergencies and by travelers enroute. The Contractor shall provide a toll-free telephone number, where capability exists, as well as toll free numbers for fax capability and shall accept collect calls appropriate for supporting all DoD/Government travel needs as required within this worldwide contract and specified in each Task Order.

1.5.2. The Contractor shall provide courteous and prompt resolution of travel problems and forward problems or traveler questions, beyond the Contractor’s resolution authority, to the COR, COTR, and QAE via electronic means (i.e., email, fax).

1.5.3. The Contractor is responsible for assisting with resolving complaints, disputes, or claims between the DoD/Government customer and any principal with whom the Contractor has arranged travel or other services, if the action was originated through the Contractor.

1.5.4. The Contractor shall reimburse the Government for additional expenses incurred to obtain alternate travel and accommodations if, as a result of negligence on the part of the Contractor, reservations made by the Contractor are not honored by the vendor or carrier.

1.5.5. Due to projected base closures and realignments, the Government cannot forecast how the revenue for official travel will be affected. As site(s) are identified for addition or deletion, the Contracting Officer will issue a modification to this contract. In such an event, the Contracting Officer will provide the Contractor a 60 calendar day written notice for CONUS locations.

EMERGENCY SERVICES

1.6.1. The Contractor shall provide Travel Management Services as needed to satisfy surge requirements and in response to contingencies including, but not limited to, national emergencies, accident investigations, aircraft recovery teams, evacuations, rescue operations, civil disturbances, disasters, military peacetime and wartime contingency operations, exercises, exodus travel (Europe only), personal emergencies, and mass causalities (human remains). At all times, the Contractor shall ensure quality customer service is maintained in accordance with applicable standards set forth in this contract. Operating hours and support by the Contractor may be modified as agreed to by the QAE or COTR in coordination with the COR in support of emergencies.

1.6.2. The Contractor shall support emergency and short-notice requirements by providing electronic or paper tickets, or, as a last resort, arranging for prepaid tickets at a carriers’ terminal or ticket office convenient to the traveler. Charges or fees associated with the issuance of prepaid tickets will be paid by the Government, unless the Contractor is responsible for late ticket issuance. When the Contractor is responsible for late ticket issuance, charges or fees associated will be handled by the QAE in coordination with the COR.

TRAVEL OFFICE FACILITIES, SAFETY AND PHYSICAL AND PERSONNEL SECURITY

1.7.1. The Contractor shall ensure business hours coincide with the local location business hours. Operating hours may be modified as agreed to by the QAE in coordination with the COR.

1.7.2. The Contractor shall ensure that the travel office facilities are maintained in a clean and orderly manner consistent with installation and agency standards.

1.7.3. The Contractor shall provide travel office interior and exterior signs that conform to Service and Agency regulations and local customs in accordance with guidance and instruction from the authorized Government representative (e.g COR, and QAE).

1.7.4. The Contractor shall ensure that Contractor personnel comply with all rules and regulations, (i.e., published safety and security guidelines) applicable to the installation. All accidents that result in damage to Government property occupied and used by the Contractor, and/or injuries to Contractor personnel shall be reported to the COR, and the QAE within one workday from occurrence.

1.7.5. The Contractor shall clearly identify its personnel in accordance with Government Service and Agency regulations and local site custom.

Contractor Representation: The Contractor shall send a letter to the respective COR/COTR with a listing of employees authorized to represent the Contractor in the performance of required services. These shall be updated within 30 calendar days of changes in personnel.

Vehicle Passes/Registration: For vehicle passes/registrations, each Contractor employee shall comply with requirements made for each installation, including those for pass receipt and security, safety rules and parking ordinances. The Contractor shall be responsible for removal of parking decals for personnel who leave the Contractor’s employment or are transferred by the Contractor to a location outside of the Government facilities.

Building/Property Security: If the Contractor occupies a separate facility or an area within a facility that can be physically secured, the contractor shall provide physical security of the contractor's facility or work area. At those locations where the contractor shares a facility with other government personnel, the contractor shall coordinate physical security requirements, responsibilities, and procedures for that location with the COTR. The contractor shall be responsible for safeguarding all government property provided for contractor use. At the close of each work period, the Contractor shall secure government facilities, equipment and materials.

Key/Combination Control: The Contractor shall establish and implement methods of ensuring that all keys/combinations issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons or for unauthorized purposes. No keys issued to the Contractor by the Government shall be duplicated by the Contractor. The Contractor shall immediately report the occurrence of lost or duplicated keys to the COR/COTR. In the event keys are lost or duplicated, the Government, at its option, may replace the affected lock or locks or perform rekeying. When a master key is lost or duplicated, all locks and keys for that system will be replaced. The total cost of replacing all locks and keys shall be paid by the Contractor.

GOVERNMENT FURNISHED FACILITIES AND SERVICES

1.8.1. The Government will make available (at no cost) on-site facilities where required, utilities, custodial services, refuse collection, pest control services, Government centralized mail distribution of interoffice mail, and police and fire protection at the level provided to local Government offices. For Staffed Offices, contractor employees shall be provided facilities comparable to Government employees (e.g. air conditioning, heating, etc.).

1.8.2 The Government may request the Contractor to relocate or realign its travel office, equipment and supplies totally and/or in–part, due to organizational/operational changes, base realignments or closures during the period of the contract. The Government will provide the Contractor at least 90 calendar days advance notification for relocation or realignment of the travel office or the movement of equipment e.g., printers/GDS. The Contractor shall comply with the specified date within the advance notification. A minimum of one-week notification will be provided to the Contractor for the relocation/movement of administrative supplies e.g., filing cabinets to include contractor’s files. Any Government request for relocation shall be at the Government’s expense.

Government request moves shall be coordinated in advance with the Contracting Officer and shall be coordinated and approved in advance by the local transportation office. Additionally, all cost associated with Government requested moves shall be approved prior to any costs being incurred and reimbursed by the local transportation office. No funds will be obligated on the contract to pay for moves. Any additional costs above and beyond the original approved amount shall be submitted to the Government for approval prior to any costs being incurred Contractor-initiated moves shall be paid by the Contractor. It is understood that in the event of various occurrences, including natural disasters, a Contractor is entitled to be excused from liability for delaying his performance; however the Government’s requirement during these periods is that the Contractor continue performance to the maximum extent practical. The Contractor shall not be required to bear the expense of providing travel services support, including the ability to perform Centrally Billed Account (CBA) reconciliation during the disaster.

1.8.3. The Government will provide, at no cost to the Contractor, existing commercial telephone lines. The cost of activating or maintaining service to existing lines shall be borne by the Contractor. The Contractor, at its expense, may install additional lines and connections. All telephone lines used by the Contractor, including those installed at the expense of the Contractor are subject to the control of the installation telephone office. Telephone numbers shall be listed in installation telephone directories as “(Contracted) Commercial Travel Office.” The name of the Contractor shall be listed IAW local policy and the Contractor may include the name of a subcontractor.

1.8.4. Telephone numbers used by the Contractor at on-base/post travel offices shall not be transferred to off base/ post locations upon expiration of the contract performance period. Any telephone numbers used for off base/ post service centers, such as a regional reservation center, promoted to the DoD military community under the contract, shall be terminated upon expiration of the contract.

1.8.5. The Contractor shall provide in-transit passenger visibility. The Contractor shall have the ability to identify and track passengers from origin to destination for arrangements made by the Contractor.

TRANSITION

1.9.1. The Contractor shall take all actions necessary to ensure there is no break in service during the transition between the Contractor hereunder and any previous or successor Contractor during phase-in and phase-out of travel operations. The transition shall be handled with minimal disruption to the customer.

1.9.2. The Contractor shall allow any successor Contractor access to Government owned or controlled office space 90 calendar days prior to contract expiration, for site surveys.

1.9.3. The Contractor shall issue and deliver tickets for travel commencing within three calendar days after contract expiration. Tickets shall be delivered no later than the close of business of the last workday of the contract based on the Contractor receiving authorization for ticketing.

1.9.4. The Contractor shall continue to reconcile all forms of payment for 120 calendar days after the contract performance period ends.

1.9.5. The Contractor shall electronically transfer to the successor Contractor all un-ticketed travel records contained in the incumbent Contractor’s data repository applicable to the effort under this contract. This includes all unticketed records in the pre-travel and travel phases. The Contractor shall be liable to indemnify the Government for any costs or losses sustained as the result of failure to deliver accurate and complete information due to actions of the Contractor.

1.9.6. For DTS transactions, the Contractor shall ensure that, prior to CTO conversion, the Passenger Name Record (PNR) validation worksheet has been completed and submitted to the Defense Travel Management Office (DTMO). Additionally, the Contractor shall ensure that active pseudo city codes have been established. All the aforementioned actions must occur 4 weeks prior to processing actual DTS transactions.

1.9.7. The Contractor shall cease operations and vacate all Government facilities by 12:00 midnight on the last working day of contract performance, unless otherwise approved by the Contracting Officer.

1.9.8. The Contractor may be expected to perform service not later than 60 calendar days after Task Order award.

1.9.9. No later than the 20th calendar day after contract expiration, the incumbent Contractor shall provide to the COR, and QAE a report for each payment mechanism containing the following information for each unbilled transaction (debits and credits) remaining in the incumbent Contractor’s database: complete ticket number, traveler’s name, accounting data, travel authorization number/travel order number, complete itinerary and dollar amount. The Contractor shall be liable to indemnify the Government for any costs or losses sustained as the result of failure to deliver accurate and complete information due to actions of the Contractor.

1.9.10. For DTS transactions, prior to task order expiration, the incumbent Contractor’s Pseudo City Code (PCC) or Subscriber Identification (SID) shall be disconnected from the DTS Reservations Module, which shall prevent creating new PNRs, modifying or cancelling existing reservation. The CTO may receive reservations approved prior to disconnection on their ticketing queue. During this transition period, DTS users will be unable to create new reservations or modify and cancel existing reservations using the Reservations Module. The CTO may receive approved reservations on their ticketing queue for processing and shall place all ticketed, cancelled, and modified DTS PNRs on the polling queue until the last working day of the contract performance. The CTO shall delete Branch or Bridge access between their PCC or SID and the DTS PCC or SID by 12:00 midnight on the last working day of task order performance.

SECURITY OF PROPRIETARY INFORMATION

1.10.1. Contractors providing travel services under this contract shall not intentionally obtain or disclose unauthorized proprietary information of another Contractor’s CTO through use of the Defense Travel System (DTS) Pseudo City Code (PCC). Such unauthorized access into the DTS is unacceptable. The Department of Defense will report unauthorized access in accordance with 18 U.S.C. § 1030 - Fraud and related activity in relationship to computers. Further, known or suspected computer vulnerabilities of the DTS must be officially and explicitly reported to the Contracting Officer and the DTS Program Management Office immediately upon discovery to allow for immediate resolution of the issues.

1.10.2. Whenever the contractor becomes aware that proprietary data pertaining to all related services to support official travel activities of authorized DoD travelers has been lost, stolen, or compromised, the Contractor shall immediately begin the process of notifying all effected cardholders. The contractor shall also notify the Defense Travel Management Office (DTMO) immediately, but not later than five (5) calendar days after the loss or compromise was discovered.

GOVERNMENT HOLIDAYS

1.11.1. The following holidays will be observed by the Contractor unless otherwise instructed by the Contracting Officer:

1.11.2. Any reference made to holidays shall be construed to mean the Government holidays listed below:

1.11.3. The Contractor shall coordinate all office closures other than for a Federal Holiday with the COR.

TRAINING

2.1. During Task Order implementation, the Contractor shall participate in a one-time Government conducted implementation training session per Task Order awarded. The training shall consist of a 60 to 90 minute presentation given to transportation officers and other DoD personnel over a two to three day period. The Contractor developed presentation shall introduce attendees to Contractor provided travel management services provided under this contract. It shall include information on areas such as CTO Assist travel services provided, after hours procedures, ticket delivery, and Centrally Billed Account (CBA) reconciliation procedures. The presentation shall be conducted through the use of Power Point Slides or other media. The Contractor is required to provide copies of all training presentations to attendees. The Contractor shall develop and provide for Government review and approval, presentations and training materials appropriate to the event 30 calendar days in advance of the training event.

Reserved.

3. REQUIREMENTS APPLICABLE TO BOTH DTS AND CTO ASSIST TRAVEL MANAGEMENT SERVICES

3.1. In accordance with compliance documents identified in Paragraph 12 of this Performance Work Statement (PWS), and the requirements in this contract, the Contractor shall perform Travel Management Services to support official travel activities of DoD sponsored travel. If the local business rules conflict with the requirements in this PWS, the Contractor shall perform in accordance with this contract. The services may include, but are not limited to the following:

Maintaining security of personnel data and ensuring enforcement of Privacy Act requirements;

Fulfillment: The travel service support function that fulfills (i.e., completes) the reservation process for the online booking customer. This function primarily includes ticketing of reservations, but may also incorporate CTO quality controls. The focus is to minimize CTO intervention in the travel process;

Air Mobility Command (AMC) Patriot Express Reservation: The Contractor shall arrange AMC Patriot

3.3. When requested by the traveler, the Contractor shall make confirmed reservations for air/rail, rental car, ground transportation, ferry and lodging. Government/DoD negotiated volume discount lodging programs shall be utilized by the Contractor where available. All U.S. commercial lodging institutions used shall be on the master list issued by the U.S. Fire Administration, Federal Emergency Management Agency, unless there is no listed property with available space within a reasonable driving distance from the TDY location. The current listing of approved lodging institutions is located on the internet at http://www.usfa.dhs.gov/applications/hotel/ . To the maximum extent possible, confirmed reservations shall only be made at commercial facilities that accept the Government charge card.

3.4. Reserved.

3.5. Electronic ticketing is the preferred method of ticket issuance. In the event that electronic ticketing is not available, airline tickets shall be issued on ticket stock, which is acceptable for movement on the carrier providing the transportation. The Contractor shall maintain sufficient quantities of ticket stock on-site to adequately handle normal and surge travel volumes and avoid ticketing delays. The Contractor shall deliver tickets to the traveler or authorized Government official. Tickets should not be issued more than three business days prior to travel, except when specifically requested by the Government. Delivery of tickets or records of reservation may be accomplished by any effective means such as regular or overnight mail, courier, and/or electronic delivery of an e-ticket, as long as timely delivery to the traveler is accomplished. Locations requiring ticket delivery will be identified at the task order level. If electronic ticketing is available and the traveler requests issuance and delivery of a paper ticket in lieu of accepting an e-ticket, the fee shall not be charged to the Government, (i.e., Individually Billed Account (IBA)/Centrally Billed Account (CBA)). The Contractor shall charge the traveler the paper ticket fee directly.

3.6. When commercial travel vendors initiate a change to previously scheduled travel arrangements, or transmit Other Service Information (OSI) or Supplementary Service Request (SSR) messages in PNRs, the Contractor shall notify traveler(s) of the changes to travel arrangements within 24 hours. Notification shall be by phone or electronic message (time permitting). If the Contractor is unable to contact the traveler, the Contractor shall leave a message at the traveler’s phone number(s) and email address(es) as contained in the traveler profile sent in the PNR. The Contractor shall ensure all PNRs originated in DTS with schedule changes are placed on the outbound/polling queue.

3.7. Travel orders/authorizations authorize official travel at Government expense. For CTO Assist (traditional) transactions, using a CBA as a form of payment, a copy of the travel order/authorization shall be provided to the Contractor prior to ticketing. For CTO Assist (traditional) transactions using an IBA as a form of payment, the Contractor shall view a hard copy of the travel order/authorization prior to ticketing. The CTO is not required to maintain a copy of the travel order/authorization. Electronic DTS generated authorizations, using the Reservation Module and an IBA as a form of payment; the CTO is not required to view a paper copy of the travel order/authorization prior to ticketing. Travel orders should be issued before travel begins unless an urgent and unusual situation prevents prior issuance. If official travel begins or is performed before travel orders are issued, the travel must be pursuant to oral, letter or message authority. For IBA transactions, issuance of tickets pursuant to oral, letter, or message authority must be authorized by an approving official; review of travel order/authorization after ticket issuance is not required. For CBA transactions, a confirmatory travel order must be issued within 72 hours of the date that travel began. The official who directed the travel will be responsible for providing the confirmatory travel order/authorization. There will be no impact or liability against the CTO if the confirmatory travel order/authorization is not obtained. The CTO is advised to notify the transportation office at the time of CBA reconciliation that the confirmatory travel order was not provided.

3.8. The Contractor shall at the request of official DoD travelers, provide LICWO travel services. The Contractor shall provide LICWO travel services to an individual on an official trip and to family members or others accompanying that individual when requested by the traveler. Because travelers are responsible for any costs that exceed the official portion of the trip, the Contractor shall not invoice the Government for any leisure reservations or services. The appropriate fee, as defined in the PWS, shall be charged to the Government for the official portion of the LICWO travel service request. The transaction fee for LICWO services shall be charged directly to the traveler.

The Contractor shall segregate costs for official travel from the leisure travel costs. The Government contracted fare shall not be used for LICWO.

3.9. The Contractor shall only provide the following services for LICWO travel and shall not advertise, solicit, or sell any leisure travel services in conjunction with official travel other than the following specified services for making LICWO arrangements:

Point-to-point reservations and ticketing on scheduled common carriers for all modes of travel.

Rental vehicle reservations

Lodging reservations

Delivery of travel documents

3.10. The Contractor shall accept requests for LICWO travel in person for staffed locations, and by email, phone, fax, or via DTS. The Contractor shall, at a minimum, accept personal charge cards, cash, checks, and money orders in accordance with commercial practices for LICWO travel and shall process timely refunds to travelers as appropriate.

3.11. The Contractor shall not, under any circumstances, provide the traveler with a cash refund for a totally or partially unused ticket issued for official Government travel, or allow a credit based on a refund toward the purchase of personal travel.

3.12. The Contractor shall identify and cancel, when capable, all unused or partially unused e-tickets 30 days from the date of the last air travel segment and initiate the process for refunds. The Contractor shall immediately process refunds for paper tickets upon receipt. E-tickets refunds shall be processed upon notification of non-use. The Contractor shall assist the Government in research of unused tickets. Additionally, the request for refunds shall be provided to the Government Transportation Office via paper/electronic means.

3.13. The Contractor shall accept payment for official travel by all forms of the Government Travel Card (i.e., IBA, CBA, and Unit Cards). Additionally, the U.S. Government Transportation Requests (GTRs) shall be accepted IAW with industry standards or as specified in the General Service Administration City Pair Contract. For official hotel and rental car reservations, the Contractor shall accept IBA, CBA (Unit Cards), and personal charge cards. This requirement is subject to industry standards.

3.14. The Contractor shall make arrangements and or issue miscellaneous charge orders in accordance with industry standards for authorized excess baggage. The Contractor shall arrange for excess baggage as allowed by the carrier. The Contractor shall provide the traveler with pertinent information related to the booking of the excess baggage to include carrier rules and fees. The traveler shall make payment for excess baggage directly to the carrier or by an IBA, CBA, or GTR in accordance with JTR/JFTR.

3.15. The Contractor shall make confirmed reservations for travelers requesting PCS duty travel accommodations to include travel of pets. The traveler will pay all costs for pet travel.

3.16. The Contractor shall make arrangement for the movement of DoD military working dogs.

3.17. The Contractor shall not issue a premium class (first class or business class) ticket at Government expense without receiving a signed or otherwise properly authenticated travel authorization specifically authorizing that class of service. Travelers are authorized to upgrade to business class at their personal expense or use frequent travel benefits.

3.18. The Contractor shall reimburse the Government for the cost of the difference between premium class travel (business or first class) and the lowest appropriate fare if business or first class arrangements are used without appropriate approval in accordance with DoD/Government travel policy.

3.19. The Contractor shall provide on-site staffing/site requested staffed office as defined in Attachment 23 (see staffed office definition) and Attachment 15 at sites identified by the Government.

3.20. The Contractor shall assist customers, via telephone or in person, with travel related inquiries. Inquiries could consist of providing cost estimates for air, rail, car, or excess baggage.

3.21. Reserved.

3.22. Reserved.

3.23. Global Distribution System (GDS) Terminals. The Contractor shall provide GDS terminals to be used by the Government for inspection/quality control purposes and for making reservations where identified in Attachment 23. The Government will use these terminals to monitor the Contractor’s compliance by checking fares, finding alternate routes, reviewing reservations, checking itineraries and for making reservations by those offices identified in this PWS. The Contractor shall adhere to any applicable industry standards and GDS security procedures and requirements in setting up the GDS. Accordingly, the Contractor shall provide the Government applicable operating instructions for the system regarding security. The Contractor shall provide to the Government training and maintenance for GDS terminals.

3.24. Software Solution with GDS-like Functionality. The Contractor shall make available an alternative to the GDS terminal through a commercial desktop application that provides functionality similar to a GDS terminal. The Contractor shall provide training and software release updates to the Government.

3.25. Satellite Ticket Printers (STPs) For Remote Ticketing. The Contractor shall provide installation, setup, training, connectivity, ticket stock, and maintenance for STPs. The Government will use the STP to print tickets at a location other than the CTOs. The Government will specify in a contract modification how many printers are required and where they shall be installed. The Contractor shall adhere to any applicable industry regulatory requirements.

3.26. For DTS transactions, the Contractor shall be required to use workaround solutions to ensure optimal customer service due to temporary system problems and charge the CTO Assist transaction fee.

3.27. Contractors shall have the capability to access all airline fares and schedules in order to ensure that the most economical airfare is available in accordance with DoD policy. This service shall be provided at the most economical cost to the Government. The Contractor shall take into account industry changes that affect revenue agreements between vendors i.e., GDS Fees, commission in their proposed fees.

3.28. When operating under a Management Service Fee (MSF) methodology, the Contractor shall retain all non-air commissions accrued. All air commissions accrued by the Contractor shall be provided to the Services and Agencies in the form of a monthly price reduction.

4. MANAGEMENT INFORMATION SYSTEM (MIS) REPORTING REQUIREMENTS

4.1. The Contractor shall provide accurate MIS information on all travel services provided. MIS reporting shall be performed in accordance with this contract; however, the Government reserves the right, pursuant to the Changes Clause, to establish additional or alternative MIS reporting requirements. See Task Order requirements (Attachment 23) for the current list of MIS reporting requirements under this task order.

4.2. Unused Paper Ticket Report

4.2.1. The Contractor shall submit two unused Paper ticket reports titled report 1 and 2. The frequency of report 1 submission is identified in the Task Order Requirements (Attachment 23). If weekly, monthly, or quarterly reports are requested, the Contractor shall submit, via email, a Microsoft Excel report to the Service and Agency Headquarters, QAE or COTR and the COR as outlined below. The report shall consist of the following data elements: number of cancelled tickets; value of cancelled tickets; number of unused travel segments; value of unused travel segments; value of requested refunds; and value of refunds received. One report shall be generated listing each site in the Attachment 14. The report shall also include the total number of unused tickets on a weekly, monthly or quarterly basis as determined in the Attachment 23. The reports shall be submitted by the 3rd business day of the subsequent week for weekly reports, 15 calendar days after the end of each month for monthly reports, or 15 calendar days after the end of the quarter for quarterly reports.

4.2.2. The frequency of report 2 submission is identified in the Task Order Requirements (Attachment 23). If weekly, monthly, or quarterly reports are requested, the Contractor shall submit, via email, a Microsoft Excel report to the Service and Agency Headquarters, QAE or COTR and the COR as outlined below. The report shall consist of the following categories: Service/Defense Agency, Organization, Commercial Travel Office, Passenger Name, Passenger telephone number (if available), Airline, Date of Ticket Issuance, Airline Ticket Number, Fare Basis Code, Cost of Original Ticket, Date of Refund Request, Refund Value and Travel Order number (if available). One report shall be generated listing each site in the Task Order. The report shall also include the total number of unused tickets on a weekly, monthly or quarterly basis as determined in the Task Order. The reports shall be submitted by the 3rd business day of the subsequent week for weekly reports, 15 calendar days after the end of each month for monthly reports, or 15 calendar days after the end of the quarter for quarterly reports.

4.3. Unused E-Ticket Report

4.3.1. The Contractor shall submit two unused E–ticket reports titled report 1 and 2. The frequency of report 1 submission is identified in the Task Order Requirements (Attachment 23). If weekly, monthly, or quarterly reports are requested, the Contractor shall submit, via email, Microsoft Excel report to the Service and Agency Headquarters, QAE or COTR and the COR as outlined below. The report shall consist of the following data elements: number of cancelled tickets; value of cancelled tickets; number of unused travel segments; value of unused travel segments; value of requested refunds; and value of refunds received. One report shall be generated listing each site in the Task Order. The report shall also include the total number of unused tickets on a weekly, monthly or quarterly basis as determined in the Task Order. The reports shall be submitted by the 3rd business day of the subsequent week for weekly reports, 15 calendar days after the end of each month for monthly reports, or 15 calendar days after the end of the quarter for quarterly reports.

4.3.2. The frequency of report 2 submission is identified in the Task Order Requirements (Attachment 23). If weekly, monthly, or quarterly reports are requested, the Contractor shall submit, via email, a Microsoft Excel report to the Service and Agency Headquarters, QAE or COTR and the COR as outlined below. The report shall consist of the following categories: Service/Defense Agency, Organization, Commercial Travel Office, Passenger Name, Passenger telephone number (if available), Airline, Date of Ticket Issuance, Airline Ticket Number, Fare Basis Code, Cost of Original Ticket, Date of Refund Request, Refund Value and Travel Order number (if available). One report shall be generated listing each site in the Task Order. The report shall also include the total number of unused tickets on a weekly, monthly or quarterly basis as determined in the Task Order. The reports shall be submitted by the 3rd business day of the subsequent week for weekly reports, 15 calendar days after the end of each month for monthly reports, or 15 calendar days after the end of the quarter for quarterly reports.

4.4. Premium Class Travel Report

4.4.1. The determination of report submission is identified in the Task Order Requirements (Attachment 23). The Contractor shall submit a monthly report, via email, Microsoft Excel report to the Service and Agency Headquarters, QAE or COTR and the COR as outlined below. The report shall consist of the following data elements: Service/Defense Agency; organization; CTO; passenger name; Grade/Rank (Sponsor's name and Grade/Rank if applicable); passenger work phone (Commercial and DSN with area code); Org/Dest; and mode (Airplane, Ship or Train), authorization number (if available), airline, airline ticket number, fare basis, date of travel, cost of original ticket, cost difference from YCA/lowest unrestricted coach fare. One report shall be generated listing each site in the Task Order. The report shall include the total number of premium class travel tickets on a monthly basis. The report shall be submitted by the 15th calendar day of each month and shall reflect travel performed during the previous month (e.g., the 15 January 2006 report shall represent travel performed in December 2005).

4.5. Travel Daily

4.5.1. The Contractor shall provide passenger name record data and support live PNR queue transfer via branch/bridge access to the Government.

4.5.2. The Contractor shall establish bridge/branch access between the Government and the Contractors pseudo city codes (PCC)/subscriber identifications (SID) which supports the creation, modification, cancellation, and ticketing, of DoD passenger name records (PNRs) to include official (i.e. CTO Assist (i.e. Traditional) and DTS) and nonofficial (i.e. LICWO, Contractor Support, etc.) travel arrangements for the sites identified under this task order. The Contractor shall ensure the bridge/branch access includes PCCs/SIDs designated for on-site staffed offices and off-site support/fulfillment such as call center service, emergency after-hours support, sub-contractor support, virtual agents, quality control, etc. The Contractor shall also establish a queue for each PCC/SID which shall be designated for the PNRs rejected by the Government due to data submission errors. Once bridge/branch access has been established, the Contractor shall queue place all newly created, modified, cancelled, and ticketed PNRs to a designated queue in the Government’s PCC/SID. The Contractor shall ensure each queued PNR contains the data elements in the applicable global distribution system (GDS) format provided in Attachment 17. Prior to implementation, the contractor may propose alternate PNR locations/GDS entries for the PNR data transfer GDS entries in a written request to the Contracting Officer. The Government will review the request and notify the Contractor whether approved/disapproved in writing. For DTS transactions, if the data element is not passed to the Contractor via the PNR, the Contractor is not required to enter the data field. The Contractor shall adhere to the guidance provided in Attachment 17 for establishing bridge/branch access, queue placement, PNR data processing instructions, and correcting data errors. The Contractor shall establish a unique alpha identifier for each site under this task order. The unique alpha identifier shall not exceed 30 characters. Additionally, the Contractor shall provide an excel spreadsheet to the DTMO COR containing each PCC/SID supporting travel services as outlined above, to include ARC/IATA number, and unique alpha identifier for each site identified under this task order in accordance with the instructions provided in Attachment 19.

4.6. Commercial…