Components

3 Twig Components
9 Render Count
4 ms Render Time
256.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState
"App\Twig\Components\ProductState"
components/ProductState.html.twig
4 0.97ms
ProductMostRecent
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig
4 2.81ms
ProductType
"App\Twig\Components\ProductType"
components/ProductType.html.twig
1 0.23ms

Render calls

ProductState App\Twig\Components\ProductState 256.0 MiB 0.36 ms
Input props
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes
[
  "showFullLabel" => "true"
]
Component
App\Twig\Components\ProductState {#93101
  +product: App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 256.0 MiB 0.23 ms
Input props
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductType {#93281
  +product: App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 256.0 MiB 0.72 ms
Input props
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductMostRecent {#93356
  +product: App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 256.0 MiB 0.22 ms
Input props
[
  "product" => App\Entity\Product\Product {#100353
    #id: 10864
    #code: "IEEE00005202"
    #attributes: Doctrine\ORM\PersistentCollection {#100334 …}
    #variants: Doctrine\ORM\PersistentCollection {#100331 …}
    #options: Doctrine\ORM\PersistentCollection {#100327 …}
    #associations: Doctrine\ORM\PersistentCollection {#100329 …}
    #createdAt: DateTime @1751039331 {#100360
      date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100333
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100344 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100372
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100353}
        #id: 38465
        #name: "IEEE N42.45:2011"
        #slug: "ieee-n42-45-2011-ieee00005202-242516"
        #description: """
           - Active.<br />\n
          Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          \t\t\t\t<br />\n
          This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100342 …}
    #channels: Doctrine\ORM\PersistentCollection {#100336 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100340 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100338 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100351 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100320
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1656367200 {#100359
      date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1306101600 {#100358
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1306101600 {#100352
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 58
    -documents: Doctrine\ORM\PersistentCollection {#100349 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100347 …}
  }
  "showFullLabel" => "true"
]
Attributes
[
  "showFullLabel" => "true"
]
Component
App\Twig\Components\ProductState {#100411
  +product: App\Entity\Product\Product {#100353
    #id: 10864
    #code: "IEEE00005202"
    #attributes: Doctrine\ORM\PersistentCollection {#100334 …}
    #variants: Doctrine\ORM\PersistentCollection {#100331 …}
    #options: Doctrine\ORM\PersistentCollection {#100327 …}
    #associations: Doctrine\ORM\PersistentCollection {#100329 …}
    #createdAt: DateTime @1751039331 {#100360
      date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100333
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100344 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100372
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100353}
        #id: 38465
        #name: "IEEE N42.45:2011"
        #slug: "ieee-n42-45-2011-ieee00005202-242516"
        #description: """
           - Active.<br />\n
          Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          \t\t\t\t<br />\n
          This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100342 …}
    #channels: Doctrine\ORM\PersistentCollection {#100336 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100340 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100338 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100351 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100320
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1656367200 {#100359
      date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1306101600 {#100358
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1306101600 {#100352
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 58
    -documents: Doctrine\ORM\PersistentCollection {#100349 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100347 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 256.0 MiB 0.74 ms
Input props
[
  "product" => App\Entity\Product\Product {#100353
    #id: 10864
    #code: "IEEE00005202"
    #attributes: Doctrine\ORM\PersistentCollection {#100334 …}
    #variants: Doctrine\ORM\PersistentCollection {#100331 …}
    #options: Doctrine\ORM\PersistentCollection {#100327 …}
    #associations: Doctrine\ORM\PersistentCollection {#100329 …}
    #createdAt: DateTime @1751039331 {#100360
      date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100333
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100344 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100372
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100353}
        #id: 38465
        #name: "IEEE N42.45:2011"
        #slug: "ieee-n42-45-2011-ieee00005202-242516"
        #description: """
           - Active.<br />\n
          Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          \t\t\t\t<br />\n
          This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100342 …}
    #channels: Doctrine\ORM\PersistentCollection {#100336 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100340 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100338 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100351 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100320
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1656367200 {#100359
      date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1306101600 {#100358
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1306101600 {#100352
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 58
    -documents: Doctrine\ORM\PersistentCollection {#100349 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100347 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductMostRecent {#100478
  +product: App\Entity\Product\Product {#100353
    #id: 10864
    #code: "IEEE00005202"
    #attributes: Doctrine\ORM\PersistentCollection {#100334 …}
    #variants: Doctrine\ORM\PersistentCollection {#100331 …}
    #options: Doctrine\ORM\PersistentCollection {#100327 …}
    #associations: Doctrine\ORM\PersistentCollection {#100329 …}
    #createdAt: DateTime @1751039331 {#100360
      date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100333
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100344 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100372
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100353}
        #id: 38465
        #name: "IEEE N42.45:2011"
        #slug: "ieee-n42-45-2011-ieee00005202-242516"
        #description: """
           - Active.<br />\n
          Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          \t\t\t\t<br />\n
          This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100342 …}
    #channels: Doctrine\ORM\PersistentCollection {#100336 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100340 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100338 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100351 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100320
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1656367200 {#100359
      date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1306101600 {#100358
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1306101600 {#100352
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 58
    -documents: Doctrine\ORM\PersistentCollection {#100349 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100347 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 256.0 MiB 0.21 ms
Input props
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes
[
  "showFullLabel" => "true"
]
Component
App\Twig\Components\ProductState {#107069
  +product: App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 256.0 MiB 0.72 ms
Input props
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductMostRecent {#107111
  +product: App\Entity\Product\Product {#7310
    #id: 12898
    #code: "IEEE00010914"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040731 {#7274
      date: 2025-06-27 18:12:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 46601
        #name: "IEEE/ANSI N42.45:2021"
        #slug: "ieee-ansi-n42-45-2021-ieee00010914-244556"
        #description: """
          Revision Standard - Active.<br />\n
          Standard test methods for the evaluation of image quality of computed tomography security-screening systems are established in this document. The quality of data for automated analysis is the primary concern. The system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body, is not addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This document establishes standard test methods and test objects for measuring the imaging performance of x-ray computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This document does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, nor is it intended for vendor-to-vendor comparisons of threat-detection performance. This standard does not purport to address radiation safety and health practices associated with CT security-screening systems; users are advised to determine the applicability of regulatory limitations prior to use. Four annexes are included. Annex A is a bibliography (informative). Annex B (normative) provides mechanical drawings of the imaging test objects that compose the test article. A sample test report form is given in Annex C (informative). Finally, Annex D (informative) offers statistical guidance on multiple scans, summary statistics, and comparison of results.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT) Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1677106800 {#7292
      date: 2023-02-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1656540000 {#7318
      date: 2022-06-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 256.0 MiB 0.18 ms
Input props
[
  "product" => App\Entity\Product\Product {#100353
    #id: 10864
    #code: "IEEE00005202"
    #attributes: Doctrine\ORM\PersistentCollection {#100334 …}
    #variants: Doctrine\ORM\PersistentCollection {#100331 …}
    #options: Doctrine\ORM\PersistentCollection {#100327 …}
    #associations: Doctrine\ORM\PersistentCollection {#100329 …}
    #createdAt: DateTime @1751039331 {#100360
      date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100333
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100344 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100372
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100353}
        #id: 38465
        #name: "IEEE N42.45:2011"
        #slug: "ieee-n42-45-2011-ieee00005202-242516"
        #description: """
           - Active.<br />\n
          Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          \t\t\t\t<br />\n
          This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100342 …}
    #channels: Doctrine\ORM\PersistentCollection {#100336 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100340 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100338 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100351 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100320
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1656367200 {#100359
      date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1306101600 {#100358
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1306101600 {#100352
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 58
    -documents: Doctrine\ORM\PersistentCollection {#100349 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100347 …}
  }
  "showFullLabel" => "true"
]
Attributes
[
  "showFullLabel" => "true"
]
Component
App\Twig\Components\ProductState {#107176
  +product: App\Entity\Product\Product {#100353
    #id: 10864
    #code: "IEEE00005202"
    #attributes: Doctrine\ORM\PersistentCollection {#100334 …}
    #variants: Doctrine\ORM\PersistentCollection {#100331 …}
    #options: Doctrine\ORM\PersistentCollection {#100327 …}
    #associations: Doctrine\ORM\PersistentCollection {#100329 …}
    #createdAt: DateTime @1751039331 {#100360
      date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100333
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100344 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100372
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100353}
        #id: 38465
        #name: "IEEE N42.45:2011"
        #slug: "ieee-n42-45-2011-ieee00005202-242516"
        #description: """
           - Active.<br />\n
          Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          \t\t\t\t<br />\n
          This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100342 …}
    #channels: Doctrine\ORM\PersistentCollection {#100336 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100340 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100338 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100351 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100320
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1656367200 {#100359
      date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1306101600 {#100358
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1306101600 {#100352
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 58
    -documents: Doctrine\ORM\PersistentCollection {#100349 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100347 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 256.0 MiB 0.63 ms
Input props
[
  "product" => App\Entity\Product\Product {#100353
    #id: 10864
    #code: "IEEE00005202"
    #attributes: Doctrine\ORM\PersistentCollection {#100334 …}
    #variants: Doctrine\ORM\PersistentCollection {#100331 …}
    #options: Doctrine\ORM\PersistentCollection {#100327 …}
    #associations: Doctrine\ORM\PersistentCollection {#100329 …}
    #createdAt: DateTime @1751039331 {#100360
      date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100333
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100344 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100372
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100353}
        #id: 38465
        #name: "IEEE N42.45:2011"
        #slug: "ieee-n42-45-2011-ieee00005202-242516"
        #description: """
           - Active.<br />\n
          Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          \t\t\t\t<br />\n
          This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100342 …}
    #channels: Doctrine\ORM\PersistentCollection {#100336 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100340 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100338 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100351 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100320
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1656367200 {#100359
      date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1306101600 {#100358
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1306101600 {#100352
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 58
    -documents: Doctrine\ORM\PersistentCollection {#100349 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100347 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductMostRecent {#107203
  +product: App\Entity\Product\Product {#100353
    #id: 10864
    #code: "IEEE00005202"
    #attributes: Doctrine\ORM\PersistentCollection {#100334 …}
    #variants: Doctrine\ORM\PersistentCollection {#100331 …}
    #options: Doctrine\ORM\PersistentCollection {#100327 …}
    #associations: Doctrine\ORM\PersistentCollection {#100329 …}
    #createdAt: DateTime @1751039331 {#100360
      date: 2025-06-27 17:48:51.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#100333
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100344 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100372
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100353}
        #id: 38465
        #name: "IEEE N42.45:2011"
        #slug: "ieee-n42-45-2011-ieee00005202-242516"
        #description: """
           - Active.<br />\n
          Test methods and test articles for the evaluation of the image quality of CT security screening systems are provided. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use its image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          \t\t\t\t<br />\n
          This standard provides test methods for the evaluation of image quality of computed tomography (CT) security-screening systems. The quality of data for automated analysis is the primary concern. This standard does not address the system’s ability to use this image data to automatically detect explosives or other threat materials, which is typically verified by an appropriate regulatory body.<br />\n
          Security screening systems are generally used to scan parcels, including luggage, for the presence of illicit items such as explosives, drugs, or other contraband. Many of the screening systems currently used, particularly in transportation security applications, are based on CT imaging technology. Generally, as the parcel is transported through the system, the system collects a CT image of the parcel. These data are then subjected to automated analysis to determine whether a threat may be present or the parcel is considered clear. If the automated analysis determines a threat may be present, the image is often presented to a system operator who can override the automated decision, clearing the parcel, or referring it for further processing such as opening it and manually searching for threats. Historically, government regulators have established evaluation procedures to determine whether a system’s automated detection performance is adequate for use in applications within their borders. Typically, a vendor submits a copy of their product, including their software to the regulator’s facility. The regulator runs a wide variety of parcels with threats inside through the system as well as parcels without threats that represent the typical stream of commerce. Detection and false alarm rates are determined and compared against performance criteria. If the criteria are met, the system is approved for use. This testing assures that the system is capable of meeting the required criteria, but how does one assure that all copies of the system meet the criteria? Normal manufacturing variability, quality control issues, or aging of the equipment may degrade performance versus what was observed on the article tested by the regulator. Replicating the original test on each machine in question is impractical. Transporting the regulator’s threat set to a factory site or to locations where the machines are in use, presents significant security and in some cases safety concerns. This standard seeks to address this issue by specifying a suite of test methods that can be carried out on site without need for hazardous materials. The performance testing carried out by the regulators essentially evaluates the combination of the system’s ability to produce an image of the parcel along with its automatic analysis of that image data to reach a decision of threat or clear. The second part of this sequence, the analysis, is implemented through software. It should be noted that the regulators generally require that this software be designed so as to NOT evolve through use. The software used at all locations in the field must perform the same as the software did at the time of evaluation by the regulator. Configuration management of such software is a well known and straightforward art. Therefore, the real opportunity for performance variation comes from the imaging system that provides the data to the analysis software. If one can quantitatively validate that the quality of the image produced by the system in question is statistically equivalent to the image produced by the article evaluated by the regulator, one can be highly confident that the performance of the system in question is the same as what was approved by the regulator. Purchasers of CT systems for security screening applications are generally not CT experts. Inconsistencies in methods for measuring seemingly standard image quality values (resolution, signal-to-noise, etc.) can confuse the potential user of such CT systems. Other standards exist for testing aspects of CT image quality, particularly in the medical field. This standard specifies a set of methods to apply in assessing CT image quality geared towards security screening. An application of this standard would be in the factory acceptance testing of equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard for Evaluating the Image Quality of X-ray Computed Tomography (CT)Security-Screening Systems"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#100342 …}
    #channels: Doctrine\ORM\PersistentCollection {#100336 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100340 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100338 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100351 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100320
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1656367200 {#100359
      date: 2022-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1306101600 {#100358
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1306101600 {#100352
      date: 2011-05-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "N42.45"
    -bookCollection: ""
    -pageCount: 58
    -documents: Doctrine\ORM\PersistentCollection {#100349 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100347 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}