Planning Guidelines and Design Standards (PGDS) Version 9.0 for Checked Baggage Inspection Systems
Key Dates
Due Date
-
Posted Date
-
Agency & Value
Agency
WORKFORCE & ENTERPRISE OPERATIONS
Contract Value
Not provided
Codes & Classification
Solicitation Number
TSA25-04-03026
NAICS
488190 - Other Support Activities for Air Transportation
Classification Code
C1BE
Additional Details
The Transportation Security Administration (TSA), under the Department of Homeland Security, has issued a Special Notice (Procurement Identifier: TSA25-04-03026) regarding the release of the "Planning Guidelines and Design Standards for Checked Baggage Inspection Systems Version 9.0" (PGDS v9.0). This document supersedes the previous Version 8.0 and is intended to provide comprehensive requirements and best practices for the design, planning, and implementation of efficient and cost-effective checked baggage screening systems at airports.
The PGDS v9.0 serves as a critical resource for designers, planners, architects, and other stakeholders involved in the development and modernization of in-line checked baggage inspection systems. The guidelines are structured to ensure that all new and upgraded systems meet TSA’s operational, security, and cost-effectiveness objectives. The document is provided as a single, consolidated file containing both the main body and appendices, streamlining access to all relevant standards and technical details.
In addition to the updated PGDS, this notice includes an industry comment form, inviting stakeholders to submit feedback or propose changes for future versions of the guidelines. The comment period is open until March 31, 2027, after which TSA will review and consider all submissions for potential inclusion in subsequent updates. This collaborative approach underscores TSA’s commitment to continuous improvement and industry engagement.
The amendment also introduces the "TSA Electronic Baggage Screening Program Funding of Checked Baggage Inspection System Project Costs Version 8.0" (CBIS Funding Policy Memo v8.0), which replaces Version 7.0. This policy memo outlines the eligibility criteria for TSA funding, details the application and project delivery processes under the Other Transaction Agreement framework, and specifies which costs are allowable, allocable, reasonable, or unallowable for in-line CBIS projects. It further clarifies funding responsibilities for various types of stand-alone Explosive Detection System projects, providing essential guidance for entities seeking federal support for baggage screening infrastructure.
The notice is classified under NAICS Code 488190 (Other Support Activities for Air Transportation) and Product Service Code C1BE, indicating its relevance to firms specializing in airport support services and construction-related activities. The contracting entity is the Workforce & Enterprise Operations office within TSA, and the primary point of contact for this notice is Jason Richards ([email protected]).
This Special Notice is not a solicitation for goods or services but rather an announcement of updated standards and funding policies that will govern future TSA-supported checked baggage inspection system projects. Contractors and industry stakeholders are encouraged to review the attached documents to ensure alignment with the latest TSA requirements and to participate in the comment process to help shape future iterations of the guidelines.
The notice remains active, with all relevant documents and attachments available via the official SAM.gov posting (Opportunity ID: c5a3f81d557c4e608cf33a93bee8444e). Interested parties should refer to the notice URL for access to the full suite of materials and for ongoing updates related to the PGDS and CBIS funding policies.
In summary, this notice provides essential updates to the standards and funding policies governing checked baggage inspection systems, with a focus on enhancing system efficiency, security, and cost-effectiveness. It offers a clear framework for project eligibility and funding, and invites industry input to ensure the guidelines remain responsive to evolving operational needs.
Documents18