Bid guide
How to bid on Transportation Security Administration’s Open Architecture Initiatives
What the TSA is buying and why it matters
The Transportation Security Administration (TSA) is seeking information from businesses about their capabilities and solutions for "open architecture" in transportation security systems. This initiative aims to develop next-generation open architecture solutions and applications.
The TSA wants to understand industry capabilities and product development to gauge the viability of future open architecture requirements. Your feedback can help the TSA in its planning and development process, and may lead to opportunities for industry to participate in non-funded proof-of-concepts or demonstrations.
Key dates and deadlines
The deadline for written responses to Request for Information (RFI) 70T04024I7573N001 is Friday, June 7, 2024, at 12:00 PM EDT. These responses should be emailed to [email protected] and [email protected].
Comments on the Digital Imaging and Communications in Security (DICOS) Software Development Kit (SDK) and Open Platform Software Library (OPSL) SDK are due by September 30, 2024. Use the attached "OAStakeholderComment FormRev1" and submit to [email protected].
Requests for Open Architecture Sensitive Security Information (SSI) access must be submitted by 2:00 PM EST on February 28, 2025, following instructions in the "Open Architecute Vetting Instructions" document.
Who this opportunity suits
This opportunity is suitable for businesses with expertise in software development, system integration, and security technologies, particularly those familiar with open architecture concepts and transportation security systems. Firms that can provide insights into vendor capabilities, qualifications, approaches, costs, risks, and technical challenges related to connected transportation security systems will find this relevant.
Companies that develop software development kits (SDKs) or related solutions for digital imaging and communications in security are also encouraged to provide feedback.
How to respond
To access the opportunity details and documents, click “View original source” on the portal. If the first click takes you to the portal’s homepage, click it again to go directly to the bid. You may need a free account to view some documents.
For the RFI, email your written responses by the deadline to the specified TSA contacts. For SDK comments, complete the provided form and email it to [email protected]. For SSI access, follow the instructions in the "Open Architecute Vetting Instructions" document and submit by the stated deadline.
Tips for preparing a competitive response
When responding to an RFI, focus on clearly articulating your firm's capabilities and experience relevant to open architecture in security systems. Provide specific examples of past projects or solutions that demonstrate your expertise.
For comments on SDKs, be precise and constructive. Highlight areas where the current SDKs excel and suggest specific features or capabilities that would enhance future versions. Your feedback should show a deep understanding of the technology and its application in transportation security.
Ensure all submissions are made by the stated deadlines and to the correct email addresses. Double-check that your email submission is received by the government to avoid any issues.
See the live bid — deadline, agency details, and how to respond
Dates and requirements can change via addenda; always verify on the bid page and at the original source before responding.
View this bid on BiddingSimpleThis guide was prepared by BiddingSimple from the solicitation’s public posting. It is not official guidance from Transportation Security Administration; the original posting controls.
