.Net Sabre Car renting search/booking sample application

!!Please do not bid on this project if you do not have Sabre credentials for using of Sabre web-services. Project is to develop an example prototype MS VS 2010 .NET console client application which calls the Sabre XML Web Services to search/check car renting availability/booking/validation status/booking cancellation. Program inputs are target airport codes, distance to airport, and requested dates. Program must use recent version of the Sabre OTA XML web services: establish an appropriate Sabre session, issue location and car availability queries, then close the session. Deliverables include working source code and prototype application, which we will test with our Sabre credentials. 1. This is what I’m expecting to get as end result: - Source code of VS2010 VB/C# (your choice, but VB is preferable, because first part is developed on VB). Project should have web-references to recent version of each type of Sabre call. - Backup of SQL DB (SQL 2008 is preferable; about DB structure see below). 2. Please check attached Sabre workflow information archive file. In project you need to implement: - “Vehicle Workflow No. 1 Without a PNR in the Sabre Work Area1”, - “Workflow No. 4 - Modify a PNR1”, - “Workflow No. 6 - Cancel a PNR1”, - “Workflow No. 7 - Modify a PNR by Adding a Vehicle Segment1”. Functionality for each workflow should be implemented on separate screen (form) or tab on the single form. Sabre credentials and SQL server connection should be managed on separate form. 3. Full list of Sabre web-services you have to use in these workflows are: SessionCreateRQ SessionCloseRQ VehLocationListLLSRQ OTA_VehAvailRateLLSRQ VehRateRulesLLSRQ TravelItineraryAddInfoLLSRQ AddRemarkLLSRQ OTA_VehResLLSRQ EndTransactionLLSRQ OTA_TravelItineraryReadLLSRQ TravelItineraryModifyLLSRQ OTA_CancelLLSRQ - Note - SessionCreateRQ/SessionCloseRQ should be a part of each workflow implementation. You do not need to create Session pool functionality. - Note – Sabre returns response with limited number of records (if I’m not wrong by default it is 11) and flag which shows do we have more data for this request or not. Your functionality should guarantee processing of completed set of data we have on Sabre. - Request/Response for each call (except SessionCreateRQ/SessionCloseRQ) should be recorded in SQL table as XML. - Response of each Sabre call should be parsed and recorded in SQL tables with proper format accordingly of response XML schema. We have to have possibility query of data from linked tables and to see what we got from Sabre in XML (unparsed value). 4. “Vehicle Workflow No. 1 Without a PNR in the Sabre Work Area1”  Screen should have: - dropdown to select airport code (if you need I can send to you list of airports with code and name). If you would like to simplify, you may have edit control for airport code value, no validation against of airport code list required). It is your choice… - Edit control for distance value; - Radio buttons for distance UOM (miles or kilometers).  List of returned by VehLocationListLLSRQ location should be displayed in the grid or dropdown. Selected by user value (from this list) should be used next OTA_VehAvailRateLLSRQ.  Value selected by user from results of OTA_VehAvailRateLLSRQ should be used for following VehRateRulesLLSRQ call.  TravelItineraryAddInfoLLSRQ should use for using of PNR all possible parameters from screen (set of edit controls with validation only required parameters)  AddRemarkLLSRQ should use new PNR object and information from a screen to add item remarks.  PNR object and OTA_VehAvailRateLLSRQ /VehRateRulesLLSRQ data should be used OTA_VehResLLSRQ call for creation of car PNR segment.  Save car reservation using EndTransactionLLSRQ  Now we have PNR car reservation info recorded in our SQL DB. This information should be used in implementation of rest workflows. 5. Application should keep details of made car reservations with current statuses.