Loren Data's FBO Daily™

fbodaily.com
Home Today's FBO Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF DECEMBER 17, 2005 FBO #1482
SPECIAL NOTICE

B -- TSA Registered Traveler Program Request for Information

Notice Date
12/15/2005
 
Notice Type
Special Notice
 
NAICS
541990 — All Other Professional, Scientific, and Technical Services
 
Contracting Office
DHS - Border and Transportation Security, Transportation Security Administration, Headquarters TSA, 601 S. 12th Street TSA-25, 10th Floor, Arlington, VA, 22202
 
ZIP Code
22202
 
Solicitation Number
Reference-Number-21-06-206TTC000
 
Response Due
1/20/2006
 
Archive Date
2/4/2006
 
Description
1. General Information Document: Request for Information (RFI) 2. Contracting Office Address Department of Homeland Security, Transportation Security Administration (TSA), 701 South 12th Street, Arlington, VA 22202 3. Background The mission of the Registered Traveler (RT) Program is to expedite screening procedures for qualified individuals at selected U.S. airports. The RT Program will be a voluntary program in which individuals who provide biometric and biographic data, undergo a TSA security threat assessment, pay a user fee, and are deemed eligible by TSA, will be allowed to use designated or dedicated security lines at participating airports and may receive additional screening benefits correlated to the security threat assessment performed. The goal of the RT program is to increase the efficiency of the Transportation Security Officers and security resources. Airline passengers who have successfully completed a security threat assessment by TSA may be expedited through security checkpoint processing and allow security resources to focus on unknown travelers. TSA anticipates the enhancement of overall aviation security and the likelihood of maintaining or improving non-RT security checkpoint wait times. 4. Purpose The TSA Registered Traveler Program (RT) is seeking information to assist in the development of a Business Model to govern the nationwide implementation of the RT program. Specifically, TSA seeks alternative methodologies for implementing each component of the Business Model as well as the technologies or services available to support implementation. TSA desires innovative and creative ideas for the RT Business Model. After reviewing the responses, TSA may incorporate into the final model any or all of the information provided. 5. Critical Functions Listed below are the critical functions inherent to the RT Program and are mandatory elements for a comprehensive business plan. Other than noting the mandatory nature of these critical functions, TSA does not define how these critical functions are met, and what, if any enhancements or desirables are to be included in the Business Model. Enrollment and biometric capture Identity/document validation at enrollment Card issuance and revocation Data transfer and storage throughout the system Interface technology for the smart card and verification system Audit processes and procedures Compensation for participating entities Identification verification at the security checkpoint Membership renewal 6. Program Guidelines Minimally, the completed Business Model for the national RT program implementation will: Utilize a public-private partnership with clear delineation of roles and responsibilities, including revenue allocation; Require interoperability of all participating RT program sites from the onset of operations (interoperability is defined as a valid card issued to any eligible participant and is operational at all authorized RT program sites without regard to where the card was issued); Accommodate all eligible enrollees through the use of technology that incorporates multiple biometrics; Collect a complete set of fingerprint images and two (2) iris images at participant enrollment; Utilize a smart card with the iris and fingerprint biometrics stored on the RT card for the use of identity verification only Include an identity authentication and verification element to link the security threat assessment to the correct individual through the biometric; Sustain the Program solely through user fees; Utilize the Transportation Security Clearinghouse (TSC) to aggregate biometric and biographic data and provide associated customer service; Create an open architecture to allow access to all interested airports/air carriers and qualified vendors from the program?s inception; Facilitate rapid roll-out; and Provide scalable and sustainable operations. TSA will define all security policies and standards; conduct the security threat assessments and adjudications; maintain security screening operations at the checkpoint lane; and oversee performance and compliance. Transportation Security Clearinghouse (TSC) is a central, neutral data management body that will facilitate the flow of information. 7. Submission Instructions As appropriate, submissions may address one or more subject areas and should describe how to define each process identified, i.e., how to define and estimate the applicant volume that drives your business model assumptions (e.g. what level of capital/infrastructure investment required, operational costs and resultant pricing of your services to applicants and/or partners); define fee structure to include flow of funds; provide incentives for stakeholders; encourage participant enrollment; identify the roles of service providers and possible contractual relationships; define the participant enrollment and member verification process, etc. Please note that this request for information is for planning purposes only and does not constitute a solicitation for competitive bids or proposals and is not to be construed as a commitment by the Government. Since this is not an active procurement, please do not include your business qualification statements. Submissions should be limited to a total count of 15 pages per submittal. Send all responses via e-mail to the TSA Contracting Officer and must be received no later than 12:00 noon ET on 20 January 2006. Early submittals are encouraged and will be reviewed upon receipt. Telephone responses will not be accepted. 8. Public Meeting Notice A meeting will be held on December 20, 2005 from 10:30 to 12:30 ET at TSA Headquarters, 601 South 12th Street, Arlington, VA. The meeting is for fact-finding and is provided as a courtesy to all interested parties to discuss the RFI submittal. All available details have been provided in this RFI and on the TSA Web site. TSA will make a reasonable effort to respond to all written questions and comments. Questions and comments submitted after January 06, 2005 may not receive a direct response from TSA; however, all responses will be posted to the Federal Business Opportunities website. If the demand presents itself, TSA may conduct a second industry day after January 03, 2006. The meeting facility is limited to 145 people; therefore, TSA will also provide a conference call bridge for your participation. RSVP your preference to attend the meeting in person or via conference call, by email, to Freda Powell, no later than 12:00 p.m. ET on December 16, 2005. Include with the RSVP the names of the individuals planning to attend this meeting. TSA will confirm your reservation in a return email by COB December 16, 2005. TSA reserves the right to limit number of attendees per entity. Attendees should plan to arrive at the TSA Visitors Center at least 30 minutes prior to the meeting. 9. Point of Contact William Melanson, Contracting Officer, email address: William.F.Melanson@dhs.gov or James Loba, email address: James.Loba@dhs.gov Meeting POC: Freda Powell, Contracting Officer Technical Representative, email address Freda.Powell@dhs.gov, Phone (202) 744-8269 10. Place of Performance Nationwide
 
Record
SN00952605-W 20051217/051215211603 (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  © 1994-2014, Loren Data Corp.