rfp# 554-18-100 common use passenger processing … · 2018. 5. 9. · rfp# 554-18-100, common use...

RFP# 554-18-100, Common Use Passenger Processing System - Addendum #2 of 18

RFP# 554-18-100 COMMON USE PASSENGER PROCESSING SYSTEM

ADDENDUM #2 Issued on May 9, 2018

The purpose of Addendum #2 is to:

• Update the RFP schedule (which includes a new proposal due date); • Answer questions that were received by the specified due date and time; • Provide an RDU Existing Equipment Listing; and • Provide a copy of the pre-proposal attendance sheet;,

UPDATED SCHEDULE

Updated RFP Schedule (update to schedule provided on page 3, Section B of RFP) below:


QUESTIONS & ANSWERS

1. Can you please send me a version of the RFP document that has Form Fill-able capabilities? No, a fillable version of the RFP is not available.

2. Can companies from Outside USA can apply for this? (like,from India or Canada) Yes.

3. Will the successful Contractor need to come over there for meetings? Yes. The PM will

be required onsite for meetings regularly and other key staff will be expected onsite as needed.

4. Can we perform the tasks (related to RFP) outside USA?(like, from India or Canada) Depending upon the proposed solution, a significant portion of the work will be required onsite.

5. Can we submit the proposals via email? No.

6. Page 9 of 25 under Submission Requirements, states that our proposal should be bound (mid-page). Further down at the bottom of the same page, it states all proposals should be unbound. Hard copy proposals should be bounded (not unbound).

7. Page 38 -- Section H Counting MWSB Participation, “For the purposes of MWSB participation, MWSB firms are counted as either minority-owned businesses (MB) or women-owned businesses (WB).” Does this mean that if a Sub-contractor is both a MBE and WBE small business that they cannot be used to satisfy BOTH MWSB requirement, but instead can only be submitted as one or the other? RDU does not have subcontractors that are certified as both MB and WB. Subcontractors can only fulfill one side of the goal. They are either MB or WB, and would count as such.

8. Page 39 – Section I.1 MWSB Program Requirements, “Agreements between a proposer

and an MWSB in which the MWSB promises not to provide proposals/quotes to other bidders are prohibited.” Does this statement mean that a MWSB subcontractor may be submitted with different/multiple Primes or proposals? This means that a Prime Bidder cannot leverage or force a MWSB subcontractor to only submit to their company. There should not be any agreement with any MWSB with any prime to limit or try to limit whom they can submit quotes.


9. Part of the RFP requires a PCI DSS response. When responding to the PCI DSS requirements, the merchant should conduct a scoping exercise to determine which requirements belong to them and which they will outsource to service providers or managed services providers. In an airport environment, the airline merchants must rely on the airport authority to provide most of the requirements. It is assumed that outside of the airline application and airline host gateway all other requirements inside of the airport will be performed by either the airport, network provider, or other 3rd party vendors (such as common use provider). When the airport authority does their own scoping exercise (with or without the assistance of a QSA), they will discover which requirements make sense to deliver internally and which to contract outside vendors to deliver. Can the airport clearly defining these boundaries? The RFP requires that the proposer “Provide a description of the proposed solution’s approach to PCI DSS and how the solution secures data in transit and at rest.” The technical requirements state “The Common Use Solution Provider shall thoroughly describe its position with regard to PCI DSS. The Common Use Solution Provider shall also describe its approach to ensuring that the RDUAA will not be held liable for violations of the PCI DSS relative to the common use system.” As noted in Requirement 5.2.0, PCI is expected to be addressed during a Joint Application Design session during the project.

10. Please advise if RDUAA has a planned start-date and end-date or is RDUAA looking for the

vendor to provide a suggested schedule? By what date does RDUAA expect completion/full implementation of all systems/services? As noted in the Response Requirements, the solution provider is expected to provide a High-Level Milestone Schedule. The entire system must be through all testing and fully-accepted by March 31, 2019.

11. It is our understanding that RDUAA has an existing VMware environment. Is it RDUAA’s

intension to provide all virtual environment requirements to host the proposed solution or should the tenderer provide their own environment; either virtual or physical? It is the responsibility of the solution provider to propose the appropriate system architecture for the proposed system. The use of RDUAA’s environment is an option if proposed.

12. If RDUAA will provide compute resources in the existing RDUAA Virtual Environment, what other COTS products would also be provided by RDUAA? i.e.: (a) Windows Server Licenses; (b) Windows CAL licenses; (c) Backup software/solution; (d) Anti-virus software. Vendor should propose what they believe is best. RDUAA can provide some or all licenses for on premise solution if proposed.

13. If the proposed solution has an on premise hardware requirement, will RDU provide rack

space and power or should the tenderer provide required racks/UPS/etc.? Yes. If it is an on premise solution and there is no demand for physical hardware. Propose your best recommended solution.


14. Will/Can the Test environment also be implemented on the existing RDUAA Virtual Environment or should the tenderer provide all necessary hardware/software? Yes. If it is an on premise solution.

15. Is the Test environment required to be an exact duplicate of the production solution, or can it be non-redundant and provide the full/equivalent functionality of the production solution? Yes. An exact duplicate with full / equivalent functionality. Redundancy is not required.

16. CUPPS: 2.8.1: “Hardware shall include”. Q: Can you clarify if the MSR/OCR hardware must be PCI compliance? The RFP requires that the proposer “Provide a description of the proposed solution’s approach to PCI DSS and how the solution secures data in transit and at rest.” The technical requirements state “The Common Use Solution Provider shall thoroughly describe its position with regard to PCI DSS. The Common Use Solution Provider shall also describe its approach to ensuring that the RDUAA will not be held liable for violations of the PCI DSS relative to the common use system.” As noted in Requirement 5.2.0, PCI is expected to be addressed during a Joint Application Design session during the project.

17. CUSS Kiosk: 3.3.9. Q: Can you clarify what is "RFID boarding pass printer?” “RFID boarding pass printer” is a typo. Exhibit A – 3.3.9 will reflect the following update below in yellow.

CUSS Kiosks 3 3 9 The Common Use Solution Provider shall provide the following hardware, as required to support the CUSS: - All required components, such as workstations, monitors, MSR/OCR scanners, boarding pass printers, and RFID bag-tag printer - Servers as required to support the proposed system - Network appliances as required to support the proposed system - Ancillary appurtenances required to support the proposed system


18. CUSS Kiosk: 3.3.0. Q: Do the kiosks need to be ADA compliant? Requirement 3.3.0 states “The Common Use Solution Provider shall provide a CUSS hardware and software platform that conforms to IATA RP 1706c, to include 75 freestanding units, ADA compliance, Multilingual capability, RFID Bag-Tag Printer, Millwork finishes as coordinated with RDUAA”.

19. Requesting an inventory listing of all existing equipment used in CUPPS, CUSS, AOBD/RMS, CMS systems. Please use the “RDU Existing Equipment” list below. We have just started the process to create an updated inventory list.

20. ClearChannel to RMS for advertisement. Confirm Relationship and expectation of displaying Clear Channel advertising content on RDUAA CMS Monitors? Any new CMS will need to display ClearChannel content without limitation.

21. BICS. Provide Make/Model, age & locations of all BIC’s. All BICs in Terminal 2 are ET215BAG 1330: 08080064, 08080066, 10110077 –( all are new) These are spare BICs :

• 1370B Office: 10110080 – Test BIC • 1E- 08080069 • 1W- 10110079 • 2E- 08080059 • 2W- 08080067 • 3E- 08080068 • 3W- 10110078 • 4E- 08080065 • 4W- 08090009 • 5E- 08080061 • 5W- 08090008

22. Airline Host Connectivity. Please confirm RDUAA will provide networking required to use existing airlines’ host connectivity to the selected vendor’s environment. Yes. RDU will provide network connection to our existing airline hosts.

23. RFID Kiosks. Questions: Do Existing CUSS kiosks have RFID Bag Tag Printer? If so/which airlines use them? No.


24. Test Environment. Questions: When in the project schedule is the build out of the Test environment envisioned? Will configuration of new airline application also be done in lab before deployment to production? Which organization will be responsible to add new airlines? Once a working production environment is completed. The production environment will be replicated to create the test environment and updated periodically to be an exact duplicate of production. Yes, configuration of new airline application will also be done in lab before deployment to production. The Common Use vendor in coordination with the airline.

25. Consumable. Questions: Who is current stock vendor providing stock to RDUAA? Please provide reports of # of Boarding Pass, Bag Tags, CUSS Boarding and CUSS Bag Tag printer over one Calendar year. RDU purchase current stock from 3 approved vendors: Magnetic Ticket & Label (MT&L) – typically gets our boarding pass order, Print-o-Tape – typically gets our bag tag order and RR Donnelley – Typically gets our CUSS kiosk stock order.

26. Please provide reports of # of Boarding Pass, Bag Tags, CUSS Boarding and CUSS Bag Tag

printer over one Calendar year. Boarding Pass – 3.2500 x 8.0000 Direct Thermal Paper Receipt Stock. 900 master cartons. 5 inner boxes per master carton. 1000 receipts/inner box. Totaling 4.5 million boarding passes. This is what we purchased the last budget year. There may be carryover stock from the previous year. We use approximately 300-450 inner boxes a month with an average of 375 inner boxes per month. Bag Tag – 600 Master Cartons consisting of 5 Individual Boxes of 625 tags per box. 3,000 individual boxes. 1,875,000 tags total. 21” Bag Tag Stock for VidTroniX ATP3 Printers. Average is about 250 individual boxes a month. We used to be 450 individual boxes a month but Delta has been providing their own RFID stock. If we go all RFID, 450 is the average we’ll have to consider. CUSS Kiosk Rolls – 700 Rolls purchased. Average about 60 rolls a month. Roll Width: 8” Roll Length: 1,134’ Stock: Alpha 800 3.4 Direct Thermal Paper Ink: 1/0 (Black Ink Only) Perforation: 1 Full Parallel Perf Packing: 2 Rolls/Carton – side x side with 1 piece of chipboard placed between the rolls. OkiData Sabre – Manifest R46 Sabre Paper for dot-matrix OkiData printers – Average about 55-60 boxes a month. 700 for the year. OkiData “ink” Ribbons – OKI52102001. Average 35 a month. 420 a year.

27. In order to do due diligence following the pre-bid meeting, would the Raleigh-Durham

Airport Authority (RDUAA) please grant a minimum 3-week extension to the due date? Refer to the updated schedule provided within this Addendum.


28. Section III, A. Financial Capacity of the RFP on page 8 of 25 states in relevant part “As part of your proposal a list of any contracts where proposer was terminated including an explanation why and a list of any past bankruptcies must be included.” Can RDUAA provide a time period of any such terminations or bankruptcies, such as in the past five (5) years? Is the requested statement limited to terminations or bankruptcies within the United States? Yes, the last five years will suffice, however the Authority has the right and discretion to further investigate and ask for more than just the immediate five year past, if needed. No, it is not limited to terminations and bankruptcies within the US.

29. Proposer notes that RDUAA reserves the right “to discuss and negotiate with selected Proposer(s) any terms and conditions in the Proposals including but not limited to financial terms.” (RFP, Section V.A.viii on page 11 of 25). May Proposers include any exceptions to the terms and conditions of Exhibit C Sample Agreement in its proposal for further discussion and negotiation upon selection? Or does the Authority expect Proposers to pose specific questions regarding the terms and conditions of Exhibit C Sample Agreement as part of the question and answer process? Yes, the proposer may submit exceptions to the terms and conditions of Exhibit C in it’s proposal for review by the Authority, however due to the time sensitive nature of this project the Authority is not interested in extended negotiations on terms and conditions in order to reach a final agreement. Note page 7 of 25 in the RFP, the second and third paragraph’s on that page. We prefer not to have the conflicting Contractual Terms and Conditions keep us from making our estimated start date.

30. It is understood that some equipment is over 8 years old. Can RDUAA please provide a complete list of equipment indicating which devices will be retained and which devices will need replacements, and their respective quantities and age including existing peripherals (i.e. Vidtronix printers)? Please use the RDU Existing Equipment list provided below. RDU just started the process to create an updated inventory list.

31. What CUSS platform is RDUAA currently using? Embross

32. Who is responsible for repairing the existing kiosks at RDU? Currently, Tier 1 Break/Fix is covered by the Common Use contractor and RDU purchases the equipment.


33. What model of kiosks are being used at RDU and can RDUAA list the components (i.e. peripherals, PC, sensors, any lighting options, remote monitoring capabilities, etc. N2, N7 and T-series. Components will be listed in the updated inventory list.

34. Is it RDUAA's intention that existing kiosks be certified and integrated into the proposer's Common Use platform? No for existing kiosks. RDU expects any new offering of kiosks to be integrated into the platform.

35. If existing kiosks must be integrated into the proposer's platform, please provide a list of

the PC used and all hardware and peripherals, sensors, any lighting options, remote monitoring capabilities, especially any hardware options not defined by the CUSS standard. Existing kiosks will not be integrated.

36. Exhibit A (req. ID 2.3.0 on line 36) mentions a DCS requirement can RDUAA explain how this will be used and what the requirements are? The vendor is required to work with the major carriers to ensure that the carrier’s DCS is certified on the new platform.

37. Will the selected provider’s product servers reside as VMs (Virtual Machines) on RDU

Airport Authority virtualization hypervisor infrastructure? If yes, what are the details on this virtualization hypervisor infrastructure (e.g. HyperV, VMware, Version, Backup solution, Antivirus protection, etc.)? Provide your best solution in accordance with the RFP requirements.

38. How many Common-Use Workstations, CUSS Kiosks, RMS workstations, and FIDS monitors will there be at RDU? Currently numbers are: CUPPS Workstations in use – 143 plus 4 lab workstations = 147 total; CUSS – 73 Kiosks – 72 in production and 1 lab; FIDS – 335

39. Does RDU have an existing MPLS network on which the selected provider could be given its own VRF (or collection of VRFs)? No.

40. The POC appears to provide no clear opportunity for meaningful M/WBE participation as

it requires the proponents’ products, proprietary knowledge and professional services (reusing as much of the existing/installed hardware as possible); please advise whether the Authority’s 7% MBE and 4% WBE participation goals are transferable, post-selection/award, to the successful POC project proponent. Please complete the requirements of Exhibit B, as provided in the RFP document.


41. Please identify the composition of the RDU evaluation/selection committee for this RFP by role and responsibility. This information is To Be Determined (TBD).

42. What are the signatory airlines operating at RDU? Other airports categorize carriers as either signatory or non-signatory. At RDU we do not categorize air carriers as signatory or non-signatory. This list does not include regionals that fly on behalf of the “major” carriers: Air Canada, Alaska Airlines, Allegiant Air, American Airlines, Delta Air Lines, Frontier Airlines, JetBlue Airways, Southwest Airlines, United Airlines.

43. Can you confirm that all CUPPS workstations are currently connected to the RDU network

and not to an independent Ultra network? How many RDU managed network ports are available at the devices location? Yes. They are all connected to the RDU network. Common Use vendor needs to state port needs/requirements for their best solution.

44. Are all CUSS kiosks currently connected to the RDU network or to an independent Ultra network? How many RDU managed network ports are available at the devices location? Yes. They are all connected to the RDU network. Common Use vendor needs to state port needs/requirements for their best solution.

45. Are all Document Printers (HP Laser and Okidata) currently connected to the RDU network or to an independent Ultra network? How many RDU managed network ports are available at the devices location? Yes. They are all connected to the RDU network. Common Use vendor needs to state port needs/requirements for their best solution.

46. Are all FIDS currently connected to the RDU network or to an independent Ultra network? How many RDU managed network ports are available at the devices location? Yes. They are all connected to the RDU network. Common Use vendor needs to state port needs/requirements for their best solution.


47. Are all BICs and Baggage Claim Workstations currently connected to the RDU network or to an independent Ultra network? How many RDU managed network ports are available at the devices location? Please note: BIC refers to the devices the baggage handlers use to set the First Bag, Last Bag, etc. at the belt locations. Please note: Baggage Claim Workstations – These would be any full-fledged workstations available for use in the baggage area, not to be confused with BICs. Yes. They are all connected to the RDU network. Common Use vendor needs to state port needs/requirements for their best solution.

48. What version of ESXi does RDU use on their VMWare headend? Version 6.0 Update 3

49. What Resources does the airport currently manage; example: ticket counters, airplane parking spots (remote, at gate, cargo, etc.)? Provide best solution based on RFP requirements.

50. What specific AODB/RMS problems is the Authority experiencing using multiple date feeds to drive FIDS? Provide best solution based on RFP requirements.

51. Please provide detailed specifications of the existing hardware. Inventory to this level of detail is not readily available, on the site walk solution providers were given the opportunity to make note of equipment in use. RDU has provided as much information as possible at this time.

a. CUPPS Workstation:

i. Confirm Quantity, 147 ii. Manufacturer: Lenovo Thinkcentre M710 Tiny

iii. Model: 10MR004JUS iv. CPU: Core i3-6100T 3.2Ghz v. RAM: 8 GB

vi. Number of Serial Ports: 0 vii. Number of Network Ports: 1

b. FIDS Client:

i. Quantity: 335 ii. Manufacturer: Lenovo

iii. Model: ThinkCentre M710q iv. CPU: Intel Core i3 6100T 3.2Ghz v. RAM: 8 GB

vi. Hard Drive Size:128 GB SSD vii. Graphic Processing: Integrated or Discrete? Integrated


viii. Number of Serial Ports:3 ix. Number of Network Ports:1

c. FIDS LEDs:

i. Quantity: ii. Manufacturer: NEC - 46 and 55 inch units

iii. Model: IDP461-2-G or a P 551 iv. Serial Number:

d. BIC Console (PC or small keypad?):

i. Manufacturer: All BICs in Terminal 2 are ET215BAG ii. Model:

iii. Serial Number: • 1330 : 08080064, 08080066, 10110077 – all are new – These are

spare BICs • 1370B Office: 10110080 – Test BIC • 1E- 08080069 • 1W- 10110079 • 2E- 08080059 • 2W- 08080067 • 3E- 08080068 • 3W- 10110078 • 4E- 08080065 • 4W- 08090009 • 5E- 08080061 • 5W- 08090008

e. Baggage Makeup Workstations (See question #10 for relevance):

i. Quantity: 4 ii. Manufacturer: Vtona (VXL)

iii. Model: V200 iv. CPU: Teradici Tera 2321 PCoIP v. RAM: 512 MB DDR

vi. Hard Drive Size: vii. Number of Serial Ports: 2

viii. Number of Network Ports: 1

f. Vidtronix MAPs: i. Quantity: 74

ii. Serial Number: iii. Firmware version: 3.307.98M3.ae


g. ATP3s: i. Quantity: 89 (including RFID)

ii. Serial Number: iii. Firmware version: 3.307.98B3.ae (Standard) 5.378.112B3.ax (RFID)

h. CUSS Kiosk Units:

i. Quantity (of each model): • N2 - 39 • N7 - 28 • T-Series - 6

ii. Manufacturer: • N2- BCM • N7- DFI • T-series – DFI

iii. Model: V110/490

iv. CPU: Core2 Duo T7400 @ 2.80 GHz

v. RAM: 2GB

vi. Hard Drive Size: 250GB

vii. Graphic Processing: Integrated or Discrete? (e.g.: Onboard Intel 530 or NVIDIA®

GeForce® GT730 2GB)

viii. Number of Serial Ports: 2

ix. Number of Network Ports: 2

i. MSR/OCR keyboard model & firmware version OR serial number? Quantity?

i. Access-IS

ii. Serial Number: 1103-

iii. Quantity - 147

j. BGR model & firmware version OR serial number? Quantity?

i. BGR 120S ii. Firmware/Serial – Unknown

iii. Quantity - 37

k. Cisco VoIP phone model? 8841


52. IED paging equipment list; model of paging stations at a minimum (e.g. 524-H)? This information is not needed in order to submit a proposal. If needed, this information will be provide at a later date to the successful contractor(s).

53. Future growth: this is estimated at 50%. Over what period is this expected? Over the life of the contract (approximately 5 years).

54. Evaluation criteria: will points be allocated to the criteria? If so, may we know what they

are? This is to be determined (TBD). The Authority strongly encourages that proposer offer their very best solution (for all criteria within the RFP) to be evaluated.

55. Will e-mail proposal submissions be acceptable? No.

56. Will A4 (8.27 x 11.69 format be acceptable? Yes, for the hard copy, bounded proposal.

57. Warranty period: may we suggest that new airlines that begin operations after the warranty period will covered by standard L3 support subject to their requirements? All airlines utilizing the common use system shall receive equal support throughout the term of the support contract.

58. With regard to page 2, section 1A. “The Authority’s intent is to select a single firm (one prime contractor) to provide the best solution and support, however the Authority may consider selecting separate firms based upon best overall value and fit.” How would you treat an RFP response from any given vendor that only covered part of the scope of work requested – would you compare that on its relative merits against the response of vendors who have responded against all of the scope or would you evaluate negatively or even omit it from your evaluation as a partial response? The “best overall value and fit” will be determined by multiple factors, including the cost, expandability, interoperability and administrative impact on the Authority to procure and manage contracts from multiple providers as well as the overall quality and service provided to the airlines. It is important to the Authority that the common use system procured through this RFP be capable of integrating new emerging technology services through interoperability with best-in-class future solutions from other solution providers, in accordance with ACI-World ACRIS interoperability Recommended Practices or other such industry wide interoperability standards.

[END OF QUESTIONS AND ANSWERS]


RDU Existing Equipment Listing

Line # EQUIPMENT: SPECIFICATIONS: 1 NEC LCD4620-2-BK / 4620-BK-A VT / 46-P461 2 NEC LCD5710-BK 3 NEC LCD6520L-BK 4 NEC LCDS5-P551 / X552S 5 NEC LCD7O-P701 6 NEC LCD32-V321 / V322 7 NEC X551S / X551UN 8 Access BGR120S 9 Access ATB 422/423 Keyboard / ATB247-MDOP

10 Access LSR120S 11 Dell Wyse P25 12 VBrick XTV125D 13 IBM AMM Blade Center 39Y9661 14 IBM HC10 Blade Center Chassis 8677 15 IBM Switch Modules FRU # 32R1895 16 IBM 2000W Power Supply Modules 39Y7360 17 IBM CP20 Workstation 3096CDX 18 IBM Server Blade HS-21 43W4015 19 IBM Workstation Blade HC10 20 IBM Kiosks 9988 / 9988-E12-N7 21 Master Clock SKA-508R / CLKNTD18-SS-POE 22 Daktronics LEDX1001 23 Daktronics AE-3010 24 Daktronics AF-3400 25 HP Printer 4014n Laser Printer 26 Lenovo Monitor 9417-HC2 / 9227-AD1 / 5047-HB2 27 Lenovo Workstation M57p E6550 28 Samsung Monitor 9227-AD1 29 OKIdata Printer Microline 320 Turbo 30 Vidtronix ATP3 ATP3/S/N 31 Vidtronix MAP 32 Pixelink LCD Richardson 32"LCD 33 Tugman Terminal Keypad ET215 / ET315 34 Tripp Lite AGPS5519 35 Serial Gear Adapter CS-42042 36 Hewlett Packard Thin Client T5540 CE / T5745 CE


37 38 39 SOFTWARE: 40 Microsoft Windows XP / Windows 7 41 RedHat Enterprise Linux 42 mM Kiosk Middleware 43 IBM Kiosk Manager 44 Ultra Applications: UltraAODB 45 UltraFIDS 46 UltraRMS 47 UltraCUSE 48 UltraSEATS 49 UltraConnect 50 51 52 SERVERS and STORAGE: 53 IBM P5 Server 54 mM SAN N5200 55 IBM SAN N5300 56 IBM IBM server x3550

[REMAINDER OF PAGE INTENTIONALLY LEFT BLANK]


Copy of the pre-proposal attendance sheet


[THIS PAGE INTENTIONALLY LEFT BLANK]

END OF ADDENDUM #2

rfp# 554-18-100 common use passenger processing … · 2018. 5. 9. · rfp# 554-18-100, common use...

Documents