GET https://dev.normadoc.fr/_partial/taxons/by-channel-menu-taxon/?template=%40SyliusShop%2FTaxon%2F_horizontalMenu.html.twig

Response
200 OK
IP
216.73.216.131
Profiled on
Token
c848d3

Components

4 Twig Components
46 Render Count
125 ms Render Time
258.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		15 120.66ms
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		15 3.71ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		15 12.25ms
PageBanner 
"App\Twig\Components\PageBanner"
components/PageBanner.html.twig 		1 4.38ms

Render calls

PageBanner App\Twig\Components\PageBanner 258.0 MiB 4.38 ms
Input props 
[
  "paddingClasses" => "p-2 px-lg-5 py-lg-0"
  "searchPlaceholder" => "sylius.ui.search"
  "showSearch" => "true"
  "searchValue" => "ASME BPVC.VIII.1-2025"
  "title" => "Search results"
]
Attributes 
[]
Component 
App\Twig\Components\PageBanner {#94736
  +supTitle: null
  +title: "Search results"
  +subTitle: null
  +backUrl: null
  +backLabel: null
  +customClasses: null
  +backgroundType: null
  +centered: true
  +showSearch: true
  +searchPlaceholder: "sylius.ui.search"
  +searchValue: "ASME BPVC.VIII.1-2025"
  +paddingClasses: "p-2 px-lg-5 py-lg-0"
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 13.75 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95509
    #id: 12614
    #code: "IEEE00010301"
    #attributes: Doctrine\ORM\PersistentCollection {#95569 …}
    #variants: Doctrine\ORM\PersistentCollection {#95567 …}
    #options: Doctrine\ORM\PersistentCollection {#95563 …}
    #associations: Doctrine\ORM\PersistentCollection {#95565 …}
    #createdAt: DateTime @1751040548 {#95512
      date: 2025-06-27 18:09:08.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95508
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95579 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96104
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95509}
        #id: 45465
        #name: "IEEE 3803:2024"
        #slug: "ieee-3803-2024-ieee00010301-244269"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard governs the use, management, and privacy of customer data from household appliances during data assetization.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the requirements for use and management of customer data in the process of data assetization and commercialization. It specifies terms and definitions, data classification schema, data collection, storage, and privacy requirements, and data authorization and exchange protocol requirements applicable to the process of data assetization and commercialization. The standard is applicable to scenarios that generate customer data via household and similar appliances.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for Household Appliance Customer Data Assetization and Commercialization Requirements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95577 …}
    #channels: Doctrine\ORM\PersistentCollection {#95571 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95575 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95573 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95585 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1727042400 {#95519
      date: 2024-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1725919200 {#95517
      date: 2024-09-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3803"
    -bookCollection: ""
    -pageCount: 33
    -documents: Doctrine\ORM\PersistentCollection {#95583 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95581 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#95984
  +product: App\Entity\Product\Product {#95509
    #id: 12614
    #code: "IEEE00010301"
    #attributes: Doctrine\ORM\PersistentCollection {#95569 …}
    #variants: Doctrine\ORM\PersistentCollection {#95567 …}
    #options: Doctrine\ORM\PersistentCollection {#95563 …}
    #associations: Doctrine\ORM\PersistentCollection {#95565 …}
    #createdAt: DateTime @1751040548 {#95512
      date: 2025-06-27 18:09:08.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95508
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95579 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96104
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95509}
        #id: 45465
        #name: "IEEE 3803:2024"
        #slug: "ieee-3803-2024-ieee00010301-244269"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard governs the use, management, and privacy of customer data from household appliances during data assetization.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the requirements for use and management of customer data in the process of data assetization and commercialization. It specifies terms and definitions, data classification schema, data collection, storage, and privacy requirements, and data authorization and exchange protocol requirements applicable to the process of data assetization and commercialization. The standard is applicable to scenarios that generate customer data via household and similar appliances.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for Household Appliance Customer Data Assetization and Commercialization Requirements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95577 …}
    #channels: Doctrine\ORM\PersistentCollection {#95571 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95575 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95573 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95585 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1727042400 {#95519
      date: 2024-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1725919200 {#95517
      date: 2024-09-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3803"
    -bookCollection: ""
    -pageCount: 33
    -documents: Doctrine\ORM\PersistentCollection {#95583 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95581 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.33 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95509
    #id: 12614
    #code: "IEEE00010301"
    #attributes: Doctrine\ORM\PersistentCollection {#95569 …}
    #variants: Doctrine\ORM\PersistentCollection {#95567 …}
    #options: Doctrine\ORM\PersistentCollection {#95563 …}
    #associations: Doctrine\ORM\PersistentCollection {#95565 …}
    #createdAt: DateTime @1751040548 {#95512
      date: 2025-06-27 18:09:08.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95508
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95579 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96104
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95509}
        #id: 45465
        #name: "IEEE 3803:2024"
        #slug: "ieee-3803-2024-ieee00010301-244269"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard governs the use, management, and privacy of customer data from household appliances during data assetization.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the requirements for use and management of customer data in the process of data assetization and commercialization. It specifies terms and definitions, data classification schema, data collection, storage, and privacy requirements, and data authorization and exchange protocol requirements applicable to the process of data assetization and commercialization. The standard is applicable to scenarios that generate customer data via household and similar appliances.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for Household Appliance Customer Data Assetization and Commercialization Requirements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95577 …}
    #channels: Doctrine\ORM\PersistentCollection {#95571 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95575 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95573 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95585 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1727042400 {#95519
      date: 2024-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1725919200 {#95517
      date: 2024-09-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3803"
    -bookCollection: ""
    -pageCount: 33
    -documents: Doctrine\ORM\PersistentCollection {#95583 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95581 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#96111
  +product: App\Entity\Product\Product {#95509
    #id: 12614
    #code: "IEEE00010301"
    #attributes: Doctrine\ORM\PersistentCollection {#95569 …}
    #variants: Doctrine\ORM\PersistentCollection {#95567 …}
    #options: Doctrine\ORM\PersistentCollection {#95563 …}
    #associations: Doctrine\ORM\PersistentCollection {#95565 …}
    #createdAt: DateTime @1751040548 {#95512
      date: 2025-06-27 18:09:08.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95508
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95579 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96104
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95509}
        #id: 45465
        #name: "IEEE 3803:2024"
        #slug: "ieee-3803-2024-ieee00010301-244269"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard governs the use, management, and privacy of customer data from household appliances during data assetization.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the requirements for use and management of customer data in the process of data assetization and commercialization. It specifies terms and definitions, data classification schema, data collection, storage, and privacy requirements, and data authorization and exchange protocol requirements applicable to the process of data assetization and commercialization. The standard is applicable to scenarios that generate customer data via household and similar appliances.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for Household Appliance Customer Data Assetization and Commercialization Requirements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95577 …}
    #channels: Doctrine\ORM\PersistentCollection {#95571 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95575 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95573 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95585 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1727042400 {#95519
      date: 2024-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1725919200 {#95517
      date: 2024-09-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3803"
    -bookCollection: ""
    -pageCount: 33
    -documents: Doctrine\ORM\PersistentCollection {#95583 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95581 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 1.00 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95509
    #id: 12614
    #code: "IEEE00010301"
    #attributes: Doctrine\ORM\PersistentCollection {#95569 …}
    #variants: Doctrine\ORM\PersistentCollection {#95567 …}
    #options: Doctrine\ORM\PersistentCollection {#95563 …}
    #associations: Doctrine\ORM\PersistentCollection {#95565 …}
    #createdAt: DateTime @1751040548 {#95512
      date: 2025-06-27 18:09:08.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95508
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95579 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96104
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95509}
        #id: 45465
        #name: "IEEE 3803:2024"
        #slug: "ieee-3803-2024-ieee00010301-244269"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard governs the use, management, and privacy of customer data from household appliances during data assetization.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the requirements for use and management of customer data in the process of data assetization and commercialization. It specifies terms and definitions, data classification schema, data collection, storage, and privacy requirements, and data authorization and exchange protocol requirements applicable to the process of data assetization and commercialization. The standard is applicable to scenarios that generate customer data via household and similar appliances.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for Household Appliance Customer Data Assetization and Commercialization Requirements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95577 …}
    #channels: Doctrine\ORM\PersistentCollection {#95571 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95575 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95573 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95585 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1727042400 {#95519
      date: 2024-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1725919200 {#95517
      date: 2024-09-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3803"
    -bookCollection: ""
    -pageCount: 33
    -documents: Doctrine\ORM\PersistentCollection {#95583 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95581 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#96205
  +product: App\Entity\Product\Product {#95509
    #id: 12614
    #code: "IEEE00010301"
    #attributes: Doctrine\ORM\PersistentCollection {#95569 …}
    #variants: Doctrine\ORM\PersistentCollection {#95567 …}
    #options: Doctrine\ORM\PersistentCollection {#95563 …}
    #associations: Doctrine\ORM\PersistentCollection {#95565 …}
    #createdAt: DateTime @1751040548 {#95512
      date: 2025-06-27 18:09:08.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95508
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95579 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96104
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95509}
        #id: 45465
        #name: "IEEE 3803:2024"
        #slug: "ieee-3803-2024-ieee00010301-244269"
        #description: """
          New IEEE Standard - Active - Draft.<br />\n
          This standard governs the use, management, and privacy of customer data from household appliances during data assetization.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the requirements for use and management of customer data in the process of data assetization and commercialization. It specifies terms and definitions, data classification schema, data collection, storage, and privacy requirements, and data authorization and exchange protocol requirements applicable to the process of data assetization and commercialization. The standard is applicable to scenarios that generate customer data via household and similar appliances.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Draft Standard for Household Appliance Customer Data Assetization and Commercialization Requirements"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95577 …}
    #channels: Doctrine\ORM\PersistentCollection {#95571 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95575 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95573 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95585 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95516
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1727042400 {#95519
      date: 2024-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1725919200 {#95517
      date: 2024-09-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3803"
    -bookCollection: ""
    -pageCount: 33
    -documents: Doctrine\ORM\PersistentCollection {#95583 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95581 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 7.76 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95556
    #id: 12615
    #code: "IEEE00010302"
    #attributes: Doctrine\ORM\PersistentCollection {#95550 …}
    #variants: Doctrine\ORM\PersistentCollection {#95552 …}
    #options: Doctrine\ORM\PersistentCollection {#95587 …}
    #associations: Doctrine\ORM\PersistentCollection {#95554 …}
    #createdAt: DateTime @1751040549 {#95561
      date: 2025-06-27 18:09:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95560
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95525 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96436
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95556}
        #id: 45469
        #name: "IEEE 3806:2023"
        #slug: "ieee-3806-2023-ieee00010302-244270"
        #description: """
          New IEEE Standard - Active.<br />\n
          Liver and gallbladder diseases affect more than one billion people around the world, but there is still a lack of successful experience and models in terms of data standardization, integration, and sharing. The goal of this document is to solve the above problems through blockchain-based data circulation standards. This standard mainly describes the format of the data circulation and the application process of hepatobiliary diseases, which standardize the data collection, processing, and exchange process of hepatobiliary disease data in the medical information system, aiming to bring a new data credible circulation innovation model for medical education, data sharing applications, and medical artificial intelligence product research and development of hepatobiliary disease big data.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the blockchain-based system architecture, interfaces, protocols, testing, and verification for the extraction and exchange of hepatobiliary disease data across multiple organizations and stakeholders.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Blockchain-Based Hepatobiliary Disease Data Extraction and Exchange"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95536 …}
    #channels: Doctrine\ORM\PersistentCollection {#95548 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95544 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95534 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95559
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708297200 {#95558
      date: 2024-02-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1706223600 {#95557
      date: 2024-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3806"
    -bookCollection: ""
    -pageCount: 59
    -documents: Doctrine\ORM\PersistentCollection {#95531 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95527 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#96414
  +product: App\Entity\Product\Product {#95556
    #id: 12615
    #code: "IEEE00010302"
    #attributes: Doctrine\ORM\PersistentCollection {#95550 …}
    #variants: Doctrine\ORM\PersistentCollection {#95552 …}
    #options: Doctrine\ORM\PersistentCollection {#95587 …}
    #associations: Doctrine\ORM\PersistentCollection {#95554 …}
    #createdAt: DateTime @1751040549 {#95561
      date: 2025-06-27 18:09:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95560
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95525 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96436
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95556}
        #id: 45469
        #name: "IEEE 3806:2023"
        #slug: "ieee-3806-2023-ieee00010302-244270"
        #description: """
          New IEEE Standard - Active.<br />\n
          Liver and gallbladder diseases affect more than one billion people around the world, but there is still a lack of successful experience and models in terms of data standardization, integration, and sharing. The goal of this document is to solve the above problems through blockchain-based data circulation standards. This standard mainly describes the format of the data circulation and the application process of hepatobiliary diseases, which standardize the data collection, processing, and exchange process of hepatobiliary disease data in the medical information system, aiming to bring a new data credible circulation innovation model for medical education, data sharing applications, and medical artificial intelligence product research and development of hepatobiliary disease big data.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the blockchain-based system architecture, interfaces, protocols, testing, and verification for the extraction and exchange of hepatobiliary disease data across multiple organizations and stakeholders.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Blockchain-Based Hepatobiliary Disease Data Extraction and Exchange"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95536 …}
    #channels: Doctrine\ORM\PersistentCollection {#95548 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95544 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95534 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95559
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708297200 {#95558
      date: 2024-02-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1706223600 {#95557
      date: 2024-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3806"
    -bookCollection: ""
    -pageCount: 59
    -documents: Doctrine\ORM\PersistentCollection {#95531 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95527 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.25 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95556
    #id: 12615
    #code: "IEEE00010302"
    #attributes: Doctrine\ORM\PersistentCollection {#95550 …}
    #variants: Doctrine\ORM\PersistentCollection {#95552 …}
    #options: Doctrine\ORM\PersistentCollection {#95587 …}
    #associations: Doctrine\ORM\PersistentCollection {#95554 …}
    #createdAt: DateTime @1751040549 {#95561
      date: 2025-06-27 18:09:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95560
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95525 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96436
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95556}
        #id: 45469
        #name: "IEEE 3806:2023"
        #slug: "ieee-3806-2023-ieee00010302-244270"
        #description: """
          New IEEE Standard - Active.<br />\n
          Liver and gallbladder diseases affect more than one billion people around the world, but there is still a lack of successful experience and models in terms of data standardization, integration, and sharing. The goal of this document is to solve the above problems through blockchain-based data circulation standards. This standard mainly describes the format of the data circulation and the application process of hepatobiliary diseases, which standardize the data collection, processing, and exchange process of hepatobiliary disease data in the medical information system, aiming to bring a new data credible circulation innovation model for medical education, data sharing applications, and medical artificial intelligence product research and development of hepatobiliary disease big data.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the blockchain-based system architecture, interfaces, protocols, testing, and verification for the extraction and exchange of hepatobiliary disease data across multiple organizations and stakeholders.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Blockchain-Based Hepatobiliary Disease Data Extraction and Exchange"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95536 …}
    #channels: Doctrine\ORM\PersistentCollection {#95548 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95544 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95534 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95559
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708297200 {#95558
      date: 2024-02-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1706223600 {#95557
      date: 2024-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3806"
    -bookCollection: ""
    -pageCount: 59
    -documents: Doctrine\ORM\PersistentCollection {#95531 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95527 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#96450
  +product: App\Entity\Product\Product {#95556
    #id: 12615
    #code: "IEEE00010302"
    #attributes: Doctrine\ORM\PersistentCollection {#95550 …}
    #variants: Doctrine\ORM\PersistentCollection {#95552 …}
    #options: Doctrine\ORM\PersistentCollection {#95587 …}
    #associations: Doctrine\ORM\PersistentCollection {#95554 …}
    #createdAt: DateTime @1751040549 {#95561
      date: 2025-06-27 18:09:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95560
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95525 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96436
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95556}
        #id: 45469
        #name: "IEEE 3806:2023"
        #slug: "ieee-3806-2023-ieee00010302-244270"
        #description: """
          New IEEE Standard - Active.<br />\n
          Liver and gallbladder diseases affect more than one billion people around the world, but there is still a lack of successful experience and models in terms of data standardization, integration, and sharing. The goal of this document is to solve the above problems through blockchain-based data circulation standards. This standard mainly describes the format of the data circulation and the application process of hepatobiliary diseases, which standardize the data collection, processing, and exchange process of hepatobiliary disease data in the medical information system, aiming to bring a new data credible circulation innovation model for medical education, data sharing applications, and medical artificial intelligence product research and development of hepatobiliary disease big data.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the blockchain-based system architecture, interfaces, protocols, testing, and verification for the extraction and exchange of hepatobiliary disease data across multiple organizations and stakeholders.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Blockchain-Based Hepatobiliary Disease Data Extraction and Exchange"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95536 …}
    #channels: Doctrine\ORM\PersistentCollection {#95548 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95544 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95534 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95559
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708297200 {#95558
      date: 2024-02-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1706223600 {#95557
      date: 2024-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3806"
    -bookCollection: ""
    -pageCount: 59
    -documents: Doctrine\ORM\PersistentCollection {#95531 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95527 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 1.02 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95556
    #id: 12615
    #code: "IEEE00010302"
    #attributes: Doctrine\ORM\PersistentCollection {#95550 …}
    #variants: Doctrine\ORM\PersistentCollection {#95552 …}
    #options: Doctrine\ORM\PersistentCollection {#95587 …}
    #associations: Doctrine\ORM\PersistentCollection {#95554 …}
    #createdAt: DateTime @1751040549 {#95561
      date: 2025-06-27 18:09:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95560
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95525 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96436
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95556}
        #id: 45469
        #name: "IEEE 3806:2023"
        #slug: "ieee-3806-2023-ieee00010302-244270"
        #description: """
          New IEEE Standard - Active.<br />\n
          Liver and gallbladder diseases affect more than one billion people around the world, but there is still a lack of successful experience and models in terms of data standardization, integration, and sharing. The goal of this document is to solve the above problems through blockchain-based data circulation standards. This standard mainly describes the format of the data circulation and the application process of hepatobiliary diseases, which standardize the data collection, processing, and exchange process of hepatobiliary disease data in the medical information system, aiming to bring a new data credible circulation innovation model for medical education, data sharing applications, and medical artificial intelligence product research and development of hepatobiliary disease big data.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the blockchain-based system architecture, interfaces, protocols, testing, and verification for the extraction and exchange of hepatobiliary disease data across multiple organizations and stakeholders.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Blockchain-Based Hepatobiliary Disease Data Extraction and Exchange"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95536 …}
    #channels: Doctrine\ORM\PersistentCollection {#95548 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95544 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95534 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95559
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708297200 {#95558
      date: 2024-02-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1706223600 {#95557
      date: 2024-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3806"
    -bookCollection: ""
    -pageCount: 59
    -documents: Doctrine\ORM\PersistentCollection {#95531 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95527 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#96524
  +product: App\Entity\Product\Product {#95556
    #id: 12615
    #code: "IEEE00010302"
    #attributes: Doctrine\ORM\PersistentCollection {#95550 …}
    #variants: Doctrine\ORM\PersistentCollection {#95552 …}
    #options: Doctrine\ORM\PersistentCollection {#95587 …}
    #associations: Doctrine\ORM\PersistentCollection {#95554 …}
    #createdAt: DateTime @1751040549 {#95561
      date: 2025-06-27 18:09:09.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95560
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95525 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96436
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95556}
        #id: 45469
        #name: "IEEE 3806:2023"
        #slug: "ieee-3806-2023-ieee00010302-244270"
        #description: """
          New IEEE Standard - Active.<br />\n
          Liver and gallbladder diseases affect more than one billion people around the world, but there is still a lack of successful experience and models in terms of data standardization, integration, and sharing. The goal of this document is to solve the above problems through blockchain-based data circulation standards. This standard mainly describes the format of the data circulation and the application process of hepatobiliary diseases, which standardize the data collection, processing, and exchange process of hepatobiliary disease data in the medical information system, aiming to bring a new data credible circulation innovation model for medical education, data sharing applications, and medical artificial intelligence product research and development of hepatobiliary disease big data.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the blockchain-based system architecture, interfaces, protocols, testing, and verification for the extraction and exchange of hepatobiliary disease data across multiple organizations and stakeholders.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Blockchain-Based Hepatobiliary Disease Data Extraction and Exchange"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95536 …}
    #channels: Doctrine\ORM\PersistentCollection {#95548 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95544 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95546 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95534 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95559
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1708297200 {#95558
      date: 2024-02-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1706223600 {#95557
      date: 2024-01-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "3806"
    -bookCollection: ""
    -pageCount: 59
    -documents: Doctrine\ORM\PersistentCollection {#95531 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95527 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 14.78 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95594
    #id: 12616
    #code: "IEEE00010304"
    #attributes: Doctrine\ORM\PersistentCollection {#95611 …}
    #variants: Doctrine\ORM\PersistentCollection {#95613 …}
    #options: Doctrine\ORM\PersistentCollection {#95617 …}
    #associations: Doctrine\ORM\PersistentCollection {#95615 …}
    #createdAt: DateTime @1751040550 {#95589
      date: 2025-06-27 18:09:10.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95590
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95601 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96666
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95594}
        #id: 45473
        #name: "IEEE 2884:2023"
        #slug: "ieee-2884-2023-ieee00010304-244271"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n
          \t\t\t\t<br />\n
          This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95603 …}
    #channels: Doctrine\ORM\PersistentCollection {#95609 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95605 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95607 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95595 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95591
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95592
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1694728800 {#95593
      date: 2023-09-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2884"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95597 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95599 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#96646
  +product: App\Entity\Product\Product {#95594
    #id: 12616
    #code: "IEEE00010304"
    #attributes: Doctrine\ORM\PersistentCollection {#95611 …}
    #variants: Doctrine\ORM\PersistentCollection {#95613 …}
    #options: Doctrine\ORM\PersistentCollection {#95617 …}
    #associations: Doctrine\ORM\PersistentCollection {#95615 …}
    #createdAt: DateTime @1751040550 {#95589
      date: 2025-06-27 18:09:10.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95590
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95601 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96666
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95594}
        #id: 45473
        #name: "IEEE 2884:2023"
        #slug: "ieee-2884-2023-ieee00010304-244271"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n
          \t\t\t\t<br />\n
          This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95603 …}
    #channels: Doctrine\ORM\PersistentCollection {#95609 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95605 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95607 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95595 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95591
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95592
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1694728800 {#95593
      date: 2023-09-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2884"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95597 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95599 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.79 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95594
    #id: 12616
    #code: "IEEE00010304"
    #attributes: Doctrine\ORM\PersistentCollection {#95611 …}
    #variants: Doctrine\ORM\PersistentCollection {#95613 …}
    #options: Doctrine\ORM\PersistentCollection {#95617 …}
    #associations: Doctrine\ORM\PersistentCollection {#95615 …}
    #createdAt: DateTime @1751040550 {#95589
      date: 2025-06-27 18:09:10.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95590
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95601 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96666
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95594}
        #id: 45473
        #name: "IEEE 2884:2023"
        #slug: "ieee-2884-2023-ieee00010304-244271"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n
          \t\t\t\t<br />\n
          This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95603 …}
    #channels: Doctrine\ORM\PersistentCollection {#95609 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95605 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95607 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95595 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95591
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95592
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1694728800 {#95593
      date: 2023-09-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2884"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95597 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95599 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#96680
  +product: App\Entity\Product\Product {#95594
    #id: 12616
    #code: "IEEE00010304"
    #attributes: Doctrine\ORM\PersistentCollection {#95611 …}
    #variants: Doctrine\ORM\PersistentCollection {#95613 …}
    #options: Doctrine\ORM\PersistentCollection {#95617 …}
    #associations: Doctrine\ORM\PersistentCollection {#95615 …}
    #createdAt: DateTime @1751040550 {#95589
      date: 2025-06-27 18:09:10.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95590
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95601 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96666
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95594}
        #id: 45473
        #name: "IEEE 2884:2023"
        #slug: "ieee-2884-2023-ieee00010304-244271"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n
          \t\t\t\t<br />\n
          This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95603 …}
    #channels: Doctrine\ORM\PersistentCollection {#95609 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95605 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95607 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95595 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95591
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95592
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1694728800 {#95593
      date: 2023-09-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2884"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95597 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95599 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 1.73 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95594
    #id: 12616
    #code: "IEEE00010304"
    #attributes: Doctrine\ORM\PersistentCollection {#95611 …}
    #variants: Doctrine\ORM\PersistentCollection {#95613 …}
    #options: Doctrine\ORM\PersistentCollection {#95617 …}
    #associations: Doctrine\ORM\PersistentCollection {#95615 …}
    #createdAt: DateTime @1751040550 {#95589
      date: 2025-06-27 18:09:10.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95590
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95601 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96666
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95594}
        #id: 45473
        #name: "IEEE 2884:2023"
        #slug: "ieee-2884-2023-ieee00010304-244271"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n
          \t\t\t\t<br />\n
          This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95603 …}
    #channels: Doctrine\ORM\PersistentCollection {#95609 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95605 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95607 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95595 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95591
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95592
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1694728800 {#95593
      date: 2023-09-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2884"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95597 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95599 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#96754
  +product: App\Entity\Product\Product {#95594
    #id: 12616
    #code: "IEEE00010304"
    #attributes: Doctrine\ORM\PersistentCollection {#95611 …}
    #variants: Doctrine\ORM\PersistentCollection {#95613 …}
    #options: Doctrine\ORM\PersistentCollection {#95617 …}
    #associations: Doctrine\ORM\PersistentCollection {#95615 …}
    #createdAt: DateTime @1751040550 {#95589
      date: 2025-06-27 18:09:10.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95590
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95601 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96666
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95594}
        #id: 45473
        #name: "IEEE 2884:2023"
        #slug: "ieee-2884-2023-ieee00010304-244271"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n
          \t\t\t\t<br />\n
          This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95603 …}
    #channels: Doctrine\ORM\PersistentCollection {#95609 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95605 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95607 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95595 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95591
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95592
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1694728800 {#95593
      date: 2023-09-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2884"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95597 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95599 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 10.44 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95624
    #id: 12617
    #code: "IEEE00010306"
    #attributes: Doctrine\ORM\PersistentCollection {#95641 …}
    #variants: Doctrine\ORM\PersistentCollection {#95643 …}
    #options: Doctrine\ORM\PersistentCollection {#95647 …}
    #associations: Doctrine\ORM\PersistentCollection {#95645 …}
    #createdAt: DateTime @1751040551 {#95619
      date: 2025-06-27 18:09:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95620
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95631 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96896
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95624}
        #id: 45477
        #name: "IEEE 2891:2023"
        #slug: "ieee-2891-2023-ieee00010306-244272"
        #description: """
          New IEEE Standard - Active.<br />\n
          The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n
          \t\t\t\t<br />\n
          This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n
          This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95633 …}
    #channels: Doctrine\ORM\PersistentCollection {#95639 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95635 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95637 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95621
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95622
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1695333600 {#95623
      date: 2023-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2891"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95627 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95629 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#96876
  +product: App\Entity\Product\Product {#95624
    #id: 12617
    #code: "IEEE00010306"
    #attributes: Doctrine\ORM\PersistentCollection {#95641 …}
    #variants: Doctrine\ORM\PersistentCollection {#95643 …}
    #options: Doctrine\ORM\PersistentCollection {#95647 …}
    #associations: Doctrine\ORM\PersistentCollection {#95645 …}
    #createdAt: DateTime @1751040551 {#95619
      date: 2025-06-27 18:09:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95620
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95631 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96896
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95624}
        #id: 45477
        #name: "IEEE 2891:2023"
        #slug: "ieee-2891-2023-ieee00010306-244272"
        #description: """
          New IEEE Standard - Active.<br />\n
          The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n
          \t\t\t\t<br />\n
          This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n
          This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95633 …}
    #channels: Doctrine\ORM\PersistentCollection {#95639 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95635 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95637 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95621
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95622
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1695333600 {#95623
      date: 2023-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2891"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95627 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95629 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.27 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95624
    #id: 12617
    #code: "IEEE00010306"
    #attributes: Doctrine\ORM\PersistentCollection {#95641 …}
    #variants: Doctrine\ORM\PersistentCollection {#95643 …}
    #options: Doctrine\ORM\PersistentCollection {#95647 …}
    #associations: Doctrine\ORM\PersistentCollection {#95645 …}
    #createdAt: DateTime @1751040551 {#95619
      date: 2025-06-27 18:09:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95620
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95631 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96896
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95624}
        #id: 45477
        #name: "IEEE 2891:2023"
        #slug: "ieee-2891-2023-ieee00010306-244272"
        #description: """
          New IEEE Standard - Active.<br />\n
          The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n
          \t\t\t\t<br />\n
          This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n
          This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95633 …}
    #channels: Doctrine\ORM\PersistentCollection {#95639 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95635 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95637 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95621
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95622
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1695333600 {#95623
      date: 2023-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2891"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95627 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95629 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#96910
  +product: App\Entity\Product\Product {#95624
    #id: 12617
    #code: "IEEE00010306"
    #attributes: Doctrine\ORM\PersistentCollection {#95641 …}
    #variants: Doctrine\ORM\PersistentCollection {#95643 …}
    #options: Doctrine\ORM\PersistentCollection {#95647 …}
    #associations: Doctrine\ORM\PersistentCollection {#95645 …}
    #createdAt: DateTime @1751040551 {#95619
      date: 2025-06-27 18:09:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95620
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95631 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96896
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95624}
        #id: 45477
        #name: "IEEE 2891:2023"
        #slug: "ieee-2891-2023-ieee00010306-244272"
        #description: """
          New IEEE Standard - Active.<br />\n
          The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n
          \t\t\t\t<br />\n
          This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n
          This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95633 …}
    #channels: Doctrine\ORM\PersistentCollection {#95639 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95635 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95637 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95621
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95622
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1695333600 {#95623
      date: 2023-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2891"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95627 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95629 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.95 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95624
    #id: 12617
    #code: "IEEE00010306"
    #attributes: Doctrine\ORM\PersistentCollection {#95641 …}
    #variants: Doctrine\ORM\PersistentCollection {#95643 …}
    #options: Doctrine\ORM\PersistentCollection {#95647 …}
    #associations: Doctrine\ORM\PersistentCollection {#95645 …}
    #createdAt: DateTime @1751040551 {#95619
      date: 2025-06-27 18:09:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95620
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95631 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96896
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95624}
        #id: 45477
        #name: "IEEE 2891:2023"
        #slug: "ieee-2891-2023-ieee00010306-244272"
        #description: """
          New IEEE Standard - Active.<br />\n
          The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n
          \t\t\t\t<br />\n
          This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n
          This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95633 …}
    #channels: Doctrine\ORM\PersistentCollection {#95639 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95635 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95637 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95621
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95622
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1695333600 {#95623
      date: 2023-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2891"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95627 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95629 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#96984
  +product: App\Entity\Product\Product {#95624
    #id: 12617
    #code: "IEEE00010306"
    #attributes: Doctrine\ORM\PersistentCollection {#95641 …}
    #variants: Doctrine\ORM\PersistentCollection {#95643 …}
    #options: Doctrine\ORM\PersistentCollection {#95647 …}
    #associations: Doctrine\ORM\PersistentCollection {#95645 …}
    #createdAt: DateTime @1751040551 {#95619
      date: 2025-06-27 18:09:11.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95620
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95631 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96896
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95624}
        #id: 45477
        #name: "IEEE 2891:2023"
        #slug: "ieee-2891-2023-ieee00010306-244272"
        #description: """
          New IEEE Standard - Active.<br />\n
          The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n
          \t\t\t\t<br />\n
          This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n
          This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95633 …}
    #channels: Doctrine\ORM\PersistentCollection {#95639 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95635 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95637 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95621
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1698012000 {#95622
      date: 2023-10-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1695333600 {#95623
      date: 2023-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2891"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#95627 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95629 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.60 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95654
    #id: 12620
    #code: "IEEE00010320"
    #attributes: Doctrine\ORM\PersistentCollection {#95671 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95677 …}
    #associations: Doctrine\ORM\PersistentCollection {#95675 …}
    #createdAt: DateTime @1751040553 {#95649
      date: 2025-06-27 18:09:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95650
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95661 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97126
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95654}
        #id: 45489
        #name: "IEEE 2889:2021"
        #slug: "ieee-2889-2021-ieee00010320-244275"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz is provided. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          \t\t\t\t<br />\n
          This document provides guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          The incident power density (IPD) is generally spatially averaged over an averaging area. Two quantities may be used to define the spatially averaged IPD, either using the normal component of IPD vectors crossing the surface, or magnitude of IPD vectors (norm) averaged over an area independent of the orientation.<br />\n
          This document provides guidance for determining the appropriate definition of IPD. The guide examines theoretical, computational, and measurement data that are relevant to the validity of each method, taking into account the dependence of the IPD metric and its averaging methods on surface temperature rise in the frequency range 6 GHz to 300 GHz.<br />\n
          This guide might be used in the development of standards for the EMF exposure limits or in the EMF compliance assessment standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Definition of Incident Power Density to Correlate Surface Temperature Elevation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95663 …}
    #channels: Doctrine\ORM\PersistentCollection {#95669 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95665 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95667 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95655 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642978800 {#95652
      date: 2022-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95653
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2889"
    -bookCollection: ""
    -pageCount: 152
    -documents: Doctrine\ORM\PersistentCollection {#95657 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95659 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#97106
  +product: App\Entity\Product\Product {#95654
    #id: 12620
    #code: "IEEE00010320"
    #attributes: Doctrine\ORM\PersistentCollection {#95671 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95677 …}
    #associations: Doctrine\ORM\PersistentCollection {#95675 …}
    #createdAt: DateTime @1751040553 {#95649
      date: 2025-06-27 18:09:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95650
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95661 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97126
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95654}
        #id: 45489
        #name: "IEEE 2889:2021"
        #slug: "ieee-2889-2021-ieee00010320-244275"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz is provided. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          \t\t\t\t<br />\n
          This document provides guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          The incident power density (IPD) is generally spatially averaged over an averaging area. Two quantities may be used to define the spatially averaged IPD, either using the normal component of IPD vectors crossing the surface, or magnitude of IPD vectors (norm) averaged over an area independent of the orientation.<br />\n
          This document provides guidance for determining the appropriate definition of IPD. The guide examines theoretical, computational, and measurement data that are relevant to the validity of each method, taking into account the dependence of the IPD metric and its averaging methods on surface temperature rise in the frequency range 6 GHz to 300 GHz.<br />\n
          This guide might be used in the development of standards for the EMF exposure limits or in the EMF compliance assessment standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Definition of Incident Power Density to Correlate Surface Temperature Elevation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95663 …}
    #channels: Doctrine\ORM\PersistentCollection {#95669 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95665 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95667 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95655 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642978800 {#95652
      date: 2022-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95653
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2889"
    -bookCollection: ""
    -pageCount: 152
    -documents: Doctrine\ORM\PersistentCollection {#95657 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95659 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.19 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95654
    #id: 12620
    #code: "IEEE00010320"
    #attributes: Doctrine\ORM\PersistentCollection {#95671 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95677 …}
    #associations: Doctrine\ORM\PersistentCollection {#95675 …}
    #createdAt: DateTime @1751040553 {#95649
      date: 2025-06-27 18:09:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95650
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95661 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97126
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95654}
        #id: 45489
        #name: "IEEE 2889:2021"
        #slug: "ieee-2889-2021-ieee00010320-244275"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz is provided. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          \t\t\t\t<br />\n
          This document provides guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          The incident power density (IPD) is generally spatially averaged over an averaging area. Two quantities may be used to define the spatially averaged IPD, either using the normal component of IPD vectors crossing the surface, or magnitude of IPD vectors (norm) averaged over an area independent of the orientation.<br />\n
          This document provides guidance for determining the appropriate definition of IPD. The guide examines theoretical, computational, and measurement data that are relevant to the validity of each method, taking into account the dependence of the IPD metric and its averaging methods on surface temperature rise in the frequency range 6 GHz to 300 GHz.<br />\n
          This guide might be used in the development of standards for the EMF exposure limits or in the EMF compliance assessment standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Definition of Incident Power Density to Correlate Surface Temperature Elevation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95663 …}
    #channels: Doctrine\ORM\PersistentCollection {#95669 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95665 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95667 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95655 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642978800 {#95652
      date: 2022-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95653
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2889"
    -bookCollection: ""
    -pageCount: 152
    -documents: Doctrine\ORM\PersistentCollection {#95657 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95659 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#97140
  +product: App\Entity\Product\Product {#95654
    #id: 12620
    #code: "IEEE00010320"
    #attributes: Doctrine\ORM\PersistentCollection {#95671 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95677 …}
    #associations: Doctrine\ORM\PersistentCollection {#95675 …}
    #createdAt: DateTime @1751040553 {#95649
      date: 2025-06-27 18:09:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95650
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95661 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97126
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95654}
        #id: 45489
        #name: "IEEE 2889:2021"
        #slug: "ieee-2889-2021-ieee00010320-244275"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz is provided. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          \t\t\t\t<br />\n
          This document provides guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          The incident power density (IPD) is generally spatially averaged over an averaging area. Two quantities may be used to define the spatially averaged IPD, either using the normal component of IPD vectors crossing the surface, or magnitude of IPD vectors (norm) averaged over an area independent of the orientation.<br />\n
          This document provides guidance for determining the appropriate definition of IPD. The guide examines theoretical, computational, and measurement data that are relevant to the validity of each method, taking into account the dependence of the IPD metric and its averaging methods on surface temperature rise in the frequency range 6 GHz to 300 GHz.<br />\n
          This guide might be used in the development of standards for the EMF exposure limits or in the EMF compliance assessment standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Definition of Incident Power Density to Correlate Surface Temperature Elevation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95663 …}
    #channels: Doctrine\ORM\PersistentCollection {#95669 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95665 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95667 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95655 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642978800 {#95652
      date: 2022-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95653
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2889"
    -bookCollection: ""
    -pageCount: 152
    -documents: Doctrine\ORM\PersistentCollection {#95657 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95659 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.61 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95654
    #id: 12620
    #code: "IEEE00010320"
    #attributes: Doctrine\ORM\PersistentCollection {#95671 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95677 …}
    #associations: Doctrine\ORM\PersistentCollection {#95675 …}
    #createdAt: DateTime @1751040553 {#95649
      date: 2025-06-27 18:09:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95650
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95661 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97126
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95654}
        #id: 45489
        #name: "IEEE 2889:2021"
        #slug: "ieee-2889-2021-ieee00010320-244275"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz is provided. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          \t\t\t\t<br />\n
          This document provides guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          The incident power density (IPD) is generally spatially averaged over an averaging area. Two quantities may be used to define the spatially averaged IPD, either using the normal component of IPD vectors crossing the surface, or magnitude of IPD vectors (norm) averaged over an area independent of the orientation.<br />\n
          This document provides guidance for determining the appropriate definition of IPD. The guide examines theoretical, computational, and measurement data that are relevant to the validity of each method, taking into account the dependence of the IPD metric and its averaging methods on surface temperature rise in the frequency range 6 GHz to 300 GHz.<br />\n
          This guide might be used in the development of standards for the EMF exposure limits or in the EMF compliance assessment standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Definition of Incident Power Density to Correlate Surface Temperature Elevation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95663 …}
    #channels: Doctrine\ORM\PersistentCollection {#95669 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95665 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95667 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95655 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642978800 {#95652
      date: 2022-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95653
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2889"
    -bookCollection: ""
    -pageCount: 152
    -documents: Doctrine\ORM\PersistentCollection {#95657 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95659 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#97214
  +product: App\Entity\Product\Product {#95654
    #id: 12620
    #code: "IEEE00010320"
    #attributes: Doctrine\ORM\PersistentCollection {#95671 …}
    #variants: Doctrine\ORM\PersistentCollection {#95673 …}
    #options: Doctrine\ORM\PersistentCollection {#95677 …}
    #associations: Doctrine\ORM\PersistentCollection {#95675 …}
    #createdAt: DateTime @1751040553 {#95649
      date: 2025-06-27 18:09:13.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95650
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95661 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97126
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95654}
        #id: 45489
        #name: "IEEE 2889:2021"
        #slug: "ieee-2889-2021-ieee00010320-244275"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz is provided. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          \t\t\t\t<br />\n
          This document provides guidance on the definition of the incident power density in correlation with surface temperature elevation in the frequency range from 6 GHz to 300 GHz. Using numerical simulations or measurement, this guide is also applicable to compliance assessment of wireless products operating in millimeter wave frequencies.<br />\n
          The incident power density (IPD) is generally spatially averaged over an averaging area. Two quantities may be used to define the spatially averaged IPD, either using the normal component of IPD vectors crossing the surface, or magnitude of IPD vectors (norm) averaged over an area independent of the orientation.<br />\n
          This document provides guidance for determining the appropriate definition of IPD. The guide examines theoretical, computational, and measurement data that are relevant to the validity of each method, taking into account the dependence of the IPD metric and its averaging methods on surface temperature rise in the frequency range 6 GHz to 300 GHz.<br />\n
          This guide might be used in the development of standards for the EMF exposure limits or in the EMF compliance assessment standards.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Definition of Incident Power Density to Correlate Surface Temperature Elevation"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95663 …}
    #channels: Doctrine\ORM\PersistentCollection {#95669 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95665 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95667 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95655 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95651
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642978800 {#95652
      date: 2022-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95653
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2889"
    -bookCollection: ""
    -pageCount: 152
    -documents: Doctrine\ORM\PersistentCollection {#95657 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95659 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.55 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95685
    #id: 12622
    #code: "IEEE00010323"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040554 {#95679
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95680
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97356
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45497
        #name: "IEEE 802.1Q:2022"
        #slug: "ieee-802-1q-2022-ieee00010323-244277"
        #description: """
          Revision Standard - Active.<br />\n
          This standard specifies how the Media Access Control (MAC) Service is supported by Bridged Networks, the principles of operation of those networks, and the operation of MAC Bridges and VLAN Bridges, including management, protocols, and algorithms. (The PDF of this standard is available at no cost compliments of the IEEE GET program https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68)<br />\n
          \t\t\t\t<br />\n
          This standard specifies Bridges that interconnect individual LANs, each supporting the IEEE 802 MAC Service using a different or identical media access control method, to provide Bridged Networks and VLANs.<br />\n
          Bridges, as specified by this standard, allow the compatible interconnection of information technology equipment attached to separate individual LANs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1752357600 {#95681
      date: 2025-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704409200 {#95682
      date: 2024-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1671663600 {#95683
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1671663600 {#95684
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "802.1Q"
    -bookCollection: ""
    -pageCount: 2163
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#97336
  +product: App\Entity\Product\Product {#95685
    #id: 12622
    #code: "IEEE00010323"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040554 {#95679
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95680
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97356
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45497
        #name: "IEEE 802.1Q:2022"
        #slug: "ieee-802-1q-2022-ieee00010323-244277"
        #description: """
          Revision Standard - Active.<br />\n
          This standard specifies how the Media Access Control (MAC) Service is supported by Bridged Networks, the principles of operation of those networks, and the operation of MAC Bridges and VLAN Bridges, including management, protocols, and algorithms. (The PDF of this standard is available at no cost compliments of the IEEE GET program https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68)<br />\n
          \t\t\t\t<br />\n
          This standard specifies Bridges that interconnect individual LANs, each supporting the IEEE 802 MAC Service using a different or identical media access control method, to provide Bridged Networks and VLANs.<br />\n
          Bridges, as specified by this standard, allow the compatible interconnection of information technology equipment attached to separate individual LANs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1752357600 {#95681
      date: 2025-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704409200 {#95682
      date: 2024-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1671663600 {#95683
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1671663600 {#95684
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "802.1Q"
    -bookCollection: ""
    -pageCount: 2163
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95685
    #id: 12622
    #code: "IEEE00010323"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040554 {#95679
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95680
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97356
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45497
        #name: "IEEE 802.1Q:2022"
        #slug: "ieee-802-1q-2022-ieee00010323-244277"
        #description: """
          Revision Standard - Active.<br />\n
          This standard specifies how the Media Access Control (MAC) Service is supported by Bridged Networks, the principles of operation of those networks, and the operation of MAC Bridges and VLAN Bridges, including management, protocols, and algorithms. (The PDF of this standard is available at no cost compliments of the IEEE GET program https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68)<br />\n
          \t\t\t\t<br />\n
          This standard specifies Bridges that interconnect individual LANs, each supporting the IEEE 802 MAC Service using a different or identical media access control method, to provide Bridged Networks and VLANs.<br />\n
          Bridges, as specified by this standard, allow the compatible interconnection of information technology equipment attached to separate individual LANs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1752357600 {#95681
      date: 2025-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704409200 {#95682
      date: 2024-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1671663600 {#95683
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1671663600 {#95684
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "802.1Q"
    -bookCollection: ""
    -pageCount: 2163
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#97363
  +product: App\Entity\Product\Product {#95685
    #id: 12622
    #code: "IEEE00010323"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040554 {#95679
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95680
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97356
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45497
        #name: "IEEE 802.1Q:2022"
        #slug: "ieee-802-1q-2022-ieee00010323-244277"
        #description: """
          Revision Standard - Active.<br />\n
          This standard specifies how the Media Access Control (MAC) Service is supported by Bridged Networks, the principles of operation of those networks, and the operation of MAC Bridges and VLAN Bridges, including management, protocols, and algorithms. (The PDF of this standard is available at no cost compliments of the IEEE GET program https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68)<br />\n
          \t\t\t\t<br />\n
          This standard specifies Bridges that interconnect individual LANs, each supporting the IEEE 802 MAC Service using a different or identical media access control method, to provide Bridged Networks and VLANs.<br />\n
          Bridges, as specified by this standard, allow the compatible interconnection of information technology equipment attached to separate individual LANs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1752357600 {#95681
      date: 2025-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704409200 {#95682
      date: 2024-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1671663600 {#95683
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1671663600 {#95684
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "802.1Q"
    -bookCollection: ""
    -pageCount: 2163
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.61 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95685
    #id: 12622
    #code: "IEEE00010323"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040554 {#95679
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95680
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97356
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45497
        #name: "IEEE 802.1Q:2022"
        #slug: "ieee-802-1q-2022-ieee00010323-244277"
        #description: """
          Revision Standard - Active.<br />\n
          This standard specifies how the Media Access Control (MAC) Service is supported by Bridged Networks, the principles of operation of those networks, and the operation of MAC Bridges and VLAN Bridges, including management, protocols, and algorithms. (The PDF of this standard is available at no cost compliments of the IEEE GET program https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68)<br />\n
          \t\t\t\t<br />\n
          This standard specifies Bridges that interconnect individual LANs, each supporting the IEEE 802 MAC Service using a different or identical media access control method, to provide Bridged Networks and VLANs.<br />\n
          Bridges, as specified by this standard, allow the compatible interconnection of information technology equipment attached to separate individual LANs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1752357600 {#95681
      date: 2025-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704409200 {#95682
      date: 2024-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1671663600 {#95683
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1671663600 {#95684
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "802.1Q"
    -bookCollection: ""
    -pageCount: 2163
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#97440
  +product: App\Entity\Product\Product {#95685
    #id: 12622
    #code: "IEEE00010323"
    #attributes: Doctrine\ORM\PersistentCollection {#95702 …}
    #variants: Doctrine\ORM\PersistentCollection {#95704 …}
    #options: Doctrine\ORM\PersistentCollection {#95708 …}
    #associations: Doctrine\ORM\PersistentCollection {#95706 …}
    #createdAt: DateTime @1751040554 {#95679
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95680
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95692 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97356
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95685}
        #id: 45497
        #name: "IEEE 802.1Q:2022"
        #slug: "ieee-802-1q-2022-ieee00010323-244277"
        #description: """
          Revision Standard - Active.<br />\n
          This standard specifies how the Media Access Control (MAC) Service is supported by Bridged Networks, the principles of operation of those networks, and the operation of MAC Bridges and VLAN Bridges, including management, protocols, and algorithms. (The PDF of this standard is available at no cost compliments of the IEEE GET program https://ieeexplore.ieee.org/browse/standards/get-program/page/series?id=68)<br />\n
          \t\t\t\t<br />\n
          This standard specifies Bridges that interconnect individual LANs, each supporting the IEEE 802 MAC Service using a different or identical media access control method, to provide Bridged Networks and VLANs.<br />\n
          Bridges, as specified by this standard, allow the compatible interconnection of information technology equipment attached to separate individual LANs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Local and Metropolitan Area Networks--Bridges and Bridged Networks"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95694 …}
    #channels: Doctrine\ORM\PersistentCollection {#95700 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95696 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95698 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95686 …}
    -apiLastModifiedAt: DateTime @1752357600 {#95681
      date: 2025-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704409200 {#95682
      date: 2024-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1671663600 {#95683
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1671663600 {#95684
      date: 2022-12-22 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "802.1Q"
    -bookCollection: ""
    -pageCount: 2163
    -documents: Doctrine\ORM\PersistentCollection {#95688 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95690 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.27 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95715
    #id: 12623
    #code: "IEEE00010324"
    #attributes: Doctrine\ORM\PersistentCollection {#95732 …}
    #variants: Doctrine\ORM\PersistentCollection {#95734 …}
    #options: Doctrine\ORM\PersistentCollection {#95738 …}
    #associations: Doctrine\ORM\PersistentCollection {#95736 …}
    #createdAt: DateTime @1751040554 {#95710
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95711
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95722 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95715}
        #id: 45501
        #name: "IEEE 1484.11.1:2022"
        #slug: "ieee-1484-11-1-2022-ieee00010324-244278"
        #description: """
          Revision Standard - Active.<br />\n
          A data model to support the interchange of data elements and their values between a content object and a runtime service (RTS) is described in this standard. This standard is based on a current industry practice called “computer managed instruction” (CMI). The work on which this standard is based was developed to support a client–server environment in which a learning technology system, generically called a “learning management system” (LMS), delivers digital content, called “content objects,” to learners. The data model supports learner data and preferences; interactions; objectives; content-object entry, exit, and status information; time parameters; and scores.<br />\n
          \t\t\t\t<br />\n
          This standard describes a data model to support the interchange of agreed-upon data elements and their values between a learning-related content object and a runtime service (RTS) used to support learning management. This standard does not specify the means of communication between a content object and an RTS nor how any component of a learning environment shall behave in response to receiving data in the form specified. This standard is based on a related data model defined in “Computer Managed Instruction (CMI) Guidelines For Interoperability,” version 3.5 [B1] by the Aviation Industry CBT Committee (AICC). To balance the need to support existing implementations with the need to make technical corrections and support emerging practice, this standard selectively includes those data elements from the CMI specification that are commonly implemented; renames some data elements taken from the CMI specification to clarify their intended meaning; modifies the data types of data elements taken from the CMI specification to reflect ISO standard data types and internationalization requirements; removes some organizational structures used in the CMI specification to group data elements that are specific to the AICC community of practice and not generally applicable; and introduces some data elements not present in the CMI specification to correct known technical deficiencies in data elements taken from that specification<br />\n
          There is widespread acknowledgment that the data model for content object communication defined in the AICC “Computer Managed Instruction (CMI) Guidelines for Interoperability”, version 3.5 [B1], has broad applicability to systems used for learning management. The purpose of this standard is to build consensus around, resolve ambiguities in, and correct defects in the AICC data model for the data exchanged between learning-related content objects and an RTS used to support learning management.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Learning Technology--Data Model for Content Object Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95724 …}
    #channels: Doctrine\ORM\PersistentCollection {#95730 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95728 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95716 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95712
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1680645600 {#95713
      date: 2023-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649973600 {#95714
      date: 2022-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1484.11.1"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#95718 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95720 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#97553
  +product: App\Entity\Product\Product {#95715
    #id: 12623
    #code: "IEEE00010324"
    #attributes: Doctrine\ORM\PersistentCollection {#95732 …}
    #variants: Doctrine\ORM\PersistentCollection {#95734 …}
    #options: Doctrine\ORM\PersistentCollection {#95738 …}
    #associations: Doctrine\ORM\PersistentCollection {#95736 …}
    #createdAt: DateTime @1751040554 {#95710
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95711
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95722 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95715}
        #id: 45501
        #name: "IEEE 1484.11.1:2022"
        #slug: "ieee-1484-11-1-2022-ieee00010324-244278"
        #description: """
          Revision Standard - Active.<br />\n
          A data model to support the interchange of data elements and their values between a content object and a runtime service (RTS) is described in this standard. This standard is based on a current industry practice called “computer managed instruction” (CMI). The work on which this standard is based was developed to support a client–server environment in which a learning technology system, generically called a “learning management system” (LMS), delivers digital content, called “content objects,” to learners. The data model supports learner data and preferences; interactions; objectives; content-object entry, exit, and status information; time parameters; and scores.<br />\n
          \t\t\t\t<br />\n
          This standard describes a data model to support the interchange of agreed-upon data elements and their values between a learning-related content object and a runtime service (RTS) used to support learning management. This standard does not specify the means of communication between a content object and an RTS nor how any component of a learning environment shall behave in response to receiving data in the form specified. This standard is based on a related data model defined in “Computer Managed Instruction (CMI) Guidelines For Interoperability,” version 3.5 [B1] by the Aviation Industry CBT Committee (AICC). To balance the need to support existing implementations with the need to make technical corrections and support emerging practice, this standard selectively includes those data elements from the CMI specification that are commonly implemented; renames some data elements taken from the CMI specification to clarify their intended meaning; modifies the data types of data elements taken from the CMI specification to reflect ISO standard data types and internationalization requirements; removes some organizational structures used in the CMI specification to group data elements that are specific to the AICC community of practice and not generally applicable; and introduces some data elements not present in the CMI specification to correct known technical deficiencies in data elements taken from that specification<br />\n
          There is widespread acknowledgment that the data model for content object communication defined in the AICC “Computer Managed Instruction (CMI) Guidelines for Interoperability”, version 3.5 [B1], has broad applicability to systems used for learning management. The purpose of this standard is to build consensus around, resolve ambiguities in, and correct defects in the AICC data model for the data exchanged between learning-related content objects and an RTS used to support learning management.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Learning Technology--Data Model for Content Object Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95724 …}
    #channels: Doctrine\ORM\PersistentCollection {#95730 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95728 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95716 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95712
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1680645600 {#95713
      date: 2023-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649973600 {#95714
      date: 2022-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1484.11.1"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#95718 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95720 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95715
    #id: 12623
    #code: "IEEE00010324"
    #attributes: Doctrine\ORM\PersistentCollection {#95732 …}
    #variants: Doctrine\ORM\PersistentCollection {#95734 …}
    #options: Doctrine\ORM\PersistentCollection {#95738 …}
    #associations: Doctrine\ORM\PersistentCollection {#95736 …}
    #createdAt: DateTime @1751040554 {#95710
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95711
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95722 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95715}
        #id: 45501
        #name: "IEEE 1484.11.1:2022"
        #slug: "ieee-1484-11-1-2022-ieee00010324-244278"
        #description: """
          Revision Standard - Active.<br />\n
          A data model to support the interchange of data elements and their values between a content object and a runtime service (RTS) is described in this standard. This standard is based on a current industry practice called “computer managed instruction” (CMI). The work on which this standard is based was developed to support a client–server environment in which a learning technology system, generically called a “learning management system” (LMS), delivers digital content, called “content objects,” to learners. The data model supports learner data and preferences; interactions; objectives; content-object entry, exit, and status information; time parameters; and scores.<br />\n
          \t\t\t\t<br />\n
          This standard describes a data model to support the interchange of agreed-upon data elements and their values between a learning-related content object and a runtime service (RTS) used to support learning management. This standard does not specify the means of communication between a content object and an RTS nor how any component of a learning environment shall behave in response to receiving data in the form specified. This standard is based on a related data model defined in “Computer Managed Instruction (CMI) Guidelines For Interoperability,” version 3.5 [B1] by the Aviation Industry CBT Committee (AICC). To balance the need to support existing implementations with the need to make technical corrections and support emerging practice, this standard selectively includes those data elements from the CMI specification that are commonly implemented; renames some data elements taken from the CMI specification to clarify their intended meaning; modifies the data types of data elements taken from the CMI specification to reflect ISO standard data types and internationalization requirements; removes some organizational structures used in the CMI specification to group data elements that are specific to the AICC community of practice and not generally applicable; and introduces some data elements not present in the CMI specification to correct known technical deficiencies in data elements taken from that specification<br />\n
          There is widespread acknowledgment that the data model for content object communication defined in the AICC “Computer Managed Instruction (CMI) Guidelines for Interoperability”, version 3.5 [B1], has broad applicability to systems used for learning management. The purpose of this standard is to build consensus around, resolve ambiguities in, and correct defects in the AICC data model for the data exchanged between learning-related content objects and an RTS used to support learning management.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Learning Technology--Data Model for Content Object Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95724 …}
    #channels: Doctrine\ORM\PersistentCollection {#95730 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95728 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95716 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95712
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1680645600 {#95713
      date: 2023-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649973600 {#95714
      date: 2022-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1484.11.1"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#95718 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95720 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#97591
  +product: App\Entity\Product\Product {#95715
    #id: 12623
    #code: "IEEE00010324"
    #attributes: Doctrine\ORM\PersistentCollection {#95732 …}
    #variants: Doctrine\ORM\PersistentCollection {#95734 …}
    #options: Doctrine\ORM\PersistentCollection {#95738 …}
    #associations: Doctrine\ORM\PersistentCollection {#95736 …}
    #createdAt: DateTime @1751040554 {#95710
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95711
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95722 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95715}
        #id: 45501
        #name: "IEEE 1484.11.1:2022"
        #slug: "ieee-1484-11-1-2022-ieee00010324-244278"
        #description: """
          Revision Standard - Active.<br />\n
          A data model to support the interchange of data elements and their values between a content object and a runtime service (RTS) is described in this standard. This standard is based on a current industry practice called “computer managed instruction” (CMI). The work on which this standard is based was developed to support a client–server environment in which a learning technology system, generically called a “learning management system” (LMS), delivers digital content, called “content objects,” to learners. The data model supports learner data and preferences; interactions; objectives; content-object entry, exit, and status information; time parameters; and scores.<br />\n
          \t\t\t\t<br />\n
          This standard describes a data model to support the interchange of agreed-upon data elements and their values between a learning-related content object and a runtime service (RTS) used to support learning management. This standard does not specify the means of communication between a content object and an RTS nor how any component of a learning environment shall behave in response to receiving data in the form specified. This standard is based on a related data model defined in “Computer Managed Instruction (CMI) Guidelines For Interoperability,” version 3.5 [B1] by the Aviation Industry CBT Committee (AICC). To balance the need to support existing implementations with the need to make technical corrections and support emerging practice, this standard selectively includes those data elements from the CMI specification that are commonly implemented; renames some data elements taken from the CMI specification to clarify their intended meaning; modifies the data types of data elements taken from the CMI specification to reflect ISO standard data types and internationalization requirements; removes some organizational structures used in the CMI specification to group data elements that are specific to the AICC community of practice and not generally applicable; and introduces some data elements not present in the CMI specification to correct known technical deficiencies in data elements taken from that specification<br />\n
          There is widespread acknowledgment that the data model for content object communication defined in the AICC “Computer Managed Instruction (CMI) Guidelines for Interoperability”, version 3.5 [B1], has broad applicability to systems used for learning management. The purpose of this standard is to build consensus around, resolve ambiguities in, and correct defects in the AICC data model for the data exchanged between learning-related content objects and an RTS used to support learning management.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Learning Technology--Data Model for Content Object Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95724 …}
    #channels: Doctrine\ORM\PersistentCollection {#95730 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95728 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95716 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95712
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1680645600 {#95713
      date: 2023-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649973600 {#95714
      date: 2022-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1484.11.1"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#95718 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95720 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.62 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95715
    #id: 12623
    #code: "IEEE00010324"
    #attributes: Doctrine\ORM\PersistentCollection {#95732 …}
    #variants: Doctrine\ORM\PersistentCollection {#95734 …}
    #options: Doctrine\ORM\PersistentCollection {#95738 …}
    #associations: Doctrine\ORM\PersistentCollection {#95736 …}
    #createdAt: DateTime @1751040554 {#95710
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95711
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95722 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95715}
        #id: 45501
        #name: "IEEE 1484.11.1:2022"
        #slug: "ieee-1484-11-1-2022-ieee00010324-244278"
        #description: """
          Revision Standard - Active.<br />\n
          A data model to support the interchange of data elements and their values between a content object and a runtime service (RTS) is described in this standard. This standard is based on a current industry practice called “computer managed instruction” (CMI). The work on which this standard is based was developed to support a client–server environment in which a learning technology system, generically called a “learning management system” (LMS), delivers digital content, called “content objects,” to learners. The data model supports learner data and preferences; interactions; objectives; content-object entry, exit, and status information; time parameters; and scores.<br />\n
          \t\t\t\t<br />\n
          This standard describes a data model to support the interchange of agreed-upon data elements and their values between a learning-related content object and a runtime service (RTS) used to support learning management. This standard does not specify the means of communication between a content object and an RTS nor how any component of a learning environment shall behave in response to receiving data in the form specified. This standard is based on a related data model defined in “Computer Managed Instruction (CMI) Guidelines For Interoperability,” version 3.5 [B1] by the Aviation Industry CBT Committee (AICC). To balance the need to support existing implementations with the need to make technical corrections and support emerging practice, this standard selectively includes those data elements from the CMI specification that are commonly implemented; renames some data elements taken from the CMI specification to clarify their intended meaning; modifies the data types of data elements taken from the CMI specification to reflect ISO standard data types and internationalization requirements; removes some organizational structures used in the CMI specification to group data elements that are specific to the AICC community of practice and not generally applicable; and introduces some data elements not present in the CMI specification to correct known technical deficiencies in data elements taken from that specification<br />\n
          There is widespread acknowledgment that the data model for content object communication defined in the AICC “Computer Managed Instruction (CMI) Guidelines for Interoperability”, version 3.5 [B1], has broad applicability to systems used for learning management. The purpose of this standard is to build consensus around, resolve ambiguities in, and correct defects in the AICC data model for the data exchanged between learning-related content objects and an RTS used to support learning management.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Learning Technology--Data Model for Content Object Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95724 …}
    #channels: Doctrine\ORM\PersistentCollection {#95730 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95728 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95716 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95712
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1680645600 {#95713
      date: 2023-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649973600 {#95714
      date: 2022-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1484.11.1"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#95718 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95720 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#97666
  +product: App\Entity\Product\Product {#95715
    #id: 12623
    #code: "IEEE00010324"
    #attributes: Doctrine\ORM\PersistentCollection {#95732 …}
    #variants: Doctrine\ORM\PersistentCollection {#95734 …}
    #options: Doctrine\ORM\PersistentCollection {#95738 …}
    #associations: Doctrine\ORM\PersistentCollection {#95736 …}
    #createdAt: DateTime @1751040554 {#95710
      date: 2025-06-27 18:09:14.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95711
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95722 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97573
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95715}
        #id: 45501
        #name: "IEEE 1484.11.1:2022"
        #slug: "ieee-1484-11-1-2022-ieee00010324-244278"
        #description: """
          Revision Standard - Active.<br />\n
          A data model to support the interchange of data elements and their values between a content object and a runtime service (RTS) is described in this standard. This standard is based on a current industry practice called “computer managed instruction” (CMI). The work on which this standard is based was developed to support a client–server environment in which a learning technology system, generically called a “learning management system” (LMS), delivers digital content, called “content objects,” to learners. The data model supports learner data and preferences; interactions; objectives; content-object entry, exit, and status information; time parameters; and scores.<br />\n
          \t\t\t\t<br />\n
          This standard describes a data model to support the interchange of agreed-upon data elements and their values between a learning-related content object and a runtime service (RTS) used to support learning management. This standard does not specify the means of communication between a content object and an RTS nor how any component of a learning environment shall behave in response to receiving data in the form specified. This standard is based on a related data model defined in “Computer Managed Instruction (CMI) Guidelines For Interoperability,” version 3.5 [B1] by the Aviation Industry CBT Committee (AICC). To balance the need to support existing implementations with the need to make technical corrections and support emerging practice, this standard selectively includes those data elements from the CMI specification that are commonly implemented; renames some data elements taken from the CMI specification to clarify their intended meaning; modifies the data types of data elements taken from the CMI specification to reflect ISO standard data types and internationalization requirements; removes some organizational structures used in the CMI specification to group data elements that are specific to the AICC community of practice and not generally applicable; and introduces some data elements not present in the CMI specification to correct known technical deficiencies in data elements taken from that specification<br />\n
          There is widespread acknowledgment that the data model for content object communication defined in the AICC “Computer Managed Instruction (CMI) Guidelines for Interoperability”, version 3.5 [B1], has broad applicability to systems used for learning management. The purpose of this standard is to build consensus around, resolve ambiguities in, and correct defects in the AICC data model for the data exchanged between learning-related content objects and an RTS used to support learning management.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Learning Technology--Data Model for Content Object Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95724 …}
    #channels: Doctrine\ORM\PersistentCollection {#95730 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95726 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95728 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95716 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95712
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1680645600 {#95713
      date: 2023-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649973600 {#95714
      date: 2022-04-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1484.11.1"
    -bookCollection: ""
    -pageCount: 52
    -documents: Doctrine\ORM\PersistentCollection {#95718 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95720 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.61 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95745
    #id: 12624
    #code: "IEEE00010325"
    #attributes: Doctrine\ORM\PersistentCollection {#95762 …}
    #variants: Doctrine\ORM\PersistentCollection {#95764 …}
    #options: Doctrine\ORM\PersistentCollection {#95768 …}
    #associations: Doctrine\ORM\PersistentCollection {#95766 …}
    #createdAt: DateTime @1751040555 {#95740
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95741
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97825
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95745}
        #id: 45505
        #name: "IEEE 1138:2021"
        #slug: "ieee-1138-2021-ieee00010325-244279"
        #description: """
          Revision Standard - Active.<br />\n
          The performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW) are covered in this standard. Functional requirements such as electrical, mechanical, optical fiber, environmental, and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests are also covered.<br />\n
          \t\t\t\t<br />\n
          This standard covers the performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW). An OPGW cable has the dual performance functions of a ground wire with telecommunications capabilities. This standard includes functional requirements, such as electrical, mechanical, optical fiber, environmental and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests. This standard is not intended to supersede any established safety rules, codes, regulations, or practices associated with the use of OPGW cables. It is the responsibility of the user of this standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations prior to use.<br />\n
          This standard covers the construction, mechanical and electrical performance, acceptance criteria, and test requirements for overhead ground wire (OPGW) designed to be located primarily on overhead power utility facilities. The standard provides performance and testing requirements that insure within the guidelines of this standard that the mechanical and electrical capabilities of the cable and cable components properly maintain mechanical integrity, optical fiber integrity, and optical transmission.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Testing and Performance of Optical Ground Wire (OPGW) for use on Electric Utility Power Lines"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95754 …}
    #channels: Doctrine\ORM\PersistentCollection {#95760 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95756 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95758 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95746 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95742
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642546800 {#95743
      date: 2022-01-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1636066800 {#95744
      date: 2021-11-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1138"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95748 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95750 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#97805
  +product: App\Entity\Product\Product {#95745
    #id: 12624
    #code: "IEEE00010325"
    #attributes: Doctrine\ORM\PersistentCollection {#95762 …}
    #variants: Doctrine\ORM\PersistentCollection {#95764 …}
    #options: Doctrine\ORM\PersistentCollection {#95768 …}
    #associations: Doctrine\ORM\PersistentCollection {#95766 …}
    #createdAt: DateTime @1751040555 {#95740
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95741
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97825
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95745}
        #id: 45505
        #name: "IEEE 1138:2021"
        #slug: "ieee-1138-2021-ieee00010325-244279"
        #description: """
          Revision Standard - Active.<br />\n
          The performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW) are covered in this standard. Functional requirements such as electrical, mechanical, optical fiber, environmental, and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests are also covered.<br />\n
          \t\t\t\t<br />\n
          This standard covers the performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW). An OPGW cable has the dual performance functions of a ground wire with telecommunications capabilities. This standard includes functional requirements, such as electrical, mechanical, optical fiber, environmental and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests. This standard is not intended to supersede any established safety rules, codes, regulations, or practices associated with the use of OPGW cables. It is the responsibility of the user of this standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations prior to use.<br />\n
          This standard covers the construction, mechanical and electrical performance, acceptance criteria, and test requirements for overhead ground wire (OPGW) designed to be located primarily on overhead power utility facilities. The standard provides performance and testing requirements that insure within the guidelines of this standard that the mechanical and electrical capabilities of the cable and cable components properly maintain mechanical integrity, optical fiber integrity, and optical transmission.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Testing and Performance of Optical Ground Wire (OPGW) for use on Electric Utility Power Lines"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95754 …}
    #channels: Doctrine\ORM\PersistentCollection {#95760 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95756 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95758 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95746 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95742
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642546800 {#95743
      date: 2022-01-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1636066800 {#95744
      date: 2021-11-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1138"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95748 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95750 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95745
    #id: 12624
    #code: "IEEE00010325"
    #attributes: Doctrine\ORM\PersistentCollection {#95762 …}
    #variants: Doctrine\ORM\PersistentCollection {#95764 …}
    #options: Doctrine\ORM\PersistentCollection {#95768 …}
    #associations: Doctrine\ORM\PersistentCollection {#95766 …}
    #createdAt: DateTime @1751040555 {#95740
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95741
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97825
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95745}
        #id: 45505
        #name: "IEEE 1138:2021"
        #slug: "ieee-1138-2021-ieee00010325-244279"
        #description: """
          Revision Standard - Active.<br />\n
          The performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW) are covered in this standard. Functional requirements such as electrical, mechanical, optical fiber, environmental, and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests are also covered.<br />\n
          \t\t\t\t<br />\n
          This standard covers the performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW). An OPGW cable has the dual performance functions of a ground wire with telecommunications capabilities. This standard includes functional requirements, such as electrical, mechanical, optical fiber, environmental and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests. This standard is not intended to supersede any established safety rules, codes, regulations, or practices associated with the use of OPGW cables. It is the responsibility of the user of this standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations prior to use.<br />\n
          This standard covers the construction, mechanical and electrical performance, acceptance criteria, and test requirements for overhead ground wire (OPGW) designed to be located primarily on overhead power utility facilities. The standard provides performance and testing requirements that insure within the guidelines of this standard that the mechanical and electrical capabilities of the cable and cable components properly maintain mechanical integrity, optical fiber integrity, and optical transmission.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Testing and Performance of Optical Ground Wire (OPGW) for use on Electric Utility Power Lines"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95754 …}
    #channels: Doctrine\ORM\PersistentCollection {#95760 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95756 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95758 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95746 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95742
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642546800 {#95743
      date: 2022-01-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1636066800 {#95744
      date: 2021-11-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1138"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95748 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95750 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#97843
  +product: App\Entity\Product\Product {#95745
    #id: 12624
    #code: "IEEE00010325"
    #attributes: Doctrine\ORM\PersistentCollection {#95762 …}
    #variants: Doctrine\ORM\PersistentCollection {#95764 …}
    #options: Doctrine\ORM\PersistentCollection {#95768 …}
    #associations: Doctrine\ORM\PersistentCollection {#95766 …}
    #createdAt: DateTime @1751040555 {#95740
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95741
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97825
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95745}
        #id: 45505
        #name: "IEEE 1138:2021"
        #slug: "ieee-1138-2021-ieee00010325-244279"
        #description: """
          Revision Standard - Active.<br />\n
          The performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW) are covered in this standard. Functional requirements such as electrical, mechanical, optical fiber, environmental, and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests are also covered.<br />\n
          \t\t\t\t<br />\n
          This standard covers the performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW). An OPGW cable has the dual performance functions of a ground wire with telecommunications capabilities. This standard includes functional requirements, such as electrical, mechanical, optical fiber, environmental and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests. This standard is not intended to supersede any established safety rules, codes, regulations, or practices associated with the use of OPGW cables. It is the responsibility of the user of this standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations prior to use.<br />\n
          This standard covers the construction, mechanical and electrical performance, acceptance criteria, and test requirements for overhead ground wire (OPGW) designed to be located primarily on overhead power utility facilities. The standard provides performance and testing requirements that insure within the guidelines of this standard that the mechanical and electrical capabilities of the cable and cable components properly maintain mechanical integrity, optical fiber integrity, and optical transmission.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Testing and Performance of Optical Ground Wire (OPGW) for use on Electric Utility Power Lines"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95754 …}
    #channels: Doctrine\ORM\PersistentCollection {#95760 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95756 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95758 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95746 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95742
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642546800 {#95743
      date: 2022-01-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1636066800 {#95744
      date: 2021-11-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1138"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95748 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95750 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.82 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95745
    #id: 12624
    #code: "IEEE00010325"
    #attributes: Doctrine\ORM\PersistentCollection {#95762 …}
    #variants: Doctrine\ORM\PersistentCollection {#95764 …}
    #options: Doctrine\ORM\PersistentCollection {#95768 …}
    #associations: Doctrine\ORM\PersistentCollection {#95766 …}
    #createdAt: DateTime @1751040555 {#95740
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95741
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97825
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95745}
        #id: 45505
        #name: "IEEE 1138:2021"
        #slug: "ieee-1138-2021-ieee00010325-244279"
        #description: """
          Revision Standard - Active.<br />\n
          The performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW) are covered in this standard. Functional requirements such as electrical, mechanical, optical fiber, environmental, and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests are also covered.<br />\n
          \t\t\t\t<br />\n
          This standard covers the performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW). An OPGW cable has the dual performance functions of a ground wire with telecommunications capabilities. This standard includes functional requirements, such as electrical, mechanical, optical fiber, environmental and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests. This standard is not intended to supersede any established safety rules, codes, regulations, or practices associated with the use of OPGW cables. It is the responsibility of the user of this standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations prior to use.<br />\n
          This standard covers the construction, mechanical and electrical performance, acceptance criteria, and test requirements for overhead ground wire (OPGW) designed to be located primarily on overhead power utility facilities. The standard provides performance and testing requirements that insure within the guidelines of this standard that the mechanical and electrical capabilities of the cable and cable components properly maintain mechanical integrity, optical fiber integrity, and optical transmission.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Testing and Performance of Optical Ground Wire (OPGW) for use on Electric Utility Power Lines"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95754 …}
    #channels: Doctrine\ORM\PersistentCollection {#95760 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95756 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95758 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95746 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95742
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642546800 {#95743
      date: 2022-01-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1636066800 {#95744
      date: 2021-11-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1138"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95748 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95750 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#97917
  +product: App\Entity\Product\Product {#95745
    #id: 12624
    #code: "IEEE00010325"
    #attributes: Doctrine\ORM\PersistentCollection {#95762 …}
    #variants: Doctrine\ORM\PersistentCollection {#95764 …}
    #options: Doctrine\ORM\PersistentCollection {#95768 …}
    #associations: Doctrine\ORM\PersistentCollection {#95766 …}
    #createdAt: DateTime @1751040555 {#95740
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95741
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97825
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95745}
        #id: 45505
        #name: "IEEE 1138:2021"
        #slug: "ieee-1138-2021-ieee00010325-244279"
        #description: """
          Revision Standard - Active.<br />\n
          The performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW) are covered in this standard. Functional requirements such as electrical, mechanical, optical fiber, environmental, and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests are also covered.<br />\n
          \t\t\t\t<br />\n
          This standard covers the performance, test requirements, procedures, and acceptance criteria for a transmission line overhead ground wire (a.k.a. shield wire, static wire, earth wire, skywire) with optical fibers commonly known as optical ground wire (OPGW). An OPGW cable has the dual performance functions of a ground wire with telecommunications capabilities. This standard includes functional requirements, such as electrical, mechanical, optical fiber, environmental and packaging, and test requirements related to design, installation, in-service, and maintenance, including routine tests. This standard is not intended to supersede any established safety rules, codes, regulations, or practices associated with the use of OPGW cables. It is the responsibility of the user of this standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations prior to use.<br />\n
          This standard covers the construction, mechanical and electrical performance, acceptance criteria, and test requirements for overhead ground wire (OPGW) designed to be located primarily on overhead power utility facilities. The standard provides performance and testing requirements that insure within the guidelines of this standard that the mechanical and electrical capabilities of the cable and cable components properly maintain mechanical integrity, optical fiber integrity, and optical transmission.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Testing and Performance of Optical Ground Wire (OPGW) for use on Electric Utility Power Lines"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95754 …}
    #channels: Doctrine\ORM\PersistentCollection {#95760 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95756 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95758 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95746 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95742
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1642546800 {#95743
      date: 2022-01-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1636066800 {#95744
      date: 2021-11-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1138"
    -bookCollection: ""
    -pageCount: 54
    -documents: Doctrine\ORM\PersistentCollection {#95748 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95750 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.26 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95776
    #id: 12625
    #code: "IEEE00010326"
    #attributes: Doctrine\ORM\PersistentCollection {#95793 …}
    #variants: Doctrine\ORM\PersistentCollection {#95795 …}
    #options: Doctrine\ORM\PersistentCollection {#95799 …}
    #associations: Doctrine\ORM\PersistentCollection {#95797 …}
    #createdAt: DateTime @1751040555 {#95770
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95771
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95783 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98076
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95776}
        #id: 45509
        #name: "IEEE 820:2021"
        #slug: "ieee-820-2021-ieee00010326-244280"
        #description: """
          Revision Standard - Active.<br />\n
          Common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard covers the general parameters and characteristics associated with telephone loops from the subscriber signaling and analog voice frequency interface to the local Class 5 switch interface. It includes only those business and residential lines in the North American public switched network where no special performance requirements are involved. This standard provides common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods.<br />\n
          The purpose of this standard is to describe quantitatively the performance characteristics of telephone loops and indicate current acceptable performance criteria.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Telephone Loop Performance Characteristics"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95785 …}
    #channels: Doctrine\ORM\PersistentCollection {#95791 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95787 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95777 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1666130400 {#95773
      date: 2022-10-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649800800 {#95774
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1649800800 {#95775
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "820"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#95779 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95781 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#98056
  +product: App\Entity\Product\Product {#95776
    #id: 12625
    #code: "IEEE00010326"
    #attributes: Doctrine\ORM\PersistentCollection {#95793 …}
    #variants: Doctrine\ORM\PersistentCollection {#95795 …}
    #options: Doctrine\ORM\PersistentCollection {#95799 …}
    #associations: Doctrine\ORM\PersistentCollection {#95797 …}
    #createdAt: DateTime @1751040555 {#95770
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95771
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95783 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98076
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95776}
        #id: 45509
        #name: "IEEE 820:2021"
        #slug: "ieee-820-2021-ieee00010326-244280"
        #description: """
          Revision Standard - Active.<br />\n
          Common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard covers the general parameters and characteristics associated with telephone loops from the subscriber signaling and analog voice frequency interface to the local Class 5 switch interface. It includes only those business and residential lines in the North American public switched network where no special performance requirements are involved. This standard provides common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods.<br />\n
          The purpose of this standard is to describe quantitatively the performance characteristics of telephone loops and indicate current acceptable performance criteria.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Telephone Loop Performance Characteristics"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95785 …}
    #channels: Doctrine\ORM\PersistentCollection {#95791 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95787 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95777 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1666130400 {#95773
      date: 2022-10-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649800800 {#95774
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1649800800 {#95775
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "820"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#95779 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95781 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95776
    #id: 12625
    #code: "IEEE00010326"
    #attributes: Doctrine\ORM\PersistentCollection {#95793 …}
    #variants: Doctrine\ORM\PersistentCollection {#95795 …}
    #options: Doctrine\ORM\PersistentCollection {#95799 …}
    #associations: Doctrine\ORM\PersistentCollection {#95797 …}
    #createdAt: DateTime @1751040555 {#95770
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95771
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95783 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98076
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95776}
        #id: 45509
        #name: "IEEE 820:2021"
        #slug: "ieee-820-2021-ieee00010326-244280"
        #description: """
          Revision Standard - Active.<br />\n
          Common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard covers the general parameters and characteristics associated with telephone loops from the subscriber signaling and analog voice frequency interface to the local Class 5 switch interface. It includes only those business and residential lines in the North American public switched network where no special performance requirements are involved. This standard provides common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods.<br />\n
          The purpose of this standard is to describe quantitatively the performance characteristics of telephone loops and indicate current acceptable performance criteria.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Telephone Loop Performance Characteristics"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95785 …}
    #channels: Doctrine\ORM\PersistentCollection {#95791 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95787 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95777 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1666130400 {#95773
      date: 2022-10-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649800800 {#95774
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1649800800 {#95775
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "820"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#95779 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95781 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#98094
  +product: App\Entity\Product\Product {#95776
    #id: 12625
    #code: "IEEE00010326"
    #attributes: Doctrine\ORM\PersistentCollection {#95793 …}
    #variants: Doctrine\ORM\PersistentCollection {#95795 …}
    #options: Doctrine\ORM\PersistentCollection {#95799 …}
    #associations: Doctrine\ORM\PersistentCollection {#95797 …}
    #createdAt: DateTime @1751040555 {#95770
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95771
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95783 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98076
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95776}
        #id: 45509
        #name: "IEEE 820:2021"
        #slug: "ieee-820-2021-ieee00010326-244280"
        #description: """
          Revision Standard - Active.<br />\n
          Common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard covers the general parameters and characteristics associated with telephone loops from the subscriber signaling and analog voice frequency interface to the local Class 5 switch interface. It includes only those business and residential lines in the North American public switched network where no special performance requirements are involved. This standard provides common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods.<br />\n
          The purpose of this standard is to describe quantitatively the performance characteristics of telephone loops and indicate current acceptable performance criteria.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Telephone Loop Performance Characteristics"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95785 …}
    #channels: Doctrine\ORM\PersistentCollection {#95791 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95787 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95777 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1666130400 {#95773
      date: 2022-10-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649800800 {#95774
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1649800800 {#95775
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "820"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#95779 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95781 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.61 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95776
    #id: 12625
    #code: "IEEE00010326"
    #attributes: Doctrine\ORM\PersistentCollection {#95793 …}
    #variants: Doctrine\ORM\PersistentCollection {#95795 …}
    #options: Doctrine\ORM\PersistentCollection {#95799 …}
    #associations: Doctrine\ORM\PersistentCollection {#95797 …}
    #createdAt: DateTime @1751040555 {#95770
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95771
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95783 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98076
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95776}
        #id: 45509
        #name: "IEEE 820:2021"
        #slug: "ieee-820-2021-ieee00010326-244280"
        #description: """
          Revision Standard - Active.<br />\n
          Common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard covers the general parameters and characteristics associated with telephone loops from the subscriber signaling and analog voice frequency interface to the local Class 5 switch interface. It includes only those business and residential lines in the North American public switched network where no special performance requirements are involved. This standard provides common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods.<br />\n
          The purpose of this standard is to describe quantitatively the performance characteristics of telephone loops and indicate current acceptable performance criteria.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Telephone Loop Performance Characteristics"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95785 …}
    #channels: Doctrine\ORM\PersistentCollection {#95791 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95787 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95777 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1666130400 {#95773
      date: 2022-10-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649800800 {#95774
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1649800800 {#95775
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "820"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#95779 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95781 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#98168
  +product: App\Entity\Product\Product {#95776
    #id: 12625
    #code: "IEEE00010326"
    #attributes: Doctrine\ORM\PersistentCollection {#95793 …}
    #variants: Doctrine\ORM\PersistentCollection {#95795 …}
    #options: Doctrine\ORM\PersistentCollection {#95799 …}
    #associations: Doctrine\ORM\PersistentCollection {#95797 …}
    #createdAt: DateTime @1751040555 {#95770
      date: 2025-06-27 18:09:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95771
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95783 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98076
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95776}
        #id: 45509
        #name: "IEEE 820:2021"
        #slug: "ieee-820-2021-ieee00010326-244280"
        #description: """
          Revision Standard - Active.<br />\n
          Common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods are provided in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard covers the general parameters and characteristics associated with telephone loops from the subscriber signaling and analog voice frequency interface to the local Class 5 switch interface. It includes only those business and residential lines in the North American public switched network where no special performance requirements are involved. This standard provides common denominators for subscriber line performance, independent of facility types, construction processes or equipment, and circuit provisioning methods.<br />\n
          The purpose of this standard is to describe quantitatively the performance characteristics of telephone loops and indicate current acceptable performance criteria.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard Telephone Loop Performance Characteristics"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95785 …}
    #channels: Doctrine\ORM\PersistentCollection {#95791 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95787 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95777 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95772
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1666130400 {#95773
      date: 2022-10-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1649800800 {#95774
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1649800800 {#95775
      date: 2022-04-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "820"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#95779 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95781 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.56 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95806
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95823 …}
    #variants: Doctrine\ORM\PersistentCollection {#95825 …}
    #options: Doctrine\ORM\PersistentCollection {#95829 …}
    #associations: Doctrine\ORM\PersistentCollection {#95827 …}
    #createdAt: DateTime @1751040556 {#95801
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95802
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95813 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95806}
        #id: 45513
        #name: "IEEE 1616:2021"
        #slug: "ieee-1616-2021-ieee00010329-244281"
        #description: """
          Revision Standard - Active.<br />\n
          Export data related to motor vehicle pre-defined events in usage history is collected, recorded, stored, and exported by motor vehicle event data recorders (MVEDRs). A protocol for MVEDR output data compatibility and export protocols of MVEDR data elements is defined by this standard. A motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol is defined for safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC) and establishing a chain of custody link. This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing.<br />\n
          \t\t\t\t<br />\n
          Motor vehicle event data recorders (MVEDRs) collect, record, store, and export data related to motor vehicle pre-defined events in usage history. This standard defines a protocol for MVEDR output data compatibility and export protocols of MVEDR data elements. This standard does not prescribe which specific data elements shall be recorded, but instead provides a data dictionary of data attributes. This standard also defines a means of maintaining data security on the vehicle via a motor vehicle diagnostic link connector lockout apparatus (MVEDRCLA) by securing the vehicle output diagnostic link connector (DLC). This standard does not prescribe data security within the vehicle electronic control units (ECUs) or within the intra-vehicle communication and/or diagnostic networks; it instead defines ways and means to permit uniform but controlled access of electronic scan tools to the DLC for legitimate vehicle emissions status, maintenance, and/or repair. This standard also defines a motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol of safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC). This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing. This standard does not directly address related issues with regard to human health or human safety. It is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public roadways, whether offered as original or aftermarket equipment, whether stand-alone or integrated within the vehicle.<br />\n
          Many light-duty motor vehicles, and increasing numbers of heavy commercial vehicles, are equipped with some form of MVEDR. These systems, which are designed and produced by individual motor vehicle manufacturers and component suppliers, are diverse in function, and proprietary in nature, however, the SAE J1962 [B118]2 (ISO 15031-3:2004 [B55]) vehicle DLC has a common design and pinout, and is thus universally used to access event data recorder information. Data access via the DLC can be accomplished by using scan tools or microcomputers and network interfaces. This same DLC and network interface is also used for re-calibrating electronic control units on a vehicle. Such ECU applications can include restraint controls, engine controls, stability controls, braking controls, etc. This standard defines a protocol to protect against misuse of electronic tools which use the DLC to erase, modify, or tamper with electronic controller or odometer readings, or to improperly download data. Implementation of MVEDRCLA provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA that will act to prevent vehicle tampering, which can include odometer fraud, illegal calibrations leading to emissions violations, and theft of personal data. Adoption of this standard will therefore make the common MVEDR/DLC data more secure and credible while still permitting accessibility to legitimate end users. The continuing implementation of MVEDR systems provides an opportunity to voluntarily standardize data output and retrieval protocols to facilitate analysis and promote compatibility of MVEDR data. Adoption of the standard will therefore make MVEDR data more accessible and useful to end users.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Motor Vehicle Event Data Recorder (MVEDR)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95815 …}
    #channels: Doctrine\ORM\PersistentCollection {#95821 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95817 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95819 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95803
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95804
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95805
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 184
    -documents: Doctrine\ORM\PersistentCollection {#95809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95811 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#98307
  +product: App\Entity\Product\Product {#95806
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95823 …}
    #variants: Doctrine\ORM\PersistentCollection {#95825 …}
    #options: Doctrine\ORM\PersistentCollection {#95829 …}
    #associations: Doctrine\ORM\PersistentCollection {#95827 …}
    #createdAt: DateTime @1751040556 {#95801
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95802
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95813 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95806}
        #id: 45513
        #name: "IEEE 1616:2021"
        #slug: "ieee-1616-2021-ieee00010329-244281"
        #description: """
          Revision Standard - Active.<br />\n
          Export data related to motor vehicle pre-defined events in usage history is collected, recorded, stored, and exported by motor vehicle event data recorders (MVEDRs). A protocol for MVEDR output data compatibility and export protocols of MVEDR data elements is defined by this standard. A motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol is defined for safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC) and establishing a chain of custody link. This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing.<br />\n
          \t\t\t\t<br />\n
          Motor vehicle event data recorders (MVEDRs) collect, record, store, and export data related to motor vehicle pre-defined events in usage history. This standard defines a protocol for MVEDR output data compatibility and export protocols of MVEDR data elements. This standard does not prescribe which specific data elements shall be recorded, but instead provides a data dictionary of data attributes. This standard also defines a means of maintaining data security on the vehicle via a motor vehicle diagnostic link connector lockout apparatus (MVEDRCLA) by securing the vehicle output diagnostic link connector (DLC). This standard does not prescribe data security within the vehicle electronic control units (ECUs) or within the intra-vehicle communication and/or diagnostic networks; it instead defines ways and means to permit uniform but controlled access of electronic scan tools to the DLC for legitimate vehicle emissions status, maintenance, and/or repair. This standard also defines a motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol of safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC). This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing. This standard does not directly address related issues with regard to human health or human safety. It is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public roadways, whether offered as original or aftermarket equipment, whether stand-alone or integrated within the vehicle.<br />\n
          Many light-duty motor vehicles, and increasing numbers of heavy commercial vehicles, are equipped with some form of MVEDR. These systems, which are designed and produced by individual motor vehicle manufacturers and component suppliers, are diverse in function, and proprietary in nature, however, the SAE J1962 [B118]2 (ISO 15031-3:2004 [B55]) vehicle DLC has a common design and pinout, and is thus universally used to access event data recorder information. Data access via the DLC can be accomplished by using scan tools or microcomputers and network interfaces. This same DLC and network interface is also used for re-calibrating electronic control units on a vehicle. Such ECU applications can include restraint controls, engine controls, stability controls, braking controls, etc. This standard defines a protocol to protect against misuse of electronic tools which use the DLC to erase, modify, or tamper with electronic controller or odometer readings, or to improperly download data. Implementation of MVEDRCLA provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA that will act to prevent vehicle tampering, which can include odometer fraud, illegal calibrations leading to emissions violations, and theft of personal data. Adoption of this standard will therefore make the common MVEDR/DLC data more secure and credible while still permitting accessibility to legitimate end users. The continuing implementation of MVEDR systems provides an opportunity to voluntarily standardize data output and retrieval protocols to facilitate analysis and promote compatibility of MVEDR data. Adoption of the standard will therefore make MVEDR data more accessible and useful to end users.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Motor Vehicle Event Data Recorder (MVEDR)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95815 …}
    #channels: Doctrine\ORM\PersistentCollection {#95821 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95817 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95819 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95803
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95804
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95805
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 184
    -documents: Doctrine\ORM\PersistentCollection {#95809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95811 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95806
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95823 …}
    #variants: Doctrine\ORM\PersistentCollection {#95825 …}
    #options: Doctrine\ORM\PersistentCollection {#95829 …}
    #associations: Doctrine\ORM\PersistentCollection {#95827 …}
    #createdAt: DateTime @1751040556 {#95801
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95802
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95813 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95806}
        #id: 45513
        #name: "IEEE 1616:2021"
        #slug: "ieee-1616-2021-ieee00010329-244281"
        #description: """
          Revision Standard - Active.<br />\n
          Export data related to motor vehicle pre-defined events in usage history is collected, recorded, stored, and exported by motor vehicle event data recorders (MVEDRs). A protocol for MVEDR output data compatibility and export protocols of MVEDR data elements is defined by this standard. A motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol is defined for safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC) and establishing a chain of custody link. This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing.<br />\n
          \t\t\t\t<br />\n
          Motor vehicle event data recorders (MVEDRs) collect, record, store, and export data related to motor vehicle pre-defined events in usage history. This standard defines a protocol for MVEDR output data compatibility and export protocols of MVEDR data elements. This standard does not prescribe which specific data elements shall be recorded, but instead provides a data dictionary of data attributes. This standard also defines a means of maintaining data security on the vehicle via a motor vehicle diagnostic link connector lockout apparatus (MVEDRCLA) by securing the vehicle output diagnostic link connector (DLC). This standard does not prescribe data security within the vehicle electronic control units (ECUs) or within the intra-vehicle communication and/or diagnostic networks; it instead defines ways and means to permit uniform but controlled access of electronic scan tools to the DLC for legitimate vehicle emissions status, maintenance, and/or repair. This standard also defines a motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol of safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC). This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing. This standard does not directly address related issues with regard to human health or human safety. It is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public roadways, whether offered as original or aftermarket equipment, whether stand-alone or integrated within the vehicle.<br />\n
          Many light-duty motor vehicles, and increasing numbers of heavy commercial vehicles, are equipped with some form of MVEDR. These systems, which are designed and produced by individual motor vehicle manufacturers and component suppliers, are diverse in function, and proprietary in nature, however, the SAE J1962 [B118]2 (ISO 15031-3:2004 [B55]) vehicle DLC has a common design and pinout, and is thus universally used to access event data recorder information. Data access via the DLC can be accomplished by using scan tools or microcomputers and network interfaces. This same DLC and network interface is also used for re-calibrating electronic control units on a vehicle. Such ECU applications can include restraint controls, engine controls, stability controls, braking controls, etc. This standard defines a protocol to protect against misuse of electronic tools which use the DLC to erase, modify, or tamper with electronic controller or odometer readings, or to improperly download data. Implementation of MVEDRCLA provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA that will act to prevent vehicle tampering, which can include odometer fraud, illegal calibrations leading to emissions violations, and theft of personal data. Adoption of this standard will therefore make the common MVEDR/DLC data more secure and credible while still permitting accessibility to legitimate end users. The continuing implementation of MVEDR systems provides an opportunity to voluntarily standardize data output and retrieval protocols to facilitate analysis and promote compatibility of MVEDR data. Adoption of the standard will therefore make MVEDR data more accessible and useful to end users.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Motor Vehicle Event Data Recorder (MVEDR)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95815 …}
    #channels: Doctrine\ORM\PersistentCollection {#95821 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95817 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95819 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95803
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95804
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95805
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 184
    -documents: Doctrine\ORM\PersistentCollection {#95809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95811 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#98345
  +product: App\Entity\Product\Product {#95806
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95823 …}
    #variants: Doctrine\ORM\PersistentCollection {#95825 …}
    #options: Doctrine\ORM\PersistentCollection {#95829 …}
    #associations: Doctrine\ORM\PersistentCollection {#95827 …}
    #createdAt: DateTime @1751040556 {#95801
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95802
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95813 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95806}
        #id: 45513
        #name: "IEEE 1616:2021"
        #slug: "ieee-1616-2021-ieee00010329-244281"
        #description: """
          Revision Standard - Active.<br />\n
          Export data related to motor vehicle pre-defined events in usage history is collected, recorded, stored, and exported by motor vehicle event data recorders (MVEDRs). A protocol for MVEDR output data compatibility and export protocols of MVEDR data elements is defined by this standard. A motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol is defined for safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC) and establishing a chain of custody link. This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing.<br />\n
          \t\t\t\t<br />\n
          Motor vehicle event data recorders (MVEDRs) collect, record, store, and export data related to motor vehicle pre-defined events in usage history. This standard defines a protocol for MVEDR output data compatibility and export protocols of MVEDR data elements. This standard does not prescribe which specific data elements shall be recorded, but instead provides a data dictionary of data attributes. This standard also defines a means of maintaining data security on the vehicle via a motor vehicle diagnostic link connector lockout apparatus (MVEDRCLA) by securing the vehicle output diagnostic link connector (DLC). This standard does not prescribe data security within the vehicle electronic control units (ECUs) or within the intra-vehicle communication and/or diagnostic networks; it instead defines ways and means to permit uniform but controlled access of electronic scan tools to the DLC for legitimate vehicle emissions status, maintenance, and/or repair. This standard also defines a motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol of safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC). This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing. This standard does not directly address related issues with regard to human health or human safety. It is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public roadways, whether offered as original or aftermarket equipment, whether stand-alone or integrated within the vehicle.<br />\n
          Many light-duty motor vehicles, and increasing numbers of heavy commercial vehicles, are equipped with some form of MVEDR. These systems, which are designed and produced by individual motor vehicle manufacturers and component suppliers, are diverse in function, and proprietary in nature, however, the SAE J1962 [B118]2 (ISO 15031-3:2004 [B55]) vehicle DLC has a common design and pinout, and is thus universally used to access event data recorder information. Data access via the DLC can be accomplished by using scan tools or microcomputers and network interfaces. This same DLC and network interface is also used for re-calibrating electronic control units on a vehicle. Such ECU applications can include restraint controls, engine controls, stability controls, braking controls, etc. This standard defines a protocol to protect against misuse of electronic tools which use the DLC to erase, modify, or tamper with electronic controller or odometer readings, or to improperly download data. Implementation of MVEDRCLA provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA that will act to prevent vehicle tampering, which can include odometer fraud, illegal calibrations leading to emissions violations, and theft of personal data. Adoption of this standard will therefore make the common MVEDR/DLC data more secure and credible while still permitting accessibility to legitimate end users. The continuing implementation of MVEDR systems provides an opportunity to voluntarily standardize data output and retrieval protocols to facilitate analysis and promote compatibility of MVEDR data. Adoption of the standard will therefore make MVEDR data more accessible and useful to end users.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Motor Vehicle Event Data Recorder (MVEDR)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95815 …}
    #channels: Doctrine\ORM\PersistentCollection {#95821 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95817 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95819 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95803
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95804
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95805
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 184
    -documents: Doctrine\ORM\PersistentCollection {#95809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95811 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.64 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95806
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95823 …}
    #variants: Doctrine\ORM\PersistentCollection {#95825 …}
    #options: Doctrine\ORM\PersistentCollection {#95829 …}
    #associations: Doctrine\ORM\PersistentCollection {#95827 …}
    #createdAt: DateTime @1751040556 {#95801
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95802
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95813 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95806}
        #id: 45513
        #name: "IEEE 1616:2021"
        #slug: "ieee-1616-2021-ieee00010329-244281"
        #description: """
          Revision Standard - Active.<br />\n
          Export data related to motor vehicle pre-defined events in usage history is collected, recorded, stored, and exported by motor vehicle event data recorders (MVEDRs). A protocol for MVEDR output data compatibility and export protocols of MVEDR data elements is defined by this standard. A motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol is defined for safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC) and establishing a chain of custody link. This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing.<br />\n
          \t\t\t\t<br />\n
          Motor vehicle event data recorders (MVEDRs) collect, record, store, and export data related to motor vehicle pre-defined events in usage history. This standard defines a protocol for MVEDR output data compatibility and export protocols of MVEDR data elements. This standard does not prescribe which specific data elements shall be recorded, but instead provides a data dictionary of data attributes. This standard also defines a means of maintaining data security on the vehicle via a motor vehicle diagnostic link connector lockout apparatus (MVEDRCLA) by securing the vehicle output diagnostic link connector (DLC). This standard does not prescribe data security within the vehicle electronic control units (ECUs) or within the intra-vehicle communication and/or diagnostic networks; it instead defines ways and means to permit uniform but controlled access of electronic scan tools to the DLC for legitimate vehicle emissions status, maintenance, and/or repair. This standard also defines a motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol of safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC). This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing. This standard does not directly address related issues with regard to human health or human safety. It is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public roadways, whether offered as original or aftermarket equipment, whether stand-alone or integrated within the vehicle.<br />\n
          Many light-duty motor vehicles, and increasing numbers of heavy commercial vehicles, are equipped with some form of MVEDR. These systems, which are designed and produced by individual motor vehicle manufacturers and component suppliers, are diverse in function, and proprietary in nature, however, the SAE J1962 [B118]2 (ISO 15031-3:2004 [B55]) vehicle DLC has a common design and pinout, and is thus universally used to access event data recorder information. Data access via the DLC can be accomplished by using scan tools or microcomputers and network interfaces. This same DLC and network interface is also used for re-calibrating electronic control units on a vehicle. Such ECU applications can include restraint controls, engine controls, stability controls, braking controls, etc. This standard defines a protocol to protect against misuse of electronic tools which use the DLC to erase, modify, or tamper with electronic controller or odometer readings, or to improperly download data. Implementation of MVEDRCLA provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA that will act to prevent vehicle tampering, which can include odometer fraud, illegal calibrations leading to emissions violations, and theft of personal data. Adoption of this standard will therefore make the common MVEDR/DLC data more secure and credible while still permitting accessibility to legitimate end users. The continuing implementation of MVEDR systems provides an opportunity to voluntarily standardize data output and retrieval protocols to facilitate analysis and promote compatibility of MVEDR data. Adoption of the standard will therefore make MVEDR data more accessible and useful to end users.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Motor Vehicle Event Data Recorder (MVEDR)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95815 …}
    #channels: Doctrine\ORM\PersistentCollection {#95821 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95817 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95819 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95803
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95804
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95805
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 184
    -documents: Doctrine\ORM\PersistentCollection {#95809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95811 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#98419
  +product: App\Entity\Product\Product {#95806
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95823 …}
    #variants: Doctrine\ORM\PersistentCollection {#95825 …}
    #options: Doctrine\ORM\PersistentCollection {#95829 …}
    #associations: Doctrine\ORM\PersistentCollection {#95827 …}
    #createdAt: DateTime @1751040556 {#95801
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95802
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95813 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95806}
        #id: 45513
        #name: "IEEE 1616:2021"
        #slug: "ieee-1616-2021-ieee00010329-244281"
        #description: """
          Revision Standard - Active.<br />\n
          Export data related to motor vehicle pre-defined events in usage history is collected, recorded, stored, and exported by motor vehicle event data recorders (MVEDRs). A protocol for MVEDR output data compatibility and export protocols of MVEDR data elements is defined by this standard. A motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol is defined for safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC) and establishing a chain of custody link. This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing.<br />\n
          \t\t\t\t<br />\n
          Motor vehicle event data recorders (MVEDRs) collect, record, store, and export data related to motor vehicle pre-defined events in usage history. This standard defines a protocol for MVEDR output data compatibility and export protocols of MVEDR data elements. This standard does not prescribe which specific data elements shall be recorded, but instead provides a data dictionary of data attributes. This standard also defines a means of maintaining data security on the vehicle via a motor vehicle diagnostic link connector lockout apparatus (MVEDRCLA) by securing the vehicle output diagnostic link connector (DLC). This standard does not prescribe data security within the vehicle electronic control units (ECUs) or within the intra-vehicle communication and/or diagnostic networks; it instead defines ways and means to permit uniform but controlled access of electronic scan tools to the DLC for legitimate vehicle emissions status, maintenance, and/or repair. This standard also defines a motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) and a near field communication (NFC) protocol of safeguarding access to a vehicle’s event data recorder (EDR) data by securing the vehicle output diagnostic link connector (DLC). This standard is without prejudice to requirements of national or regional laws related to privacy, data protection, and personal data processing. This standard does not directly address related issues with regard to human health or human safety. It is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public roadways, whether offered as original or aftermarket equipment, whether stand-alone or integrated within the vehicle.<br />\n
          Many light-duty motor vehicles, and increasing numbers of heavy commercial vehicles, are equipped with some form of MVEDR. These systems, which are designed and produced by individual motor vehicle manufacturers and component suppliers, are diverse in function, and proprietary in nature, however, the SAE J1962 [B118]2 (ISO 15031-3:2004 [B55]) vehicle DLC has a common design and pinout, and is thus universally used to access event data recorder information. Data access via the DLC can be accomplished by using scan tools or microcomputers and network interfaces. This same DLC and network interface is also used for re-calibrating electronic control units on a vehicle. Such ECU applications can include restraint controls, engine controls, stability controls, braking controls, etc. This standard defines a protocol to protect against misuse of electronic tools which use the DLC to erase, modify, or tamper with electronic controller or odometer readings, or to improperly download data. Implementation of MVEDRCLA provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA that will act to prevent vehicle tampering, which can include odometer fraud, illegal calibrations leading to emissions violations, and theft of personal data. Adoption of this standard will therefore make the common MVEDR/DLC data more secure and credible while still permitting accessibility to legitimate end users. The continuing implementation of MVEDR systems provides an opportunity to voluntarily standardize data output and retrieval protocols to facilitate analysis and promote compatibility of MVEDR data. Adoption of the standard will therefore make MVEDR data more accessible and useful to end users.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Motor Vehicle Event Data Recorder (MVEDR)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95815 …}
    #channels: Doctrine\ORM\PersistentCollection {#95821 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95817 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95819 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95807 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95803
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95804
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95805
      date: 2021-12-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 184
    -documents: Doctrine\ORM\PersistentCollection {#95809 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95811 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.22 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95837
    #id: 12635
    #code: "IEEE00010351"
    #attributes: Doctrine\ORM\PersistentCollection {#95854 …}
    #variants: Doctrine\ORM\PersistentCollection {#95856 …}
    #options: Doctrine\ORM\PersistentCollection {#95860 …}
    #associations: Doctrine\ORM\PersistentCollection {#95858 …}
    #createdAt: DateTime @1751040561 {#95831
      date: 2025-06-27 18:09:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95832
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98578
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95837}
        #id: 45549
        #name: "IEEE 1910.1:2020"
        #slug: "ieee-1910-1-2020-ieee00010351-244290"
        #description: """
          New IEEE Standard - Active.<br />\n
          Meshed tree bridging protocol (MTBP) ensures that bridged network constituents receive high reliability in frame delivery in the event of link or bridge failures. MTBP is based on the meshed tree algorithm (MTA) that allows for simultaneous construction and maintenance of multiple trees or tree branches from a single root. In the event of tree branch failures due to link or bridge failures, another preconstructed and maintained branch exists as an immediate fallback. Recovery and tree pruning times in meshed tree bridging is minimal. Multiple roots should be preassigned to construct multiple distinguishable meshed trees from each root. In the event of a root bridge failure, the standby root and its meshed tree provides loop-free paths for frame forwarding with minimal recovery delays.<br />\n
          \t\t\t\t<br />\n
          The scope of this document is as follows:<br />\n
          a) In bridged networks running MTBP, ports shall be identified as either a meshed tree port that participates in the meshed tree resolution, or a host port, to which a local host is connected. Only meshed tree ports are allowed to participate in the meshed tree resolution.<br />\n
          b) MTBP provides superior fault tolerance by preconfiguring several logical trees from a root. One of these logical trees is considered the primary tree and is used for forwarding broadcast frames. In the event of a network component failure and immediately on failure detection of the primary branch, broadcast frame forwarding is taken over by any one of the other preconfigured tree branches. This is achieved with minimal message dissemination and delay.<br />\n
          c) The addition of a bridge configured to run MTBP will allow the bridge to send a request to join (via MT_JOIN message) message to all other bridges to which it is connected. The new bridge will join the bridges already in the topology. The new bridge then receives multiple invitations from its neighbors to join tree branches that they are already part of. The new bridge decides to join the multiple tree branches and stores the multiple paths in order of preference. One of these paths shall be the path for broadcast frame forwarding.<br />\n
          The purpose of this standard is to specify the methods for establishing several tree-like structures on an existing topology. The protocol leverages any useable path rather than eliminating possible alternate links. Upon changes to the topology, the meshed tree protocol will converge in zero time through the immediate use of alternate predetermined viable pathways on failure detection.<br />\n
          MTBP allows for maintenance of multiple active topologies by adopting the MTA (described in Clause 5). The concept of meshed trees is novel in that they do not use the traditionally prevailing concept of a single tree from one root. They allow for multiple trees or subtrees to be constructed from a root and thus maintain multiple paths in readiness to take over in the event of a link or path failure. Meshed trees thus address the path redundancy in bridged networks by providing multiple loop-free tree paths between a root bridge and a non-root bridge. Meshed trees also address immediate failover upon link failure detection because they allow several logical pathways to exist between any two communicating bridges. To cut down on the delays due to root election and re-election in the event of current root failure, the MMT concept allows for multiple meshed trees to be constructed from multiple predesignated roots.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Meshed Tree Bridging with Loop-Free Forwarding"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95846 …}
    #channels: Doctrine\ORM\PersistentCollection {#95852 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95833
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1608505200 {#95834
      date: 2020-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605222000 {#95835
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605222000 {#95836
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1910.1"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#95840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95842 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#98558
  +product: App\Entity\Product\Product {#95837
    #id: 12635
    #code: "IEEE00010351"
    #attributes: Doctrine\ORM\PersistentCollection {#95854 …}
    #variants: Doctrine\ORM\PersistentCollection {#95856 …}
    #options: Doctrine\ORM\PersistentCollection {#95860 …}
    #associations: Doctrine\ORM\PersistentCollection {#95858 …}
    #createdAt: DateTime @1751040561 {#95831
      date: 2025-06-27 18:09:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95832
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98578
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95837}
        #id: 45549
        #name: "IEEE 1910.1:2020"
        #slug: "ieee-1910-1-2020-ieee00010351-244290"
        #description: """
          New IEEE Standard - Active.<br />\n
          Meshed tree bridging protocol (MTBP) ensures that bridged network constituents receive high reliability in frame delivery in the event of link or bridge failures. MTBP is based on the meshed tree algorithm (MTA) that allows for simultaneous construction and maintenance of multiple trees or tree branches from a single root. In the event of tree branch failures due to link or bridge failures, another preconstructed and maintained branch exists as an immediate fallback. Recovery and tree pruning times in meshed tree bridging is minimal. Multiple roots should be preassigned to construct multiple distinguishable meshed trees from each root. In the event of a root bridge failure, the standby root and its meshed tree provides loop-free paths for frame forwarding with minimal recovery delays.<br />\n
          \t\t\t\t<br />\n
          The scope of this document is as follows:<br />\n
          a) In bridged networks running MTBP, ports shall be identified as either a meshed tree port that participates in the meshed tree resolution, or a host port, to which a local host is connected. Only meshed tree ports are allowed to participate in the meshed tree resolution.<br />\n
          b) MTBP provides superior fault tolerance by preconfiguring several logical trees from a root. One of these logical trees is considered the primary tree and is used for forwarding broadcast frames. In the event of a network component failure and immediately on failure detection of the primary branch, broadcast frame forwarding is taken over by any one of the other preconfigured tree branches. This is achieved with minimal message dissemination and delay.<br />\n
          c) The addition of a bridge configured to run MTBP will allow the bridge to send a request to join (via MT_JOIN message) message to all other bridges to which it is connected. The new bridge will join the bridges already in the topology. The new bridge then receives multiple invitations from its neighbors to join tree branches that they are already part of. The new bridge decides to join the multiple tree branches and stores the multiple paths in order of preference. One of these paths shall be the path for broadcast frame forwarding.<br />\n
          The purpose of this standard is to specify the methods for establishing several tree-like structures on an existing topology. The protocol leverages any useable path rather than eliminating possible alternate links. Upon changes to the topology, the meshed tree protocol will converge in zero time through the immediate use of alternate predetermined viable pathways on failure detection.<br />\n
          MTBP allows for maintenance of multiple active topologies by adopting the MTA (described in Clause 5). The concept of meshed trees is novel in that they do not use the traditionally prevailing concept of a single tree from one root. They allow for multiple trees or subtrees to be constructed from a root and thus maintain multiple paths in readiness to take over in the event of a link or path failure. Meshed trees thus address the path redundancy in bridged networks by providing multiple loop-free tree paths between a root bridge and a non-root bridge. Meshed trees also address immediate failover upon link failure detection because they allow several logical pathways to exist between any two communicating bridges. To cut down on the delays due to root election and re-election in the event of current root failure, the MMT concept allows for multiple meshed trees to be constructed from multiple predesignated roots.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Meshed Tree Bridging with Loop-Free Forwarding"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95846 …}
    #channels: Doctrine\ORM\PersistentCollection {#95852 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95833
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1608505200 {#95834
      date: 2020-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605222000 {#95835
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605222000 {#95836
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1910.1"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#95840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95842 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95837
    #id: 12635
    #code: "IEEE00010351"
    #attributes: Doctrine\ORM\PersistentCollection {#95854 …}
    #variants: Doctrine\ORM\PersistentCollection {#95856 …}
    #options: Doctrine\ORM\PersistentCollection {#95860 …}
    #associations: Doctrine\ORM\PersistentCollection {#95858 …}
    #createdAt: DateTime @1751040561 {#95831
      date: 2025-06-27 18:09:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95832
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98578
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95837}
        #id: 45549
        #name: "IEEE 1910.1:2020"
        #slug: "ieee-1910-1-2020-ieee00010351-244290"
        #description: """
          New IEEE Standard - Active.<br />\n
          Meshed tree bridging protocol (MTBP) ensures that bridged network constituents receive high reliability in frame delivery in the event of link or bridge failures. MTBP is based on the meshed tree algorithm (MTA) that allows for simultaneous construction and maintenance of multiple trees or tree branches from a single root. In the event of tree branch failures due to link or bridge failures, another preconstructed and maintained branch exists as an immediate fallback. Recovery and tree pruning times in meshed tree bridging is minimal. Multiple roots should be preassigned to construct multiple distinguishable meshed trees from each root. In the event of a root bridge failure, the standby root and its meshed tree provides loop-free paths for frame forwarding with minimal recovery delays.<br />\n
          \t\t\t\t<br />\n
          The scope of this document is as follows:<br />\n
          a) In bridged networks running MTBP, ports shall be identified as either a meshed tree port that participates in the meshed tree resolution, or a host port, to which a local host is connected. Only meshed tree ports are allowed to participate in the meshed tree resolution.<br />\n
          b) MTBP provides superior fault tolerance by preconfiguring several logical trees from a root. One of these logical trees is considered the primary tree and is used for forwarding broadcast frames. In the event of a network component failure and immediately on failure detection of the primary branch, broadcast frame forwarding is taken over by any one of the other preconfigured tree branches. This is achieved with minimal message dissemination and delay.<br />\n
          c) The addition of a bridge configured to run MTBP will allow the bridge to send a request to join (via MT_JOIN message) message to all other bridges to which it is connected. The new bridge will join the bridges already in the topology. The new bridge then receives multiple invitations from its neighbors to join tree branches that they are already part of. The new bridge decides to join the multiple tree branches and stores the multiple paths in order of preference. One of these paths shall be the path for broadcast frame forwarding.<br />\n
          The purpose of this standard is to specify the methods for establishing several tree-like structures on an existing topology. The protocol leverages any useable path rather than eliminating possible alternate links. Upon changes to the topology, the meshed tree protocol will converge in zero time through the immediate use of alternate predetermined viable pathways on failure detection.<br />\n
          MTBP allows for maintenance of multiple active topologies by adopting the MTA (described in Clause 5). The concept of meshed trees is novel in that they do not use the traditionally prevailing concept of a single tree from one root. They allow for multiple trees or subtrees to be constructed from a root and thus maintain multiple paths in readiness to take over in the event of a link or path failure. Meshed trees thus address the path redundancy in bridged networks by providing multiple loop-free tree paths between a root bridge and a non-root bridge. Meshed trees also address immediate failover upon link failure detection because they allow several logical pathways to exist between any two communicating bridges. To cut down on the delays due to root election and re-election in the event of current root failure, the MMT concept allows for multiple meshed trees to be constructed from multiple predesignated roots.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Meshed Tree Bridging with Loop-Free Forwarding"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95846 …}
    #channels: Doctrine\ORM\PersistentCollection {#95852 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95833
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1608505200 {#95834
      date: 2020-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605222000 {#95835
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605222000 {#95836
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1910.1"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#95840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95842 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#98592
  +product: App\Entity\Product\Product {#95837
    #id: 12635
    #code: "IEEE00010351"
    #attributes: Doctrine\ORM\PersistentCollection {#95854 …}
    #variants: Doctrine\ORM\PersistentCollection {#95856 …}
    #options: Doctrine\ORM\PersistentCollection {#95860 …}
    #associations: Doctrine\ORM\PersistentCollection {#95858 …}
    #createdAt: DateTime @1751040561 {#95831
      date: 2025-06-27 18:09:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95832
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98578
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95837}
        #id: 45549
        #name: "IEEE 1910.1:2020"
        #slug: "ieee-1910-1-2020-ieee00010351-244290"
        #description: """
          New IEEE Standard - Active.<br />\n
          Meshed tree bridging protocol (MTBP) ensures that bridged network constituents receive high reliability in frame delivery in the event of link or bridge failures. MTBP is based on the meshed tree algorithm (MTA) that allows for simultaneous construction and maintenance of multiple trees or tree branches from a single root. In the event of tree branch failures due to link or bridge failures, another preconstructed and maintained branch exists as an immediate fallback. Recovery and tree pruning times in meshed tree bridging is minimal. Multiple roots should be preassigned to construct multiple distinguishable meshed trees from each root. In the event of a root bridge failure, the standby root and its meshed tree provides loop-free paths for frame forwarding with minimal recovery delays.<br />\n
          \t\t\t\t<br />\n
          The scope of this document is as follows:<br />\n
          a) In bridged networks running MTBP, ports shall be identified as either a meshed tree port that participates in the meshed tree resolution, or a host port, to which a local host is connected. Only meshed tree ports are allowed to participate in the meshed tree resolution.<br />\n
          b) MTBP provides superior fault tolerance by preconfiguring several logical trees from a root. One of these logical trees is considered the primary tree and is used for forwarding broadcast frames. In the event of a network component failure and immediately on failure detection of the primary branch, broadcast frame forwarding is taken over by any one of the other preconfigured tree branches. This is achieved with minimal message dissemination and delay.<br />\n
          c) The addition of a bridge configured to run MTBP will allow the bridge to send a request to join (via MT_JOIN message) message to all other bridges to which it is connected. The new bridge will join the bridges already in the topology. The new bridge then receives multiple invitations from its neighbors to join tree branches that they are already part of. The new bridge decides to join the multiple tree branches and stores the multiple paths in order of preference. One of these paths shall be the path for broadcast frame forwarding.<br />\n
          The purpose of this standard is to specify the methods for establishing several tree-like structures on an existing topology. The protocol leverages any useable path rather than eliminating possible alternate links. Upon changes to the topology, the meshed tree protocol will converge in zero time through the immediate use of alternate predetermined viable pathways on failure detection.<br />\n
          MTBP allows for maintenance of multiple active topologies by adopting the MTA (described in Clause 5). The concept of meshed trees is novel in that they do not use the traditionally prevailing concept of a single tree from one root. They allow for multiple trees or subtrees to be constructed from a root and thus maintain multiple paths in readiness to take over in the event of a link or path failure. Meshed trees thus address the path redundancy in bridged networks by providing multiple loop-free tree paths between a root bridge and a non-root bridge. Meshed trees also address immediate failover upon link failure detection because they allow several logical pathways to exist between any two communicating bridges. To cut down on the delays due to root election and re-election in the event of current root failure, the MMT concept allows for multiple meshed trees to be constructed from multiple predesignated roots.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Meshed Tree Bridging with Loop-Free Forwarding"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95846 …}
    #channels: Doctrine\ORM\PersistentCollection {#95852 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95833
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1608505200 {#95834
      date: 2020-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605222000 {#95835
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605222000 {#95836
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1910.1"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#95840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95842 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.66 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95837
    #id: 12635
    #code: "IEEE00010351"
    #attributes: Doctrine\ORM\PersistentCollection {#95854 …}
    #variants: Doctrine\ORM\PersistentCollection {#95856 …}
    #options: Doctrine\ORM\PersistentCollection {#95860 …}
    #associations: Doctrine\ORM\PersistentCollection {#95858 …}
    #createdAt: DateTime @1751040561 {#95831
      date: 2025-06-27 18:09:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95832
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98578
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95837}
        #id: 45549
        #name: "IEEE 1910.1:2020"
        #slug: "ieee-1910-1-2020-ieee00010351-244290"
        #description: """
          New IEEE Standard - Active.<br />\n
          Meshed tree bridging protocol (MTBP) ensures that bridged network constituents receive high reliability in frame delivery in the event of link or bridge failures. MTBP is based on the meshed tree algorithm (MTA) that allows for simultaneous construction and maintenance of multiple trees or tree branches from a single root. In the event of tree branch failures due to link or bridge failures, another preconstructed and maintained branch exists as an immediate fallback. Recovery and tree pruning times in meshed tree bridging is minimal. Multiple roots should be preassigned to construct multiple distinguishable meshed trees from each root. In the event of a root bridge failure, the standby root and its meshed tree provides loop-free paths for frame forwarding with minimal recovery delays.<br />\n
          \t\t\t\t<br />\n
          The scope of this document is as follows:<br />\n
          a) In bridged networks running MTBP, ports shall be identified as either a meshed tree port that participates in the meshed tree resolution, or a host port, to which a local host is connected. Only meshed tree ports are allowed to participate in the meshed tree resolution.<br />\n
          b) MTBP provides superior fault tolerance by preconfiguring several logical trees from a root. One of these logical trees is considered the primary tree and is used for forwarding broadcast frames. In the event of a network component failure and immediately on failure detection of the primary branch, broadcast frame forwarding is taken over by any one of the other preconfigured tree branches. This is achieved with minimal message dissemination and delay.<br />\n
          c) The addition of a bridge configured to run MTBP will allow the bridge to send a request to join (via MT_JOIN message) message to all other bridges to which it is connected. The new bridge will join the bridges already in the topology. The new bridge then receives multiple invitations from its neighbors to join tree branches that they are already part of. The new bridge decides to join the multiple tree branches and stores the multiple paths in order of preference. One of these paths shall be the path for broadcast frame forwarding.<br />\n
          The purpose of this standard is to specify the methods for establishing several tree-like structures on an existing topology. The protocol leverages any useable path rather than eliminating possible alternate links. Upon changes to the topology, the meshed tree protocol will converge in zero time through the immediate use of alternate predetermined viable pathways on failure detection.<br />\n
          MTBP allows for maintenance of multiple active topologies by adopting the MTA (described in Clause 5). The concept of meshed trees is novel in that they do not use the traditionally prevailing concept of a single tree from one root. They allow for multiple trees or subtrees to be constructed from a root and thus maintain multiple paths in readiness to take over in the event of a link or path failure. Meshed trees thus address the path redundancy in bridged networks by providing multiple loop-free tree paths between a root bridge and a non-root bridge. Meshed trees also address immediate failover upon link failure detection because they allow several logical pathways to exist between any two communicating bridges. To cut down on the delays due to root election and re-election in the event of current root failure, the MMT concept allows for multiple meshed trees to be constructed from multiple predesignated roots.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Meshed Tree Bridging with Loop-Free Forwarding"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95846 …}
    #channels: Doctrine\ORM\PersistentCollection {#95852 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95833
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1608505200 {#95834
      date: 2020-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605222000 {#95835
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605222000 {#95836
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1910.1"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#95840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95842 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#98665
  +product: App\Entity\Product\Product {#95837
    #id: 12635
    #code: "IEEE00010351"
    #attributes: Doctrine\ORM\PersistentCollection {#95854 …}
    #variants: Doctrine\ORM\PersistentCollection {#95856 …}
    #options: Doctrine\ORM\PersistentCollection {#95860 …}
    #associations: Doctrine\ORM\PersistentCollection {#95858 …}
    #createdAt: DateTime @1751040561 {#95831
      date: 2025-06-27 18:09:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95832
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95844 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98578
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95837}
        #id: 45549
        #name: "IEEE 1910.1:2020"
        #slug: "ieee-1910-1-2020-ieee00010351-244290"
        #description: """
          New IEEE Standard - Active.<br />\n
          Meshed tree bridging protocol (MTBP) ensures that bridged network constituents receive high reliability in frame delivery in the event of link or bridge failures. MTBP is based on the meshed tree algorithm (MTA) that allows for simultaneous construction and maintenance of multiple trees or tree branches from a single root. In the event of tree branch failures due to link or bridge failures, another preconstructed and maintained branch exists as an immediate fallback. Recovery and tree pruning times in meshed tree bridging is minimal. Multiple roots should be preassigned to construct multiple distinguishable meshed trees from each root. In the event of a root bridge failure, the standby root and its meshed tree provides loop-free paths for frame forwarding with minimal recovery delays.<br />\n
          \t\t\t\t<br />\n
          The scope of this document is as follows:<br />\n
          a) In bridged networks running MTBP, ports shall be identified as either a meshed tree port that participates in the meshed tree resolution, or a host port, to which a local host is connected. Only meshed tree ports are allowed to participate in the meshed tree resolution.<br />\n
          b) MTBP provides superior fault tolerance by preconfiguring several logical trees from a root. One of these logical trees is considered the primary tree and is used for forwarding broadcast frames. In the event of a network component failure and immediately on failure detection of the primary branch, broadcast frame forwarding is taken over by any one of the other preconfigured tree branches. This is achieved with minimal message dissemination and delay.<br />\n
          c) The addition of a bridge configured to run MTBP will allow the bridge to send a request to join (via MT_JOIN message) message to all other bridges to which it is connected. The new bridge will join the bridges already in the topology. The new bridge then receives multiple invitations from its neighbors to join tree branches that they are already part of. The new bridge decides to join the multiple tree branches and stores the multiple paths in order of preference. One of these paths shall be the path for broadcast frame forwarding.<br />\n
          The purpose of this standard is to specify the methods for establishing several tree-like structures on an existing topology. The protocol leverages any useable path rather than eliminating possible alternate links. Upon changes to the topology, the meshed tree protocol will converge in zero time through the immediate use of alternate predetermined viable pathways on failure detection.<br />\n
          MTBP allows for maintenance of multiple active topologies by adopting the MTA (described in Clause 5). The concept of meshed trees is novel in that they do not use the traditionally prevailing concept of a single tree from one root. They allow for multiple trees or subtrees to be constructed from a root and thus maintain multiple paths in readiness to take over in the event of a link or path failure. Meshed trees thus address the path redundancy in bridged networks by providing multiple loop-free tree paths between a root bridge and a non-root bridge. Meshed trees also address immediate failover upon link failure detection because they allow several logical pathways to exist between any two communicating bridges. To cut down on the delays due to root election and re-election in the event of current root failure, the MMT concept allows for multiple meshed trees to be constructed from multiple predesignated roots.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Meshed Tree Bridging with Loop-Free Forwarding"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95846 …}
    #channels: Doctrine\ORM\PersistentCollection {#95852 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95848 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95850 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95838 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95833
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1608505200 {#95834
      date: 2020-12-21 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605222000 {#95835
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605222000 {#95836
      date: 2020-11-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1910.1"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#95840 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95842 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.62 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95868
    #id: 12636
    #code: "IEEE00010352"
    #attributes: Doctrine\ORM\PersistentCollection {#95885 …}
    #variants: Doctrine\ORM\PersistentCollection {#95887 …}
    #options: Doctrine\ORM\PersistentCollection {#95891 …}
    #associations: Doctrine\ORM\PersistentCollection {#95889 …}
    #createdAt: DateTime @1751040562 {#95862
      date: 2025-06-27 18:09:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95863
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95875 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98807
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95868}
        #id: 45553
        #name: "IEEE 1920.1:2022"
        #slug: "ieee-1920-1-2022-ieee00010352-244291"
        #description: """
          New IEEE Standard - Active.<br />\n
          IEEE Std 1920.1 defines air-to-air communications for self-organized ad hoc aerial networks. It outlines the network service architecture, security framework, and data model. IEEE Std 1920.1 is agnostic to the type of network (Wireless or Cellular or other) and it is applicable to manned and unmanned, small and large, and civil and commercial aircraft systems. IEEE Std 1920.1 is the first in the series of IEEE P1920.X standards. It is anticipated that IEEE Std 1920.1 will be used as a foundation to define more specific standards in this series.<br />\n
          \t\t\t\t<br />\n
          IEEE Std 1920.1 defines air-to-air communications over self-organized aerial ad hoc networks and describes the reference architecture for aerial networks, where aircraft can form a network to share information with one another with or without any supporting infrastructure, such as satellite or cellular communications. This standard is intended for RLOS and BRLOS small UASs used for civil and commercial applications. The architecture can also be extended to include additional platforms, making it a useful guide for other aircraft systems. The communications and networking standards are independent of the type of network (wireless, cellular, or other). The main objective of the IEEE Std 1920.1 data model is to define and format data consistently in a common, secure data structure that can be leveraged across the industry. This can help improve the integrity, safety, and security of the data regardless of the types of use cases, communication technologies, or diversity of the vehicles utilized. IEEE Std 1920.1 does not specify procedures or protocols that define the means to access radio-frequency spectrum and manage its use (i.e., an “air interface”). IEEE Std 1920.1 does not specify the size, maximum take-off weight (MTOW), modes of propulsion, and other characteristics of the UAS. It is expected that most UASs with less than 250 kg MTOW can use the protocols defined in IEEE Std 1920.1. An MTOW above 250 kg would put the UAS in the scope of certification requirements that impose requirements beyond those applicable to aircraft operating communications services within the scope of IEEE Std 1920.1.<br />\n
          IEEE Std 1920.1 can contribute to aviation safety by providing for enhancing situational awareness of manned and unmanned aircraft in the shared airspace through air-to-air communications facilitated by an aerial ad hoc network. As UASs become increasingly integrated into the National Airspace (NAS), there is a corresponding need for technology systems to provide enhanced situational awareness of all aircraft operating in the shared airspace. IEEE Std 1920.1 also provides a means of compliance for the network remote identification of unmanned aircraft systems, to provide information to distinguish compliant UAS users from those potentially posing aviation security risk. The need for self-organized aerial networks in increasing the situational awareness of aircraft systems was highlighted in a working paper titled “Use of Self-organizing Airborne Networks to Monitor Commercial Aircraft Globally” presented in a May 2014 meeting of the International Civil Aviation Organization (ICAO) (see ADS-B in Europe (B1)).
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Aerial Network Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95877 …}
    #channels: Doctrine\ORM\PersistentCollection {#95883 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95879 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95881 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95869 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95864
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1685311200 {#95865
      date: 2023-05-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1682373600 {#95866
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1682373600 {#95867
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1920.1"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#95871 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95873 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#98787
  +product: App\Entity\Product\Product {#95868
    #id: 12636
    #code: "IEEE00010352"
    #attributes: Doctrine\ORM\PersistentCollection {#95885 …}
    #variants: Doctrine\ORM\PersistentCollection {#95887 …}
    #options: Doctrine\ORM\PersistentCollection {#95891 …}
    #associations: Doctrine\ORM\PersistentCollection {#95889 …}
    #createdAt: DateTime @1751040562 {#95862
      date: 2025-06-27 18:09:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95863
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95875 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98807
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95868}
        #id: 45553
        #name: "IEEE 1920.1:2022"
        #slug: "ieee-1920-1-2022-ieee00010352-244291"
        #description: """
          New IEEE Standard - Active.<br />\n
          IEEE Std 1920.1 defines air-to-air communications for self-organized ad hoc aerial networks. It outlines the network service architecture, security framework, and data model. IEEE Std 1920.1 is agnostic to the type of network (Wireless or Cellular or other) and it is applicable to manned and unmanned, small and large, and civil and commercial aircraft systems. IEEE Std 1920.1 is the first in the series of IEEE P1920.X standards. It is anticipated that IEEE Std 1920.1 will be used as a foundation to define more specific standards in this series.<br />\n
          \t\t\t\t<br />\n
          IEEE Std 1920.1 defines air-to-air communications over self-organized aerial ad hoc networks and describes the reference architecture for aerial networks, where aircraft can form a network to share information with one another with or without any supporting infrastructure, such as satellite or cellular communications. This standard is intended for RLOS and BRLOS small UASs used for civil and commercial applications. The architecture can also be extended to include additional platforms, making it a useful guide for other aircraft systems. The communications and networking standards are independent of the type of network (wireless, cellular, or other). The main objective of the IEEE Std 1920.1 data model is to define and format data consistently in a common, secure data structure that can be leveraged across the industry. This can help improve the integrity, safety, and security of the data regardless of the types of use cases, communication technologies, or diversity of the vehicles utilized. IEEE Std 1920.1 does not specify procedures or protocols that define the means to access radio-frequency spectrum and manage its use (i.e., an “air interface”). IEEE Std 1920.1 does not specify the size, maximum take-off weight (MTOW), modes of propulsion, and other characteristics of the UAS. It is expected that most UASs with less than 250 kg MTOW can use the protocols defined in IEEE Std 1920.1. An MTOW above 250 kg would put the UAS in the scope of certification requirements that impose requirements beyond those applicable to aircraft operating communications services within the scope of IEEE Std 1920.1.<br />\n
          IEEE Std 1920.1 can contribute to aviation safety by providing for enhancing situational awareness of manned and unmanned aircraft in the shared airspace through air-to-air communications facilitated by an aerial ad hoc network. As UASs become increasingly integrated into the National Airspace (NAS), there is a corresponding need for technology systems to provide enhanced situational awareness of all aircraft operating in the shared airspace. IEEE Std 1920.1 also provides a means of compliance for the network remote identification of unmanned aircraft systems, to provide information to distinguish compliant UAS users from those potentially posing aviation security risk. The need for self-organized aerial networks in increasing the situational awareness of aircraft systems was highlighted in a working paper titled “Use of Self-organizing Airborne Networks to Monitor Commercial Aircraft Globally” presented in a May 2014 meeting of the International Civil Aviation Organization (ICAO) (see ADS-B in Europe (B1)).
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Aerial Network Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95877 …}
    #channels: Doctrine\ORM\PersistentCollection {#95883 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95879 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95881 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95869 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95864
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1685311200 {#95865
      date: 2023-05-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1682373600 {#95866
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1682373600 {#95867
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1920.1"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#95871 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95873 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.19 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95868
    #id: 12636
    #code: "IEEE00010352"
    #attributes: Doctrine\ORM\PersistentCollection {#95885 …}
    #variants: Doctrine\ORM\PersistentCollection {#95887 …}
    #options: Doctrine\ORM\PersistentCollection {#95891 …}
    #associations: Doctrine\ORM\PersistentCollection {#95889 …}
    #createdAt: DateTime @1751040562 {#95862
      date: 2025-06-27 18:09:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95863
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95875 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98807
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95868}
        #id: 45553
        #name: "IEEE 1920.1:2022"
        #slug: "ieee-1920-1-2022-ieee00010352-244291"
        #description: """
          New IEEE Standard - Active.<br />\n
          IEEE Std 1920.1 defines air-to-air communications for self-organized ad hoc aerial networks. It outlines the network service architecture, security framework, and data model. IEEE Std 1920.1 is agnostic to the type of network (Wireless or Cellular or other) and it is applicable to manned and unmanned, small and large, and civil and commercial aircraft systems. IEEE Std 1920.1 is the first in the series of IEEE P1920.X standards. It is anticipated that IEEE Std 1920.1 will be used as a foundation to define more specific standards in this series.<br />\n
          \t\t\t\t<br />\n
          IEEE Std 1920.1 defines air-to-air communications over self-organized aerial ad hoc networks and describes the reference architecture for aerial networks, where aircraft can form a network to share information with one another with or without any supporting infrastructure, such as satellite or cellular communications. This standard is intended for RLOS and BRLOS small UASs used for civil and commercial applications. The architecture can also be extended to include additional platforms, making it a useful guide for other aircraft systems. The communications and networking standards are independent of the type of network (wireless, cellular, or other). The main objective of the IEEE Std 1920.1 data model is to define and format data consistently in a common, secure data structure that can be leveraged across the industry. This can help improve the integrity, safety, and security of the data regardless of the types of use cases, communication technologies, or diversity of the vehicles utilized. IEEE Std 1920.1 does not specify procedures or protocols that define the means to access radio-frequency spectrum and manage its use (i.e., an “air interface”). IEEE Std 1920.1 does not specify the size, maximum take-off weight (MTOW), modes of propulsion, and other characteristics of the UAS. It is expected that most UASs with less than 250 kg MTOW can use the protocols defined in IEEE Std 1920.1. An MTOW above 250 kg would put the UAS in the scope of certification requirements that impose requirements beyond those applicable to aircraft operating communications services within the scope of IEEE Std 1920.1.<br />\n
          IEEE Std 1920.1 can contribute to aviation safety by providing for enhancing situational awareness of manned and unmanned aircraft in the shared airspace through air-to-air communications facilitated by an aerial ad hoc network. As UASs become increasingly integrated into the National Airspace (NAS), there is a corresponding need for technology systems to provide enhanced situational awareness of all aircraft operating in the shared airspace. IEEE Std 1920.1 also provides a means of compliance for the network remote identification of unmanned aircraft systems, to provide information to distinguish compliant UAS users from those potentially posing aviation security risk. The need for self-organized aerial networks in increasing the situational awareness of aircraft systems was highlighted in a working paper titled “Use of Self-organizing Airborne Networks to Monitor Commercial Aircraft Globally” presented in a May 2014 meeting of the International Civil Aviation Organization (ICAO) (see ADS-B in Europe (B1)).
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Aerial Network Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95877 …}
    #channels: Doctrine\ORM\PersistentCollection {#95883 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95879 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95881 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95869 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95864
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1685311200 {#95865
      date: 2023-05-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1682373600 {#95866
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1682373600 {#95867
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1920.1"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#95871 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95873 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#98821
  +product: App\Entity\Product\Product {#95868
    #id: 12636
    #code: "IEEE00010352"
    #attributes: Doctrine\ORM\PersistentCollection {#95885 …}
    #variants: Doctrine\ORM\PersistentCollection {#95887 …}
    #options: Doctrine\ORM\PersistentCollection {#95891 …}
    #associations: Doctrine\ORM\PersistentCollection {#95889 …}
    #createdAt: DateTime @1751040562 {#95862
      date: 2025-06-27 18:09:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95863
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95875 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98807
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95868}
        #id: 45553
        #name: "IEEE 1920.1:2022"
        #slug: "ieee-1920-1-2022-ieee00010352-244291"
        #description: """
          New IEEE Standard - Active.<br />\n
          IEEE Std 1920.1 defines air-to-air communications for self-organized ad hoc aerial networks. It outlines the network service architecture, security framework, and data model. IEEE Std 1920.1 is agnostic to the type of network (Wireless or Cellular or other) and it is applicable to manned and unmanned, small and large, and civil and commercial aircraft systems. IEEE Std 1920.1 is the first in the series of IEEE P1920.X standards. It is anticipated that IEEE Std 1920.1 will be used as a foundation to define more specific standards in this series.<br />\n
          \t\t\t\t<br />\n
          IEEE Std 1920.1 defines air-to-air communications over self-organized aerial ad hoc networks and describes the reference architecture for aerial networks, where aircraft can form a network to share information with one another with or without any supporting infrastructure, such as satellite or cellular communications. This standard is intended for RLOS and BRLOS small UASs used for civil and commercial applications. The architecture can also be extended to include additional platforms, making it a useful guide for other aircraft systems. The communications and networking standards are independent of the type of network (wireless, cellular, or other). The main objective of the IEEE Std 1920.1 data model is to define and format data consistently in a common, secure data structure that can be leveraged across the industry. This can help improve the integrity, safety, and security of the data regardless of the types of use cases, communication technologies, or diversity of the vehicles utilized. IEEE Std 1920.1 does not specify procedures or protocols that define the means to access radio-frequency spectrum and manage its use (i.e., an “air interface”). IEEE Std 1920.1 does not specify the size, maximum take-off weight (MTOW), modes of propulsion, and other characteristics of the UAS. It is expected that most UASs with less than 250 kg MTOW can use the protocols defined in IEEE Std 1920.1. An MTOW above 250 kg would put the UAS in the scope of certification requirements that impose requirements beyond those applicable to aircraft operating communications services within the scope of IEEE Std 1920.1.<br />\n
          IEEE Std 1920.1 can contribute to aviation safety by providing for enhancing situational awareness of manned and unmanned aircraft in the shared airspace through air-to-air communications facilitated by an aerial ad hoc network. As UASs become increasingly integrated into the National Airspace (NAS), there is a corresponding need for technology systems to provide enhanced situational awareness of all aircraft operating in the shared airspace. IEEE Std 1920.1 also provides a means of compliance for the network remote identification of unmanned aircraft systems, to provide information to distinguish compliant UAS users from those potentially posing aviation security risk. The need for self-organized aerial networks in increasing the situational awareness of aircraft systems was highlighted in a working paper titled “Use of Self-organizing Airborne Networks to Monitor Commercial Aircraft Globally” presented in a May 2014 meeting of the International Civil Aviation Organization (ICAO) (see ADS-B in Europe (B1)).
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Aerial Network Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95877 …}
    #channels: Doctrine\ORM\PersistentCollection {#95883 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95879 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95881 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95869 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95864
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1685311200 {#95865
      date: 2023-05-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1682373600 {#95866
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1682373600 {#95867
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1920.1"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#95871 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95873 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.65 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95868
    #id: 12636
    #code: "IEEE00010352"
    #attributes: Doctrine\ORM\PersistentCollection {#95885 …}
    #variants: Doctrine\ORM\PersistentCollection {#95887 …}
    #options: Doctrine\ORM\PersistentCollection {#95891 …}
    #associations: Doctrine\ORM\PersistentCollection {#95889 …}
    #createdAt: DateTime @1751040562 {#95862
      date: 2025-06-27 18:09:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95863
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95875 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98807
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95868}
        #id: 45553
        #name: "IEEE 1920.1:2022"
        #slug: "ieee-1920-1-2022-ieee00010352-244291"
        #description: """
          New IEEE Standard - Active.<br />\n
          IEEE Std 1920.1 defines air-to-air communications for self-organized ad hoc aerial networks. It outlines the network service architecture, security framework, and data model. IEEE Std 1920.1 is agnostic to the type of network (Wireless or Cellular or other) and it is applicable to manned and unmanned, small and large, and civil and commercial aircraft systems. IEEE Std 1920.1 is the first in the series of IEEE P1920.X standards. It is anticipated that IEEE Std 1920.1 will be used as a foundation to define more specific standards in this series.<br />\n
          \t\t\t\t<br />\n
          IEEE Std 1920.1 defines air-to-air communications over self-organized aerial ad hoc networks and describes the reference architecture for aerial networks, where aircraft can form a network to share information with one another with or without any supporting infrastructure, such as satellite or cellular communications. This standard is intended for RLOS and BRLOS small UASs used for civil and commercial applications. The architecture can also be extended to include additional platforms, making it a useful guide for other aircraft systems. The communications and networking standards are independent of the type of network (wireless, cellular, or other). The main objective of the IEEE Std 1920.1 data model is to define and format data consistently in a common, secure data structure that can be leveraged across the industry. This can help improve the integrity, safety, and security of the data regardless of the types of use cases, communication technologies, or diversity of the vehicles utilized. IEEE Std 1920.1 does not specify procedures or protocols that define the means to access radio-frequency spectrum and manage its use (i.e., an “air interface”). IEEE Std 1920.1 does not specify the size, maximum take-off weight (MTOW), modes of propulsion, and other characteristics of the UAS. It is expected that most UASs with less than 250 kg MTOW can use the protocols defined in IEEE Std 1920.1. An MTOW above 250 kg would put the UAS in the scope of certification requirements that impose requirements beyond those applicable to aircraft operating communications services within the scope of IEEE Std 1920.1.<br />\n
          IEEE Std 1920.1 can contribute to aviation safety by providing for enhancing situational awareness of manned and unmanned aircraft in the shared airspace through air-to-air communications facilitated by an aerial ad hoc network. As UASs become increasingly integrated into the National Airspace (NAS), there is a corresponding need for technology systems to provide enhanced situational awareness of all aircraft operating in the shared airspace. IEEE Std 1920.1 also provides a means of compliance for the network remote identification of unmanned aircraft systems, to provide information to distinguish compliant UAS users from those potentially posing aviation security risk. The need for self-organized aerial networks in increasing the situational awareness of aircraft systems was highlighted in a working paper titled “Use of Self-organizing Airborne Networks to Monitor Commercial Aircraft Globally” presented in a May 2014 meeting of the International Civil Aviation Organization (ICAO) (see ADS-B in Europe (B1)).
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Aerial Network Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95877 …}
    #channels: Doctrine\ORM\PersistentCollection {#95883 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95879 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95881 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95869 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95864
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1685311200 {#95865
      date: 2023-05-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1682373600 {#95866
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1682373600 {#95867
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1920.1"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#95871 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95873 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#98895
  +product: App\Entity\Product\Product {#95868
    #id: 12636
    #code: "IEEE00010352"
    #attributes: Doctrine\ORM\PersistentCollection {#95885 …}
    #variants: Doctrine\ORM\PersistentCollection {#95887 …}
    #options: Doctrine\ORM\PersistentCollection {#95891 …}
    #associations: Doctrine\ORM\PersistentCollection {#95889 …}
    #createdAt: DateTime @1751040562 {#95862
      date: 2025-06-27 18:09:22.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95863
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95875 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98807
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95868}
        #id: 45553
        #name: "IEEE 1920.1:2022"
        #slug: "ieee-1920-1-2022-ieee00010352-244291"
        #description: """
          New IEEE Standard - Active.<br />\n
          IEEE Std 1920.1 defines air-to-air communications for self-organized ad hoc aerial networks. It outlines the network service architecture, security framework, and data model. IEEE Std 1920.1 is agnostic to the type of network (Wireless or Cellular or other) and it is applicable to manned and unmanned, small and large, and civil and commercial aircraft systems. IEEE Std 1920.1 is the first in the series of IEEE P1920.X standards. It is anticipated that IEEE Std 1920.1 will be used as a foundation to define more specific standards in this series.<br />\n
          \t\t\t\t<br />\n
          IEEE Std 1920.1 defines air-to-air communications over self-organized aerial ad hoc networks and describes the reference architecture for aerial networks, where aircraft can form a network to share information with one another with or without any supporting infrastructure, such as satellite or cellular communications. This standard is intended for RLOS and BRLOS small UASs used for civil and commercial applications. The architecture can also be extended to include additional platforms, making it a useful guide for other aircraft systems. The communications and networking standards are independent of the type of network (wireless, cellular, or other). The main objective of the IEEE Std 1920.1 data model is to define and format data consistently in a common, secure data structure that can be leveraged across the industry. This can help improve the integrity, safety, and security of the data regardless of the types of use cases, communication technologies, or diversity of the vehicles utilized. IEEE Std 1920.1 does not specify procedures or protocols that define the means to access radio-frequency spectrum and manage its use (i.e., an “air interface”). IEEE Std 1920.1 does not specify the size, maximum take-off weight (MTOW), modes of propulsion, and other characteristics of the UAS. It is expected that most UASs with less than 250 kg MTOW can use the protocols defined in IEEE Std 1920.1. An MTOW above 250 kg would put the UAS in the scope of certification requirements that impose requirements beyond those applicable to aircraft operating communications services within the scope of IEEE Std 1920.1.<br />\n
          IEEE Std 1920.1 can contribute to aviation safety by providing for enhancing situational awareness of manned and unmanned aircraft in the shared airspace through air-to-air communications facilitated by an aerial ad hoc network. As UASs become increasingly integrated into the National Airspace (NAS), there is a corresponding need for technology systems to provide enhanced situational awareness of all aircraft operating in the shared airspace. IEEE Std 1920.1 also provides a means of compliance for the network remote identification of unmanned aircraft systems, to provide information to distinguish compliant UAS users from those potentially posing aviation security risk. The need for self-organized aerial networks in increasing the situational awareness of aircraft systems was highlighted in a working paper titled “Use of Self-organizing Airborne Networks to Monitor Commercial Aircraft Globally” presented in a May 2014 meeting of the International Civil Aviation Organization (ICAO) (see ADS-B in Europe (B1)).
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Trial-Use Standard for Aerial Network Communication"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95877 …}
    #channels: Doctrine\ORM\PersistentCollection {#95883 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95879 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95881 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95869 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95864
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1685311200 {#95865
      date: 2023-05-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1682373600 {#95866
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1682373600 {#95867
      date: 2023-04-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1920.1"
    -bookCollection: ""
    -pageCount: 86
    -documents: Doctrine\ORM\PersistentCollection {#95871 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95873 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 8.78 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95898
    #id: 12639
    #code: "IEEE00010357"
    #attributes: Doctrine\ORM\PersistentCollection {#95915 …}
    #variants: Doctrine\ORM\PersistentCollection {#95917 …}
    #options: Doctrine\ORM\PersistentCollection {#95921 …}
    #associations: Doctrine\ORM\PersistentCollection {#95919 …}
    #createdAt: DateTime @1751040564 {#95893
      date: 2025-06-27 18:09:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95894
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95905 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99037
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95898}
        #id: 45565
        #name: "IEEE 2411:2021"
        #slug: "ieee-2411-2021-ieee00010357-244294"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance to prepare, plan, and conduct human factors performance-based validation of a component, sub-system, or system prior to its placement in-service, to assess reasonable confidence of compliance with functional and operational requirements is provided in this document. (An errata is available at https://standards.ieee.org/wp-content/uploads/2022/04/2411-2021_errata.pdf)<br />\n
          \t\t\t\t<br />\n
          This document provides human factors engineering guidance for the validation of the system interface design and the integrated systems operations. This guidance identifies general validation principles and provides acceptable means to:<br />\n
          - Define methods<br />\n
          - Plan and conduct validation activities<br />\n
          - Conduct single or multi-staged validation<br />\n
          The purpose of this document is to provide guidance that can be used by nuclear facility designers, applicants, licensees, architects/engineers, and regulators to establish reasonable confidence that a system can be safely and effectively operated by personnel during conditions under which the facility is expected to operate during the facility’s lifetime.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Human Factors Engineering for the Validation of System Designs and Integrated Systems Operations at Nuclear Facilities"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95907 …}
    #channels: Doctrine\ORM\PersistentCollection {#95913 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95909 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95911 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95899 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95895
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1649023200 {#95896
      date: 2022-04-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1642633200 {#95897
      date: 2022-01-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2411"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#95901 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95903 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#99017
  +product: App\Entity\Product\Product {#95898
    #id: 12639
    #code: "IEEE00010357"
    #attributes: Doctrine\ORM\PersistentCollection {#95915 …}
    #variants: Doctrine\ORM\PersistentCollection {#95917 …}
    #options: Doctrine\ORM\PersistentCollection {#95921 …}
    #associations: Doctrine\ORM\PersistentCollection {#95919 …}
    #createdAt: DateTime @1751040564 {#95893
      date: 2025-06-27 18:09:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95894
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95905 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99037
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95898}
        #id: 45565
        #name: "IEEE 2411:2021"
        #slug: "ieee-2411-2021-ieee00010357-244294"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance to prepare, plan, and conduct human factors performance-based validation of a component, sub-system, or system prior to its placement in-service, to assess reasonable confidence of compliance with functional and operational requirements is provided in this document. (An errata is available at https://standards.ieee.org/wp-content/uploads/2022/04/2411-2021_errata.pdf)<br />\n
          \t\t\t\t<br />\n
          This document provides human factors engineering guidance for the validation of the system interface design and the integrated systems operations. This guidance identifies general validation principles and provides acceptable means to:<br />\n
          - Define methods<br />\n
          - Plan and conduct validation activities<br />\n
          - Conduct single or multi-staged validation<br />\n
          The purpose of this document is to provide guidance that can be used by nuclear facility designers, applicants, licensees, architects/engineers, and regulators to establish reasonable confidence that a system can be safely and effectively operated by personnel during conditions under which the facility is expected to operate during the facility’s lifetime.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Human Factors Engineering for the Validation of System Designs and Integrated Systems Operations at Nuclear Facilities"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95907 …}
    #channels: Doctrine\ORM\PersistentCollection {#95913 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95909 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95911 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95899 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95895
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1649023200 {#95896
      date: 2022-04-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1642633200 {#95897
      date: 2022-01-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2411"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#95901 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95903 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.21 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95898
    #id: 12639
    #code: "IEEE00010357"
    #attributes: Doctrine\ORM\PersistentCollection {#95915 …}
    #variants: Doctrine\ORM\PersistentCollection {#95917 …}
    #options: Doctrine\ORM\PersistentCollection {#95921 …}
    #associations: Doctrine\ORM\PersistentCollection {#95919 …}
    #createdAt: DateTime @1751040564 {#95893
      date: 2025-06-27 18:09:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95894
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95905 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99037
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95898}
        #id: 45565
        #name: "IEEE 2411:2021"
        #slug: "ieee-2411-2021-ieee00010357-244294"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance to prepare, plan, and conduct human factors performance-based validation of a component, sub-system, or system prior to its placement in-service, to assess reasonable confidence of compliance with functional and operational requirements is provided in this document. (An errata is available at https://standards.ieee.org/wp-content/uploads/2022/04/2411-2021_errata.pdf)<br />\n
          \t\t\t\t<br />\n
          This document provides human factors engineering guidance for the validation of the system interface design and the integrated systems operations. This guidance identifies general validation principles and provides acceptable means to:<br />\n
          - Define methods<br />\n
          - Plan and conduct validation activities<br />\n
          - Conduct single or multi-staged validation<br />\n
          The purpose of this document is to provide guidance that can be used by nuclear facility designers, applicants, licensees, architects/engineers, and regulators to establish reasonable confidence that a system can be safely and effectively operated by personnel during conditions under which the facility is expected to operate during the facility’s lifetime.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Human Factors Engineering for the Validation of System Designs and Integrated Systems Operations at Nuclear Facilities"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95907 …}
    #channels: Doctrine\ORM\PersistentCollection {#95913 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95909 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95911 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95899 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95895
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1649023200 {#95896
      date: 2022-04-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1642633200 {#95897
      date: 2022-01-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2411"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#95901 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95903 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#99051
  +product: App\Entity\Product\Product {#95898
    #id: 12639
    #code: "IEEE00010357"
    #attributes: Doctrine\ORM\PersistentCollection {#95915 …}
    #variants: Doctrine\ORM\PersistentCollection {#95917 …}
    #options: Doctrine\ORM\PersistentCollection {#95921 …}
    #associations: Doctrine\ORM\PersistentCollection {#95919 …}
    #createdAt: DateTime @1751040564 {#95893
      date: 2025-06-27 18:09:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95894
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95905 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99037
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95898}
        #id: 45565
        #name: "IEEE 2411:2021"
        #slug: "ieee-2411-2021-ieee00010357-244294"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance to prepare, plan, and conduct human factors performance-based validation of a component, sub-system, or system prior to its placement in-service, to assess reasonable confidence of compliance with functional and operational requirements is provided in this document. (An errata is available at https://standards.ieee.org/wp-content/uploads/2022/04/2411-2021_errata.pdf)<br />\n
          \t\t\t\t<br />\n
          This document provides human factors engineering guidance for the validation of the system interface design and the integrated systems operations. This guidance identifies general validation principles and provides acceptable means to:<br />\n
          - Define methods<br />\n
          - Plan and conduct validation activities<br />\n
          - Conduct single or multi-staged validation<br />\n
          The purpose of this document is to provide guidance that can be used by nuclear facility designers, applicants, licensees, architects/engineers, and regulators to establish reasonable confidence that a system can be safely and effectively operated by personnel during conditions under which the facility is expected to operate during the facility’s lifetime.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Human Factors Engineering for the Validation of System Designs and Integrated Systems Operations at Nuclear Facilities"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95907 …}
    #channels: Doctrine\ORM\PersistentCollection {#95913 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95909 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95911 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95899 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95895
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1649023200 {#95896
      date: 2022-04-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1642633200 {#95897
      date: 2022-01-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2411"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#95901 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95903 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.97 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95898
    #id: 12639
    #code: "IEEE00010357"
    #attributes: Doctrine\ORM\PersistentCollection {#95915 …}
    #variants: Doctrine\ORM\PersistentCollection {#95917 …}
    #options: Doctrine\ORM\PersistentCollection {#95921 …}
    #associations: Doctrine\ORM\PersistentCollection {#95919 …}
    #createdAt: DateTime @1751040564 {#95893
      date: 2025-06-27 18:09:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95894
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95905 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99037
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95898}
        #id: 45565
        #name: "IEEE 2411:2021"
        #slug: "ieee-2411-2021-ieee00010357-244294"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance to prepare, plan, and conduct human factors performance-based validation of a component, sub-system, or system prior to its placement in-service, to assess reasonable confidence of compliance with functional and operational requirements is provided in this document. (An errata is available at https://standards.ieee.org/wp-content/uploads/2022/04/2411-2021_errata.pdf)<br />\n
          \t\t\t\t<br />\n
          This document provides human factors engineering guidance for the validation of the system interface design and the integrated systems operations. This guidance identifies general validation principles and provides acceptable means to:<br />\n
          - Define methods<br />\n
          - Plan and conduct validation activities<br />\n
          - Conduct single or multi-staged validation<br />\n
          The purpose of this document is to provide guidance that can be used by nuclear facility designers, applicants, licensees, architects/engineers, and regulators to establish reasonable confidence that a system can be safely and effectively operated by personnel during conditions under which the facility is expected to operate during the facility’s lifetime.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Human Factors Engineering for the Validation of System Designs and Integrated Systems Operations at Nuclear Facilities"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95907 …}
    #channels: Doctrine\ORM\PersistentCollection {#95913 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95909 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95911 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95899 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95895
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1649023200 {#95896
      date: 2022-04-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1642633200 {#95897
      date: 2022-01-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2411"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#95901 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95903 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#99125
  +product: App\Entity\Product\Product {#95898
    #id: 12639
    #code: "IEEE00010357"
    #attributes: Doctrine\ORM\PersistentCollection {#95915 …}
    #variants: Doctrine\ORM\PersistentCollection {#95917 …}
    #options: Doctrine\ORM\PersistentCollection {#95921 …}
    #associations: Doctrine\ORM\PersistentCollection {#95919 …}
    #createdAt: DateTime @1751040564 {#95893
      date: 2025-06-27 18:09:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#95894
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95905 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99037
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95898}
        #id: 45565
        #name: "IEEE 2411:2021"
        #slug: "ieee-2411-2021-ieee00010357-244294"
        #description: """
          New IEEE Standard - Active.<br />\n
          Guidance to prepare, plan, and conduct human factors performance-based validation of a component, sub-system, or system prior to its placement in-service, to assess reasonable confidence of compliance with functional and operational requirements is provided in this document. (An errata is available at https://standards.ieee.org/wp-content/uploads/2022/04/2411-2021_errata.pdf)<br />\n
          \t\t\t\t<br />\n
          This document provides human factors engineering guidance for the validation of the system interface design and the integrated systems operations. This guidance identifies general validation principles and provides acceptable means to:<br />\n
          - Define methods<br />\n
          - Plan and conduct validation activities<br />\n
          - Conduct single or multi-staged validation<br />\n
          The purpose of this document is to provide guidance that can be used by nuclear facility designers, applicants, licensees, architects/engineers, and regulators to establish reasonable confidence that a system can be safely and effectively operated by personnel during conditions under which the facility is expected to operate during the facility’s lifetime.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Human Factors Engineering for the Validation of System Designs and Integrated Systems Operations at Nuclear Facilities"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95907 …}
    #channels: Doctrine\ORM\PersistentCollection {#95913 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95909 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95911 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95899 …}
    -apiLastModifiedAt: DateTime @1743289200 {#95895
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1649023200 {#95896
      date: 2022-04-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1642633200 {#95897
      date: 2022-01-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2411"
    -bookCollection: ""
    -pageCount: 38
    -documents: Doctrine\ORM\PersistentCollection {#95901 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95903 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 7.07 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95928
    #id: 12641
    #code: "IEEE00010359"
    #attributes: Doctrine\ORM\PersistentCollection {#95945 …}
    #variants: Doctrine\ORM\PersistentCollection {#95947 …}
    #options: Doctrine\ORM\PersistentCollection {#95951 …}
    #associations: Doctrine\ORM\PersistentCollection {#95949 …}
    #createdAt: DateTime @1751040565 {#95923
      date: 2025-06-27 18:09:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95924
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95935 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99275
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95928}
        #id: 45573
        #name: "IEEE 2777:2021"
        #slug: "ieee-2777-2021-ieee00010359-244296"
        #description: """
          New IEEE Standard - Active.<br />\n
          General technical recommended practice for operation of pulverized coal-fired boilers in power plants is provided, including start-up, shutdown, operation and maintenance, and emergency and failure detection/handling/prevention. In this document, a boiler with existing single units with a capacity of 300 MW to 600 MW in thermal power plants, where pulverized coal is combusted to generate electricity and/or to supply heat, is discussed. Development of boiler operation code as a reference to determine detailed operation steps and/or procedures for a particular boiler in the plant is outlined. The specifications of manufacturers, successful experiences from practice, and stipulations defined in other related high-level standards/regulations/codes are also considered.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the principles and procedures for start-up, normal operation, shutdown, daily operation, and maintenance during normal and emergency conditions for a 300 MW to 600 MW pulverized coal-fired boiler and its main auxiliary equipment. This recommended practice applies to 300 MW to 600 MW pulverized coal-fired boilers with a balanced draft, including natural circulation and forced circulation; subcritical and supercritical once-through boilers; tangential-fired boilers; opposed-fired boilers; and so on. For specific applications, an additional document needs to be formulated by users based on this recommended practice to cover detailed procedures or normally so-called “operation code,” together with the instructions of manufacturers and the experiences derived from normal operation practice.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Operation of 300 MW to 600 MW Pulverized Coal-Fired Boiler"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95937 …}
    #channels: Doctrine\ORM\PersistentCollection {#95943 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95939 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95941 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95929 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95925
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1621807200 {#95926
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1619733600 {#95927
      date: 2021-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2777"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#95931 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95933 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#99255
  +product: App\Entity\Product\Product {#95928
    #id: 12641
    #code: "IEEE00010359"
    #attributes: Doctrine\ORM\PersistentCollection {#95945 …}
    #variants: Doctrine\ORM\PersistentCollection {#95947 …}
    #options: Doctrine\ORM\PersistentCollection {#95951 …}
    #associations: Doctrine\ORM\PersistentCollection {#95949 …}
    #createdAt: DateTime @1751040565 {#95923
      date: 2025-06-27 18:09:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95924
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95935 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99275
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95928}
        #id: 45573
        #name: "IEEE 2777:2021"
        #slug: "ieee-2777-2021-ieee00010359-244296"
        #description: """
          New IEEE Standard - Active.<br />\n
          General technical recommended practice for operation of pulverized coal-fired boilers in power plants is provided, including start-up, shutdown, operation and maintenance, and emergency and failure detection/handling/prevention. In this document, a boiler with existing single units with a capacity of 300 MW to 600 MW in thermal power plants, where pulverized coal is combusted to generate electricity and/or to supply heat, is discussed. Development of boiler operation code as a reference to determine detailed operation steps and/or procedures for a particular boiler in the plant is outlined. The specifications of manufacturers, successful experiences from practice, and stipulations defined in other related high-level standards/regulations/codes are also considered.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the principles and procedures for start-up, normal operation, shutdown, daily operation, and maintenance during normal and emergency conditions for a 300 MW to 600 MW pulverized coal-fired boiler and its main auxiliary equipment. This recommended practice applies to 300 MW to 600 MW pulverized coal-fired boilers with a balanced draft, including natural circulation and forced circulation; subcritical and supercritical once-through boilers; tangential-fired boilers; opposed-fired boilers; and so on. For specific applications, an additional document needs to be formulated by users based on this recommended practice to cover detailed procedures or normally so-called “operation code,” together with the instructions of manufacturers and the experiences derived from normal operation practice.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Operation of 300 MW to 600 MW Pulverized Coal-Fired Boiler"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95937 …}
    #channels: Doctrine\ORM\PersistentCollection {#95943 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95939 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95941 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95929 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95925
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1621807200 {#95926
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1619733600 {#95927
      date: 2021-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2777"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#95931 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95933 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95928
    #id: 12641
    #code: "IEEE00010359"
    #attributes: Doctrine\ORM\PersistentCollection {#95945 …}
    #variants: Doctrine\ORM\PersistentCollection {#95947 …}
    #options: Doctrine\ORM\PersistentCollection {#95951 …}
    #associations: Doctrine\ORM\PersistentCollection {#95949 …}
    #createdAt: DateTime @1751040565 {#95923
      date: 2025-06-27 18:09:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95924
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95935 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99275
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95928}
        #id: 45573
        #name: "IEEE 2777:2021"
        #slug: "ieee-2777-2021-ieee00010359-244296"
        #description: """
          New IEEE Standard - Active.<br />\n
          General technical recommended practice for operation of pulverized coal-fired boilers in power plants is provided, including start-up, shutdown, operation and maintenance, and emergency and failure detection/handling/prevention. In this document, a boiler with existing single units with a capacity of 300 MW to 600 MW in thermal power plants, where pulverized coal is combusted to generate electricity and/or to supply heat, is discussed. Development of boiler operation code as a reference to determine detailed operation steps and/or procedures for a particular boiler in the plant is outlined. The specifications of manufacturers, successful experiences from practice, and stipulations defined in other related high-level standards/regulations/codes are also considered.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the principles and procedures for start-up, normal operation, shutdown, daily operation, and maintenance during normal and emergency conditions for a 300 MW to 600 MW pulverized coal-fired boiler and its main auxiliary equipment. This recommended practice applies to 300 MW to 600 MW pulverized coal-fired boilers with a balanced draft, including natural circulation and forced circulation; subcritical and supercritical once-through boilers; tangential-fired boilers; opposed-fired boilers; and so on. For specific applications, an additional document needs to be formulated by users based on this recommended practice to cover detailed procedures or normally so-called “operation code,” together with the instructions of manufacturers and the experiences derived from normal operation practice.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Operation of 300 MW to 600 MW Pulverized Coal-Fired Boiler"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95937 …}
    #channels: Doctrine\ORM\PersistentCollection {#95943 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95939 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95941 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95929 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95925
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1621807200 {#95926
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1619733600 {#95927
      date: 2021-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2777"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#95931 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95933 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#99289
  +product: App\Entity\Product\Product {#95928
    #id: 12641
    #code: "IEEE00010359"
    #attributes: Doctrine\ORM\PersistentCollection {#95945 …}
    #variants: Doctrine\ORM\PersistentCollection {#95947 …}
    #options: Doctrine\ORM\PersistentCollection {#95951 …}
    #associations: Doctrine\ORM\PersistentCollection {#95949 …}
    #createdAt: DateTime @1751040565 {#95923
      date: 2025-06-27 18:09:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95924
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95935 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99275
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95928}
        #id: 45573
        #name: "IEEE 2777:2021"
        #slug: "ieee-2777-2021-ieee00010359-244296"
        #description: """
          New IEEE Standard - Active.<br />\n
          General technical recommended practice for operation of pulverized coal-fired boilers in power plants is provided, including start-up, shutdown, operation and maintenance, and emergency and failure detection/handling/prevention. In this document, a boiler with existing single units with a capacity of 300 MW to 600 MW in thermal power plants, where pulverized coal is combusted to generate electricity and/or to supply heat, is discussed. Development of boiler operation code as a reference to determine detailed operation steps and/or procedures for a particular boiler in the plant is outlined. The specifications of manufacturers, successful experiences from practice, and stipulations defined in other related high-level standards/regulations/codes are also considered.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the principles and procedures for start-up, normal operation, shutdown, daily operation, and maintenance during normal and emergency conditions for a 300 MW to 600 MW pulverized coal-fired boiler and its main auxiliary equipment. This recommended practice applies to 300 MW to 600 MW pulverized coal-fired boilers with a balanced draft, including natural circulation and forced circulation; subcritical and supercritical once-through boilers; tangential-fired boilers; opposed-fired boilers; and so on. For specific applications, an additional document needs to be formulated by users based on this recommended practice to cover detailed procedures or normally so-called “operation code,” together with the instructions of manufacturers and the experiences derived from normal operation practice.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Operation of 300 MW to 600 MW Pulverized Coal-Fired Boiler"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95937 …}
    #channels: Doctrine\ORM\PersistentCollection {#95943 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95939 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95941 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95929 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95925
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1621807200 {#95926
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1619733600 {#95927
      date: 2021-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2777"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#95931 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95933 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.67 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95928
    #id: 12641
    #code: "IEEE00010359"
    #attributes: Doctrine\ORM\PersistentCollection {#95945 …}
    #variants: Doctrine\ORM\PersistentCollection {#95947 …}
    #options: Doctrine\ORM\PersistentCollection {#95951 …}
    #associations: Doctrine\ORM\PersistentCollection {#95949 …}
    #createdAt: DateTime @1751040565 {#95923
      date: 2025-06-27 18:09:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95924
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95935 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99275
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95928}
        #id: 45573
        #name: "IEEE 2777:2021"
        #slug: "ieee-2777-2021-ieee00010359-244296"
        #description: """
          New IEEE Standard - Active.<br />\n
          General technical recommended practice for operation of pulverized coal-fired boilers in power plants is provided, including start-up, shutdown, operation and maintenance, and emergency and failure detection/handling/prevention. In this document, a boiler with existing single units with a capacity of 300 MW to 600 MW in thermal power plants, where pulverized coal is combusted to generate electricity and/or to supply heat, is discussed. Development of boiler operation code as a reference to determine detailed operation steps and/or procedures for a particular boiler in the plant is outlined. The specifications of manufacturers, successful experiences from practice, and stipulations defined in other related high-level standards/regulations/codes are also considered.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the principles and procedures for start-up, normal operation, shutdown, daily operation, and maintenance during normal and emergency conditions for a 300 MW to 600 MW pulverized coal-fired boiler and its main auxiliary equipment. This recommended practice applies to 300 MW to 600 MW pulverized coal-fired boilers with a balanced draft, including natural circulation and forced circulation; subcritical and supercritical once-through boilers; tangential-fired boilers; opposed-fired boilers; and so on. For specific applications, an additional document needs to be formulated by users based on this recommended practice to cover detailed procedures or normally so-called “operation code,” together with the instructions of manufacturers and the experiences derived from normal operation practice.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Operation of 300 MW to 600 MW Pulverized Coal-Fired Boiler"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95937 …}
    #channels: Doctrine\ORM\PersistentCollection {#95943 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95939 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95941 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95929 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95925
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1621807200 {#95926
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1619733600 {#95927
      date: 2021-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2777"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#95931 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95933 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#99363
  +product: App\Entity\Product\Product {#95928
    #id: 12641
    #code: "IEEE00010359"
    #attributes: Doctrine\ORM\PersistentCollection {#95945 …}
    #variants: Doctrine\ORM\PersistentCollection {#95947 …}
    #options: Doctrine\ORM\PersistentCollection {#95951 …}
    #associations: Doctrine\ORM\PersistentCollection {#95949 …}
    #createdAt: DateTime @1751040565 {#95923
      date: 2025-06-27 18:09:25.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95924
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95935 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99275
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95928}
        #id: 45573
        #name: "IEEE 2777:2021"
        #slug: "ieee-2777-2021-ieee00010359-244296"
        #description: """
          New IEEE Standard - Active.<br />\n
          General technical recommended practice for operation of pulverized coal-fired boilers in power plants is provided, including start-up, shutdown, operation and maintenance, and emergency and failure detection/handling/prevention. In this document, a boiler with existing single units with a capacity of 300 MW to 600 MW in thermal power plants, where pulverized coal is combusted to generate electricity and/or to supply heat, is discussed. Development of boiler operation code as a reference to determine detailed operation steps and/or procedures for a particular boiler in the plant is outlined. The specifications of manufacturers, successful experiences from practice, and stipulations defined in other related high-level standards/regulations/codes are also considered.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the principles and procedures for start-up, normal operation, shutdown, daily operation, and maintenance during normal and emergency conditions for a 300 MW to 600 MW pulverized coal-fired boiler and its main auxiliary equipment. This recommended practice applies to 300 MW to 600 MW pulverized coal-fired boilers with a balanced draft, including natural circulation and forced circulation; subcritical and supercritical once-through boilers; tangential-fired boilers; opposed-fired boilers; and so on. For specific applications, an additional document needs to be formulated by users based on this recommended practice to cover detailed procedures or normally so-called “operation code,” together with the instructions of manufacturers and the experiences derived from normal operation practice.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Operation of 300 MW to 600 MW Pulverized Coal-Fired Boiler"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95937 …}
    #channels: Doctrine\ORM\PersistentCollection {#95943 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95939 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95941 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95929 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95925
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1621807200 {#95926
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1619733600 {#95927
      date: 2021-04-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2777"
    -bookCollection: ""
    -pageCount: 74
    -documents: Doctrine\ORM\PersistentCollection {#95931 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95933 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductCard App\Twig\Components\ProductCard 258.0 MiB 6.40 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95959
    #id: 12642
    #code: "IEEE00010360"
    #attributes: Doctrine\ORM\PersistentCollection {#95976 …}
    #variants: Doctrine\ORM\PersistentCollection {#95978 …}
    #options: Doctrine\ORM\PersistentCollection {#95982 …}
    #associations: Doctrine\ORM\PersistentCollection {#95980 …}
    #createdAt: DateTime @1751040566 {#95953
      date: 2025-06-27 18:09:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95954
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95966 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99513
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95959}
        #id: 45577
        #name: "IEEE 1609.3:2020"
        #slug: "ieee-1609-3-2020-ieee00010360-244297"
        #description: """
          Revision Standard - Active.<br />\n
          Services to WAVE devices and systems are provided. Layer 3 and layer 4 of the open system interconnect (OSI) model and the Internet Protocol (IP), User Datagram Protocol (UDP), and Transmission Control Protocol (TCP) elements of the Internet model are represented. Management and data services within WAVE devices are provided.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is to define services, operating at the network and transport layers, in support of wireless connectivity among vehicles, roadside devices, and Intelligent Transportation Systems (ITS) devices. The scope also includes aspects of the corresponding architecture related to the use of lower layer underlying wireless communication technologies.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)--Networking Services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95968 …}
    #channels: Doctrine\ORM\PersistentCollection {#95974 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95970 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95972 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95960 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95955
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1730329200 {#95956
      date: 2024-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1615244400 {#95957
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1615244400 {#95958
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.3"
    -bookCollection: ""
    -pageCount: 210
    -documents: Doctrine\ORM\PersistentCollection {#95962 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95964 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#99493
  +product: App\Entity\Product\Product {#95959
    #id: 12642
    #code: "IEEE00010360"
    #attributes: Doctrine\ORM\PersistentCollection {#95976 …}
    #variants: Doctrine\ORM\PersistentCollection {#95978 …}
    #options: Doctrine\ORM\PersistentCollection {#95982 …}
    #associations: Doctrine\ORM\PersistentCollection {#95980 …}
    #createdAt: DateTime @1751040566 {#95953
      date: 2025-06-27 18:09:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95954
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95966 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99513
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95959}
        #id: 45577
        #name: "IEEE 1609.3:2020"
        #slug: "ieee-1609-3-2020-ieee00010360-244297"
        #description: """
          Revision Standard - Active.<br />\n
          Services to WAVE devices and systems are provided. Layer 3 and layer 4 of the open system interconnect (OSI) model and the Internet Protocol (IP), User Datagram Protocol (UDP), and Transmission Control Protocol (TCP) elements of the Internet model are represented. Management and data services within WAVE devices are provided.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is to define services, operating at the network and transport layers, in support of wireless connectivity among vehicles, roadside devices, and Intelligent Transportation Systems (ITS) devices. The scope also includes aspects of the corresponding architecture related to the use of lower layer underlying wireless communication technologies.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)--Networking Services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95968 …}
    #channels: Doctrine\ORM\PersistentCollection {#95974 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95970 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95972 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95960 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95955
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1730329200 {#95956
      date: 2024-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1615244400 {#95957
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1615244400 {#95958
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.3"
    -bookCollection: ""
    -pageCount: 210
    -documents: Doctrine\ORM\PersistentCollection {#95962 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95964 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 258.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95959
    #id: 12642
    #code: "IEEE00010360"
    #attributes: Doctrine\ORM\PersistentCollection {#95976 …}
    #variants: Doctrine\ORM\PersistentCollection {#95978 …}
    #options: Doctrine\ORM\PersistentCollection {#95982 …}
    #associations: Doctrine\ORM\PersistentCollection {#95980 …}
    #createdAt: DateTime @1751040566 {#95953
      date: 2025-06-27 18:09:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95954
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95966 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99513
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95959}
        #id: 45577
        #name: "IEEE 1609.3:2020"
        #slug: "ieee-1609-3-2020-ieee00010360-244297"
        #description: """
          Revision Standard - Active.<br />\n
          Services to WAVE devices and systems are provided. Layer 3 and layer 4 of the open system interconnect (OSI) model and the Internet Protocol (IP), User Datagram Protocol (UDP), and Transmission Control Protocol (TCP) elements of the Internet model are represented. Management and data services within WAVE devices are provided.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is to define services, operating at the network and transport layers, in support of wireless connectivity among vehicles, roadside devices, and Intelligent Transportation Systems (ITS) devices. The scope also includes aspects of the corresponding architecture related to the use of lower layer underlying wireless communication technologies.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)--Networking Services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95968 …}
    #channels: Doctrine\ORM\PersistentCollection {#95974 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95970 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95972 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95960 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95955
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1730329200 {#95956
      date: 2024-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1615244400 {#95957
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1615244400 {#95958
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.3"
    -bookCollection: ""
    -pageCount: 210
    -documents: Doctrine\ORM\PersistentCollection {#95962 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95964 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#99531
  +product: App\Entity\Product\Product {#95959
    #id: 12642
    #code: "IEEE00010360"
    #attributes: Doctrine\ORM\PersistentCollection {#95976 …}
    #variants: Doctrine\ORM\PersistentCollection {#95978 …}
    #options: Doctrine\ORM\PersistentCollection {#95982 …}
    #associations: Doctrine\ORM\PersistentCollection {#95980 …}
    #createdAt: DateTime @1751040566 {#95953
      date: 2025-06-27 18:09:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95954
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95966 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99513
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95959}
        #id: 45577
        #name: "IEEE 1609.3:2020"
        #slug: "ieee-1609-3-2020-ieee00010360-244297"
        #description: """
          Revision Standard - Active.<br />\n
          Services to WAVE devices and systems are provided. Layer 3 and layer 4 of the open system interconnect (OSI) model and the Internet Protocol (IP), User Datagram Protocol (UDP), and Transmission Control Protocol (TCP) elements of the Internet model are represented. Management and data services within WAVE devices are provided.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is to define services, operating at the network and transport layers, in support of wireless connectivity among vehicles, roadside devices, and Intelligent Transportation Systems (ITS) devices. The scope also includes aspects of the corresponding architecture related to the use of lower layer underlying wireless communication technologies.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)--Networking Services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95968 …}
    #channels: Doctrine\ORM\PersistentCollection {#95974 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95970 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95972 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95960 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95955
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1730329200 {#95956
      date: 2024-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1615244400 {#95957
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1615244400 {#95958
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.3"
    -bookCollection: ""
    -pageCount: 210
    -documents: Doctrine\ORM\PersistentCollection {#95962 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95964 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 258.0 MiB 0.68 ms
Input props 
[
  "product" => App\Entity\Product\Product {#95959
    #id: 12642
    #code: "IEEE00010360"
    #attributes: Doctrine\ORM\PersistentCollection {#95976 …}
    #variants: Doctrine\ORM\PersistentCollection {#95978 …}
    #options: Doctrine\ORM\PersistentCollection {#95982 …}
    #associations: Doctrine\ORM\PersistentCollection {#95980 …}
    #createdAt: DateTime @1751040566 {#95953
      date: 2025-06-27 18:09:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95954
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95966 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99513
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95959}
        #id: 45577
        #name: "IEEE 1609.3:2020"
        #slug: "ieee-1609-3-2020-ieee00010360-244297"
        #description: """
          Revision Standard - Active.<br />\n
          Services to WAVE devices and systems are provided. Layer 3 and layer 4 of the open system interconnect (OSI) model and the Internet Protocol (IP), User Datagram Protocol (UDP), and Transmission Control Protocol (TCP) elements of the Internet model are represented. Management and data services within WAVE devices are provided.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is to define services, operating at the network and transport layers, in support of wireless connectivity among vehicles, roadside devices, and Intelligent Transportation Systems (ITS) devices. The scope also includes aspects of the corresponding architecture related to the use of lower layer underlying wireless communication technologies.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)--Networking Services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95968 …}
    #channels: Doctrine\ORM\PersistentCollection {#95974 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95970 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95972 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95960 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95955
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1730329200 {#95956
      date: 2024-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1615244400 {#95957
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1615244400 {#95958
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.3"
    -bookCollection: ""
    -pageCount: 210
    -documents: Doctrine\ORM\PersistentCollection {#95962 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95964 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#99605
  +product: App\Entity\Product\Product {#95959
    #id: 12642
    #code: "IEEE00010360"
    #attributes: Doctrine\ORM\PersistentCollection {#95976 …}
    #variants: Doctrine\ORM\PersistentCollection {#95978 …}
    #options: Doctrine\ORM\PersistentCollection {#95982 …}
    #associations: Doctrine\ORM\PersistentCollection {#95980 …}
    #createdAt: DateTime @1751040566 {#95953
      date: 2025-06-27 18:09:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95954
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95966 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#99513
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95959}
        #id: 45577
        #name: "IEEE 1609.3:2020"
        #slug: "ieee-1609-3-2020-ieee00010360-244297"
        #description: """
          Revision Standard - Active.<br />\n
          Services to WAVE devices and systems are provided. Layer 3 and layer 4 of the open system interconnect (OSI) model and the Internet Protocol (IP), User Datagram Protocol (UDP), and Transmission Control Protocol (TCP) elements of the Internet model are represented. Management and data services within WAVE devices are provided.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is to define services, operating at the network and transport layers, in support of wireless connectivity among vehicles, roadside devices, and Intelligent Transportation Systems (ITS) devices. The scope also includes aspects of the corresponding architecture related to the use of lower layer underlying wireless communication technologies.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)--Networking Services"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95968 …}
    #channels: Doctrine\ORM\PersistentCollection {#95974 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#52179 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95970 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95972 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95586 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95960 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95955
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1730329200 {#95956
      date: 2024-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1615244400 {#95957
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1615244400 {#95958
      date: 2021-03-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.3"
    -bookCollection: ""
    -pageCount: 210
    -documents: Doctrine\ORM\PersistentCollection {#95962 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95964 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}