FILE | 70 | TWIC HAND-HELD READERS - Amended Attachment E (TWIC Price Scenario Worksheet) - TWIC Questions and Responses - Amended Attachment D (TWIC Vendor Demonstration Scenario)

FBO DAILY ISSUE OF JULY 18, 2008 FBO #2426
DOCUMENT

70 -- TWIC HAND-HELD READERS - Amended Attachment E (TWIC Price Scenario Worksheet) - TWIC Questions and Responses - Amended Attachment D (TWIC Vendor Demonstration Scenario)

Notice Date: 7/16/2008
Notice Type: Amended Attachment D (TWIC Vendor Demonstration Scenario)
NAICS: 334119 — Other Computer Peripheral Equipment Manufacturing
Contracting Office: Department of Homeland Security, United States Coast Guard (USCG), Commandant (CG-912), U.S. Coast Guard Headquarters, U.S. Coast Guard Headquarters (CG-912), 1900 Half Street, SW, Washington, District of Columbia, 20593-0001
ZIP Code: 20593-0001
Solicitation Number: HSCG23-08-R-MMN450
Point of Contact: Ijeoma Ezeonwuka,, Phone: 202-475-3236, Beverly R. Fowler,, Phone: 202-475-3212
E-Mail Address: ijeoma.ezeonwuka@uscg.mil, Beverly.R.Fowler@uscg.mil
Small Business Set-Aside: N/A
Description: This combined synopsis/solicitation HSCG23-08-R-MMN450 is hereby amended to respond to the following Vendor questions received. The following attachments are included and are hereby incorporated into this solicitation: TWIC Questions and Responses, (Amended) Attachment D: Vendor Demonstration Scenario and (Amended) Attachment E: Price Scenario Worksheet. 1. What will be the driver in determining whether the USCG purchases 10 versus 300 devices? Response: This initial delivery order for 10 TWIC Hand-Held readers will be issued concurrently with the Contract. Additional delivery orders depend upon operational need and availability of funds. 2. On what date will the demonstrations begin? Response: Product Demonstrations will be held from 11 August 2008 through 14 August 2008 at the United States Coast Guard Headquarters in Washington, DC. After the receipt of proposals, Vendors will be provided with available time slots. 3. Is this opportunity related to the sources sought notice that was released awhile back for TWIC Hand Held Readers under # HSCG2307IMMN664? Also is this a new requirement, or is some one else currently doing the work? Response: Yes this is related to the sources sought notice (HSCG23-08-I-MMN450) posted back in April 2008 and this is a new requirement. 4. May we break the CLIN 00002 into quantities of 10 units by approximate zone of destination? Since the destination ports span a wide geographic area, your cost comparison projections may be improved if we inform you of shipping options (overnight, 2-day, ground) by a comparable quantity across USCG Districts. Response: Yes as long as there is a Grand Total Price for all 300 TWIC Hand-Held readers for price evaluation. Any proposal without a Grand Total Price may be rejected. 5. For the requested Quantity Discounts, would annual volume pricing bands between different quantity levels be most helpful? Volume bands may assist allocation of costs between individual port locations, and can be broken out to be very granular. Response: See response to Question 4. 6. Please confirm that Specification # 40A through 40F in the USCG TWIC Portable Biometric Reader specification are Objectives versus Threshold requirements. Response: Yes they are Objectives. 7. Can you let us know when (how soon after Aug 1 close date) and what city the intended Product Demonstrations are going to be scheduled Response: See response to Question 2. 8. What is the anticipated contract award date? Response: On or before 30 September 2008. 9. In Attachment A, Section 1.3.3 Employee Identification, FIPS 201 compliant credentials may be available for employees (depending on their expected length of time on the contract). Are you stating that a separate credential (showing clearance level) is required for personnel working on this contract? Response: No 10. In Attachment A, Section 1.13 Intellectual Property, is it the government’s intent that any development under this contract would be considered government use licensing? Response: Yes. In reference to Attachment A, Section 1.13 Intellectual Property, the Government shall own such rights to modifications made during the performance of the contract. 11. In Attachment A, Section 5.1.5 Inspection and Acceptance of the TWIC Hand-held Readers, please identify all functionality required in order for the hand-held readers to be considered in accordance with the USCG’s Independent Verification and Validation (IV&V). Response: This USCG’s Independent Verification and Validation (IV&V) will be provided after contract award. 12. RFP Reference: Solicitation, page 2, “CLIN 0002: Delivery (FOB Destination).” Question: What numbers of units per shipment should bidders use for CLIN 0002? Response: The initial delivery order and shipment will be for 10 TWIC Hand-Held readers. Additional delivery orders and shipments depend upon operational need and availability of funds. In accordance with the solicitation, it is preferred that a standard delivery price (s) be quoted (F.O.B Destination) for the readers. 13. RFP Reference: Solicitation, page 2, “CLIN 0004: Travel (excluding travel for training shall not exceed $25,000).” Question: Are labor costs associated with CLIN 0004 included in the $25,000 figure? If not, will the USCG be opening a different CLIN for labor? Response: There will be no labor costs associated with CLIN 0004. 14. RFP Reference: Solicitation, page 7, Proposal Page Limit Question: Will the USCG consider the use of “11x17 fold-outs” for graphics as part of the page limit? Response: Yes 15. RFP References: Attachment A, Section 5.1.4 Software Updates and Table 7.1 Deliverables and Delivery Schedule; Attachment B, Line 7D “Attachment B, Line 7D: The reader shall also read the Seafarers’ Identity Documents (SID) and conduct a comparison of the individuals biometric to the template stored in the bar code. – THRESHOLD” “5.1.4 Software Updates: Based on current versions of the TSA TWIC reader hardware and card application specification, the Contractor shall provide fully tested software updates to the TWIC hand-held readers after the COTR approves that these software updates are necessary. The Contractor shall also provide software patches as needed. It shall be the responsibility of the Contractor to be aware when current versions of the TSA TWIC reader hardware and card application specification are made available and if software updates are needed. “Table 7.1 Deliverables and Delivery Schedule: 30 days after current versions of the TSA TWIC reader hardware and card application software is released. Question: This is an open-ended requirement within a FFP contract and does not address modifications to the TWIC/SID specifications that may affect fundamental changes in hardware as well as software. Will the USCG define such hardware and software updates as a separate contract line item number (CLIN) subject to price and scope negotiation on an as-needed basis? Response: Yes. Attachment E (TWIC Price Scenario Worksheet) has been amended to include this new CLIN structure and it is subject to negotiation after contract award. 16. RFP Reference: Section 5.1.5 of Attachment A to the Solicitation Question: Will a copy of the USCG’s Independent Verification and Validation (IV&V) criteria be provided? Response: See response to Question 11. 17. Page 3, first paragraph, under 1) Technical Capability: b) – is the inclusion of product literature required or optional? The word used here is “should”. Response: If the product literature is an essential component of the proposal then it is recommended that it should be included. Please note that the product literature is included in the page limit. 18. Page 3: 2) product demonstration; is the contractor limited to 45 minutes? Is this a defined cut-off point in the demo? Response: Yes, the demonstration is limited to 45 minutes 19. Page 4: 5) Relevant Past Performance: can you define further the language that asks that past performance descriptions pertain to readers that are the “same as or similar to the requirements specified in the above specifications and PWS”? Since the TWIC specifications are relatively new and there have only been pilots heretofore as part of TWIC phase III, it is highly unlikely that readers will have a track record in TWIC usage under the current specifications. Therefore, what constitutes “similar to the requirements”? Response: It is understood that the TWIC Hand-Held requirements are relatively new however “same as or similar to” in this solicitation would refer to for example other “same as or similar” biometric readers. 20. Page 7: Proposal Page Limit: does the font size limitation for Volume II also apply to Volume I? Response: Yes. 21. Attachment A: 1.3.3. Employee Identification: who is responsible for supplying the required identification badge? Response: The United States Coast Guard 22. Should the ORCA be sent in paper form? Response: No, please reference the online link in the price proposal. 23. In the referenced FAR clause, 52.212-5, you indicated that clauses 14 - 21 were applicable. Clause 14 indicates a total service-disabled veteran-owned set-aside. Is this correct? Response: No. Please disregard this clause. The resultant contract will omit the clause. 24. Should we assume that the maximum 12 training courses for CLIN 00003 will be conducted in the Washington, DC Headquarters and leverage your facilities? We may utilize a zone-based approach for geographically-dispersed training and save your team's travel time and expenses by doing so. Also, use of your current facilities will save costs for rental of appropriate training space. Response: In addition to the USCG Headquarters in Washington DC, other training locations could include the USCG units in Western Rivers, Gulf Coast, Great Lakes, West Coast and other East Coast Locations. 25. What other activities are potentially envisioned for travel requirements encompassed by CLIN 00004 outside of the Kick-Off meeting and occasional status meetings by purpose and frequency? Our team is adept at utilizing virtual meeting facilities, including online conferencing and secure online forums, and can potentially save travel costs. Response: There are no other activities envisioned for travel requirements outside of the Kick-Off meeting and occasional status meetings. 26. Please clarify the TWIC and PIV Specification with the Two TWIC Cards Presented Simultaneously Use Case (Demonstration Scenario 5). a.It’s not clear what the term “reject” means. Does it mean that an error is displayed/logged, or can the card presentation just be ignored? Response: Both cards should be ignored as if none were presented. Attachment D (TWIC Vendor Demonstration Scenario) has been amended. b.Page 30 of the May 30, 2008 TSA TWIC specification says: “If two or more contactless smart cards are presented at the same time in a TWIC reader's contactless field, the TWIC reader shall reject all of the presented cards.” This contradicts the FIPS201 specification, which requires FIPS201 cards to meet standards defined in the ISO/IEC 14443 specification for contactless readers, and contradicts the standard anti-collision mechanisms as defined in ISO/IEC 14443-3:2001. Having a contradicting requirement will make multi-mode (e.g., PIV + TWIC) readers impossible. Response: Resolving anti-collision may or may not be supported by a reader (PCD). The ISO/IEC 14443-3:2001 standard limits requirements on the reader (PCD) to requiring “detection” of multiple cards (PICC) in the operating field. There is no language in this standard mandating a reader resolves a collision. c.This requirement is difficult or impossible to meet on some platforms with drivers that automatically perform anti-collision detection. The driver may serialize the card presentations to the terminal as though they were presented one after the other. The reader is not even aware of the multiple-card presentation, so it can’t reject the cards. Response: Respondents are encouraged to create new (or modify existing) drivers to support the required behavior of ignoring multiple cards presented at the same time. 27. Please clarify the CHUID with Biometrics Verification Use Case (Demonstration Scenario 2). a.In the CHUID With Biometrics Verification Use Case Scenario Purpose Section, may we assume that the TWIC cards for persons Alpha and Beta have been registered? Response: The Hand Held should be configured for CHUID with biometric identification mode. Registration of TWICs into a PACS is not necessary. Attachment D (TWIC Vendor Demonstration Scenario) has been amended. b.Is it correct to assume that the TWIC cards may first be presented to a contact reader contained on the handheld, the TPKs read and temporarily stored on the handheld, and then the TWIC card would then be presented to the contactless interface as described in the procedures? Response: If a reader is using the contact interface for a transaction, there is no need to begin the transaction as a contact session and then switch “in the middle” to a contactless session; all the information required to perform a biometric match should be retrieved over the contact interface in a single session. [Refer to Table 4.3 on Page 23 of the TWIC Reader Hardware and Card Application Specification] 28. Please clarify the CHUID with Biometrics Verification Using Wrong Cardholder Use Case (Demonstration Scenario 4). a.To meet the May 30, 2008 TSA TWIC specification will you allow the following scenario: the TWIC cards may first be presented to a contact reader contained on the handheld, the TPKs read and temporarily stored on the handheld, the TWIC card would then be presented to the contactless interface as described in the procedures? Response: If a reader is using the contact interface for a transaction, there is no need to begin the transaction as a contact session and then switch “in the middle” to a contactless session; all the information required to perform a biometric match should be retrieved over the contact interface in a single session. [Refer to Table 4.3 on Page 23 of the TWIC Reader Hardware and Card Application Specification] b.We want to comply with Table 4.3 on Page 23 of the May 30, 2008 TSA TWIC specification; "the TPK required to decipher it may be obtained from three possible sources: the magnetic stripe of the card, the contact interface of the TWIC card application, or from the PACS system" Response: The information in Table 4.3 is meant to detail all available methods for obtaining the TWIC Privacy Key. What TPK retrieval methods are supported is dependent on reader configuration. For the USCG’s Hand Held TWIC readers, the TPK may be obtained from the magnetic stripe or the contact interface. The USCG Hand Held TWIC readers will not interface with a PACS. 29. Please clarify the Minimum of One Second of Time Between Card Presentations Use Case (Demonstration Scenario 8). a.Under Procedure Item 4. Restore privileges of Person Alpha in the PACS prior to starting another scenario, this does not fit with the Reference(s). Response: Regarding scenario #6 (on page 8), procedure #4 can be ignored since PACS are irrelevant for the USCG Hand Held TWIC reader. 30. The combined solicitation synopsis and PWS states that the reader must be interoperability with the SID (Seafarer’s card) and references Appendix D (Vendor Demonstration Scenario). As we read the Appendix D of the TWIC reader spec, it refers to AID and ATRs related to CACs and other types of PIV/FIPS 201 credentials. Is USCG requesting interoperability around the 2-D PDF 417 Seafarers card or DOD Common Access Card (CAC) or both? Response: Minimum requirements are TWIC and SID. Other capabilities can be detailed in the RFP response. 31. In attachment B (USCG TWIC Specification), Specification #7D reads: The reader shall also read the Seafarers’ Identity Documents (SID) and conduct a comparison of the individuals biometric to the template stored in the bar code. – THRESHOLD. 7A-C requires the reader to have contact and contactless smart card read capabilities. The ILO card is neither a contact nor contactless smart card. What type of mechanism is expected to read the Seafarer’s card as you cannot use a contact or contactless interface based on the Seafarer’s card technology? Response: Bar Code. 32. Is it USCG intent to require multiple bar code standards to be utilized (TWIC / PIV and ILO)? Response: No, only bar code read for SID. 33. Is there an issue related to liability for a vendor if it reads a card for the USCG based on an ILO treaty, that has not been ratified by the US, governing the use of the Seafarer’s card? Response: No. 34. How does the USCG plan to do a validity check of the status of the mariner based on the SID? Is there a System of Record that stores the status of mariners? Response: The only requirement at this time is to conduct a biometric match for SID. 35. Is there a national database in the US or another country that can be accessed for the purposes of this RFP per ILO 185 Article 4? Response: See the response to question 34. 36. Does the USCG anticipate real time connections to any ILO 185 national databases at the time of the transaction between USCG Handheld and the SID? Response: See the response to question 34. 37. Where can test SIDs be obtained? Response: The USCG will not provide test SIDs. 38. Can you confirm that only the demonstration scenarios in Appendix D will be required and no other product functionality is required in order to be selected? Given the window of 1 hour for demonstrations, there are some requirements in Appendix B (i.e. battery life of 12 hours) that cannot be demonstrated. Response: Yes. All other requirements must be addressed in the written response to the RFP. 39. For the CHUID with biometrics verification scenario, can this be performed alternatively via the contact interface, since you can obtain the TPK and CHUID and perform a successful 1:1 match via the contact interface and will be a faster transaction since you do not need to hold the card to the contactless reader, swipe the mag stripe (to obtain TPK), and then place the finger on the reader? Response: If a reader is using the contact interface for a transaction, there is no need to begin the transaction as a contact session and then switch “in the middle” to a contactless session; all the information required to perform a biometric match should be retrieved over the contact interface in a single session. [Refer to Table 4.3 on Page 23 of the TWIC Reader Hardware and Card Application Specification] 40. For the CHUID with biometrics verification scenario using the wrong cardholder, can this be performed alternatively via the contact interface, since you can obtain the TPK and CHUID and perform a successful 1:1 match via the contact interface and will be a faster transaction since you do not need to hold the card to the contactless reader, swipe the mag stripe (to obtain TPK), and then place the finger on the reader? Response: If a reader is using the contact interface for a transaction, there is no need to begin the transaction as a contact session and then switch “in the middle” to a contactless session; all the information required to perform a biometric match should be retrieved over the contact interface in a single session. [Refer to Table 4.3 on Page 23 of the TWIC Reader Hardware and Card Application Specification] 41. For any of the testing scenarios, if a portable reader does not have contactless capability, can a contact only version be submitted? Conversely, can a supplier submit only a contactless portable reader? Response: No. The threshold requirement is for both a contact and contactless portable reader. 42. Do the readers need to be on the FIPS 201 APL prior to the Aug 1 date? Response: No. 43. In testing scenario #1, the procedure calls for CHUID read and verification within 2 seconds. Can you clarify what you mean by verification of CHUID? Can you clarify how the time measurement will be obtained? Response: Verification of the CHUID within 2 seconds means the reader performs a contactless read of the CHUID (signed or unsigned), performs any internal data validation tasks (for this mode), and subsequently indicates the presence or displays the CHUID based on the processed information. The time will be measured from the read to the final indication. 44. Can you clarify that the use of the TWIC CRL for obtaining status information “Section 6, 4th paragraph “A portable TWIC reader shall be capable of downloading and using the most recent TWIC Hotlist. A portable TWIC reader may support a Certificate Revocation List (CRL) subject to availability of a network connection”. Is an acceptable means for obtaining validity status of the TWIC? Response: The TWIC Certificate Revocation List (CRL) is maintained by the TWIC program along with the Hot List. To use a CRL the reader would need to read the serial number of at least one of the X.509 certificates (e.g. the Card Authentication certificate) held in the PIV card application and check if this serial number appears on the TWIC CRL. The CRL check is presumed to be done using a network connection. Alternatively the FASC-N can be checked to see if it appears on the Hot List. The Hot List is presumed to be loaded on the portable reader on a regular basis and will be used without a network connection. 45. In attachment B, Specification 11C, do want to display the whole CHUID or just the FASC-N. Can you explain what data elements of the CHUID you expect to see on the Handheld reader screen? Is the expectation that the whole data block of the CHUID be displayed on the screen of the reader? If so, what is the value of displaying the whole CHUID to an operator? This number value does not have any human related value that could be of interest to make an access decision. Response: As a back-up, enough information, including the expiration date, should be visible to the operator to allow for a manual check against the TSA published hotlist. 46. In attachment B, Specification 15, do you mean 1 model/version for USCG purposes since these are not for the ports themselves? Response: 1 model/version for the USCG. 47. In attachment B, Specification 15, do you intend for the manufacturer to keep an inventory of the selected baseline device for warranty replacement purposes or new purchases? If so, what is the expected maximum quantity that the USCG expects the manufacturer to have available in that configuration? How does the USCG expect the manufacturer to address production component replacement/hardware upgrades that are required due to component obsolescence? Response: The USCG expects that as a delivery order is placed, a TWIC Hand-Held reader will be delivered by the time specified in the order. 48. In attachment B, Specification 18, does this mean you are requiring the log-in to the device to be via the USCG issued CACs-similar to CAC log-in onto a desktop/laptop PC and use of the CAC per HSPD-12? Response: No. 49. In Attachment B, Specification 8, how is the USCG determining primary versus secondary biometric? Is this the 2nd fingerprint biometric on the TWIC? Response: The biometric template contains, in most cases, two fingerprint minutiae patterns. The quality value of each fingerprint is detailed in the biometric template. 50. In attachment B, all of the requirements related to the portable media are “Objective” except for #26. “The reader shall have a cleanup utility to remove all records and data after uploading to portable media – THRESHOLD”. Is this also supposed to be “Objective” to be consistent with all other portable media requirements in this document? Response: No. 51. In Attachment B #14, this user message requirement states that the reader should display “Valid TWIC” or “Invalid TWIC” as the User Interface message. The DHS TSA response for the TWIC BAA, they clarified the message that should be seen on the Handheld related to “Valid TWIC” and “Invalid TWIC” and that this should be” Respondents should detail what is displayed, if anything, after a check against the Hotlist. The display values are meant to be illustrative and not a requirement”. Does the USCG agree with this approach from TSA or is the requirement in Attachment B supposed to be a requirement or illustrative? Response: When comparing the CHUID of a presented TWIC against the most recently downloaded hotlist the system shall display results of the check and the reason why. (VALID and INVALID are illustrative) - THRESHOLD 52. What elements of the FASC-N do you want displayed or do you just want the whole integer displayed? Response: As a back-up, enough information including the expiration date, should be visible to the operator to allow for a manual check against the TSA published hotlist. 53. Battery life objective – we understand to be 2 to 4 hours, is this correct? Response: The battery shall support 12-hours of continuous operations. - OBJECTIVE 54. Training: can you define the locations for which the training will take place as defined under Price Scenario Worksheet (maximum of 12 training classes) Response: See the response to question 24. 55. Attachment A: 1.3.2. does the 24 hour resolution requirement pertain only to weekdays (workdays), does this pertain also to weekends? Response: 7-days per week 56. Attachment A: 5.1.3. What is the intended process for downloading the TWIC hotlist to the mobile device, e.g. thumb drive, daily PC connection, wireless connection, etc. What is the intended frequency of doing so? Answer: The Hot List is updated daily from TSA and it is presumed a daily download can be accommodated via thumb drive or similar process. 57. Please, clarify\define the purpose of the TWIC BAA Request, versus the recently requested TWIC RFP Solicitation. Answer: These two announcements represent different requirements, as documented in the body of each announcement. Among other differences, the US Coast Guard's RFP is solely related to handheld readers, while the TSA BAA is related to both handheld and fixed readers. Interested parties should read both announcements and their corresponding instructions carefully to ascertain the differences between the announcements. Enclosures: Amended Attachment D (TWIC Vendor Demonstration Scenario) and **Amended Attachment E (TWIC Price Scenario Worksheet). **Please use Attachment E (TWIC Price Scenario Worksheet) as a guide to develop your Price Proposal. Also please note that they must be a Grand Total Price for all 300 readers.
Web Link: FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=a7db267128d6e6231fb9576c7d88252b&tab=core&_cview=1)
Document(s): Amended Attachment D (TWIC Vendor Demonstration Scenario); File Name: Amended Attachment E (TWIC Price Scenario Worksheet) ((Amended) TWIC Price Scenario Worksheet (Attachment E).xls); Link: https://www.fbo.gov//utils/view?id=416d2bcdde0c980d76086374d935c017; Bytes: 22.50 Kb; File Name: TWIC Questions and Responses (TWIC Questions and Responses 16JUL08.doc); Link: https://www.fbo.gov//utils/view?id=0ff23660a31668703b1b6dd84e09be1c; Bytes: 99.00 Kb; File Name: Amended Attachment D (TWIC Vendor Demonstration Scenario) ((Amended) TWIC Vendor Demonstration Scenario (Attachment D).doc); Link: https://www.fbo.gov//utils/view?id=789adb2584ae85b336d58ccc24713081; Bytes: 94.50 Kb; Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
Place of Performance: Address: Places of Performance shall be the Contractor’s and/or Government’s Facilities., United States
Record: SN01615191-W 20080718/080716220459-a7db267128d6e6231fb9576c7d88252b (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

70 -- TWIC HAND-HELD READERS - Amended Attachment E (TWIC Price Scenario Worksheet) - TWIC Questions and Responses - Amended Attachment D (TWIC Vendor Demonstration Scenario)