Planning Guidelines and Design Standards for Checked Baggage Inspection Systems - Version 6 - Supporting and requirement definitions

Sep 18, 2026

Uploaded by Levi

Planning Guidelines and Design Standards for Checked Baggage Inspection Systems (PGDS) establishes TSA requirements and documented best practices for implementing a checked baggage inspection system, from early design through commissioning. It defines key terms—Requirement, Best Practice/Guidance, and Support—distinguishing mandatory “shall” language from recommended guidance and non-mandatory informational statements. It also outlines applicability, exceptions, and governance for upgrades, testing, resubmission timing, major redesigns, and industry collaboration.

LanguageEnglish

CategoryResearch & Report

FormatPDF

Pages576

Reading Time24 h 12 min

AccessFree to download

Purpose and scope

Definitions and identification of requirements, best practices and support statements

Version history

Exceptions

PGDS applicability

Delayed opening of CBIS

Major redesigns

Industry collaboration and comments

Planning Guidelines and Design Standards for Checked Baggage Inspection Systems Version 6.0 September 29, 2017 DISCLAIMER This document is being distributed under the sponsorship of the Transportation Security Administration (TSA) of the U. S. Department of Homeland Security (DHS) in the interest of information exchange. The U. S. Government assumes no liability for the contents or use of this document. The purpose of the document is to present TSA’s requirements and documented best practices for implementing a high performance and cost-effective checked baggage inspection system (CBIS) . This document captures TSA’s requirements for a CBIS project from the beginning stages of design through commissioning of the system. Best practices are meant to highlight practices that have proven successful during implementation and which TSA recommends for the Project Sponsor’s consideration during the design and construction of a CBIS. DEFINITIONSAND IDENTIFICATION OF REQUIREMENTS, BEST PRACTICES AND SUPPORT INFORMATION When used in the Planning Guidelines and Design Standards (PGDS) for Checked Baggage Inspection Systems , the terms Requirement, Best Practice/Guidance, and Support statements shall be defined as follows: Requirement – a statement of required, mandatory practice. All requirement statements are presented in underlined text. The verb “shall” is used. The verbs “should” and “will” are not used in requirement statements. Best Practice/Guidance – a statement of recommended, but not mandatory , practice. These statements are generated from lessons learned. These statements are geared to inform the reader of known effective practices that have proven successful during implementation. Best practice/guidance statements can be identified within the document by the use of the verb “should”. The verbs “shall” and “will” are not used in best practice/guidance statements. Support–an informational statement that does not convey any degree of mandate, recommendation, authorization, prohibition, or enforceable condition. The verbs “shall” and “should” are not used in Support statements. The verb “will” can sometimes be used in support statements when referencing things that are the government’s responsibility. VERSION HISTORY | Version | Date | Modifications | | --- | --- | --- | | 1.0 | October 10, 2007 | First published version | | 2.0 | January 31, 2009 | Update based on recommended follow-on studies and comments on Version 1.0 | | 3.0 | November 27, 2009 | Update based on recommended follow-on studies and comments on Version 2.0 | | 4.0 | July 15, 2011 | Update based on recommended follow-on studies and comments on Version 3.0 | | 4.1 | September 15, 2011 | Update based on recommended follow-on studies and comments on Version 4.0 | | 4.2 | May 2, 2014 | Update based on recommended follow-on studies and comments on Version 4.1 | | 5.0 | July 9 , 2015 | Update based on need for clear differentiation betw een requirements and best practices, follow-on studies and comments on Version 4.2 | | 6.0 | September 29, 2017 | Update based on recommended follow-on studies and comments on Version 5.0 | EXCEPTIONS PGDS Applicability Designs for new checked baggage inspection systems shall comply with the requirements set forth in this version of the PGDS . However, any project sponsor that has received formal confirmation from TSA of the receipt of the complete 30% Detailed Design Package for a CBIS project prior to the publication date of this version of the PGDS shall continue to be governed by the PGDS version in effect at the time of such confirmation. Furthermore, projects that have passed the 30% Detailed Design phase—including those systems currently under construction or in operation—with TSA approval shall be held to the design standards specified by that approval (either under the previous PGDS versions or prior standards in place before the publication of Version 1.0 of the PGDS) . For Operational Analysis

FAQs

What is the purpose of the PGDS for checked baggage inspection systems?

To present TSA requirements and documented best practices for implementing a high performance, cost-effective checked baggage inspection system from design through commissioning.

How does the document distinguish a Requirement from Best Practice/Guidance and Support?

Requirements use mandatory language with “shall.” Best Practice/Guidance uses “should” and is recommended but not mandatory. Support statements provide information without mandate or enforceable conditions, with “shall” and “should” not used.

How does the PGDS handle upgrades, testing, and delayed opening scenarios?

TSA may evaluate a CBIS against the most current PGDS version. Testing follows Appendix D of the latest PGDS in effect at the time of testing, and delayed opening can require resubmission of the 30% Detailed Design Package under the latest PGDS if deadlines are not met.

Sep 18, 2026

Uploaded by Levi

Planning Guidelines and Design Standards for Checked Baggage Inspection Systems - Version 6 - Supporting and requirement definitions_Page 1

Open in WPS to view all 576 pages