Symfony Profiler

[
  "backLabel" => "43 : Road vehicles engineering"
  "backUrl" => "/taxons/main/ics-2277/43-road-vehicles-engineering-5715"
  "paddingClasses" => "p-2 px-lg-5 py-lg-0"
  "searchPlaceholder" => "sylius.ui.search"
  "showSearch" => "true"
  "title" => "43.040"
]

App\Twig\Components\PageBanner {#94278
  +supTitle: null
  +title: "43.040"
  +subTitle: null
  +backUrl: "/taxons/main/ics-2277/43-road-vehicles-engineering-5715"
  +backLabel: "43 : Road vehicles engineering"
  +customClasses: null
  +backgroundType: null
  +centered: true
  +showSearch: true
  +searchPlaceholder: "sylius.ui.search"
  +searchValue: null
  +paddingClasses: "p-2 px-lg-5 py-lg-0"
}

[
  "url" => "/taxons/main/ics-2277/43-road-vehicles-engineering-5715"
  "label" => "43 : Road vehicles engineering"
]

App\Twig\Components\BackButton {#94369
  +label: "43 : Road vehicles engineering"
  +url: "/taxons/main/ics-2277/43-road-vehicles-engineering-5715"
}

[
  "product" => App\Entity\Product\Product {#94885
    #id: 9368
    #code: "IEEE00002171"
    #attributes: Doctrine\ORM\PersistentCollection {#94950 …}
    #variants: Doctrine\ORM\PersistentCollection {#94948 …}
    #options: Doctrine\ORM\PersistentCollection {#94944 …}
    #associations: Doctrine\ORM\PersistentCollection {#94946 …}
    #createdAt: DateTime @1751038207 {#94865
      date: 2025-06-27 17:30:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94900
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94960 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95241
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94885}
        #id: 32481
        #name: "IEEE 1455:1999 (R2006)"
        #slug: "ieee-1455-1999-r2006-ieee00002171-241020"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          &quot; Those characteristics of a dedicated short-range communications (DSRC) system thetare independent of the Physical and Data Link Layers (ISO model Layers 1 and 2) are specified.The required and optional features of the roadside equipment (RSE) and the onboard equipment(OBE) are specified. In addition, the Applications Layer (ISO model Layer 7) services and protocols,the RSE resource manager, the corresponding OBE command interpreter, and the application-spe-cific messages are all specified. Standard supports and guidelines are provided for implementingsecure DSRC systems. &quot;<br />\n
          \t\t\t\t<br />\n
          Research, compile, and consolidate information leading to the publication of a standard for exchanging DSRC information, providing for bi-directional message transmission and device control, in a manner which is compatible with but independent of the ASTM efforts to specify DSRC Layers 1 and 2. This will entail specifying the transponder resources, the transponder resource manager, the application message sets, and the sighals and services such as the Electronic Toll and Traffic Mgmt User's Group, the ATA, the CVO community, the vendor community, and other standards bodies to synthesize existing messaging requirements into a single, open industry standard which supports non-interfereing and interoperable DSRC implementations by the various user agencies.<br />\n
          The ETTM field is rapidly emerging with multiple technologies and incompatible products. In addition, the emergence of the ASTM standard for Layers 1 and 2 has created the potential for significant interference between RF compatible systems. The lack of standard message sets, lower layer protocols, and transponder resource definitions threatens to postpone the deployment of this critical technology to the marketplace. The effort behind this PAR will consolidate and publish a standard to support Commercial Vehicle Operation and ETTM. The open nature of the developed interface will ensure that it is extensible to other DSRC areas, e.g. CVO credential information exchange, pre-clearance screening, fleet management and private messaging.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Sets for Vehicle/Roadside Communications"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94958 …}
    #channels: Doctrine\ORM\PersistentCollection {#94952 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94956 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94954 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94966 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94905
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94855
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @937692000 {#94898
      date: 1999-09-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1149717600 {#94904
      date: 2006-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1455"
    -bookCollection: ""
    -pageCount: 134
    -documents: Doctrine\ORM\PersistentCollection {#94964 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94962 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#95143
  +product: App\Entity\Product\Product {#94885
    #id: 9368
    #code: "IEEE00002171"
    #attributes: Doctrine\ORM\PersistentCollection {#94950 …}
    #variants: Doctrine\ORM\PersistentCollection {#94948 …}
    #options: Doctrine\ORM\PersistentCollection {#94944 …}
    #associations: Doctrine\ORM\PersistentCollection {#94946 …}
    #createdAt: DateTime @1751038207 {#94865
      date: 2025-06-27 17:30:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94900
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94960 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95241
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94885}
        #id: 32481
        #name: "IEEE 1455:1999 (R2006)"
        #slug: "ieee-1455-1999-r2006-ieee00002171-241020"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          &quot; Those characteristics of a dedicated short-range communications (DSRC) system thetare independent of the Physical and Data Link Layers (ISO model Layers 1 and 2) are specified.The required and optional features of the roadside equipment (RSE) and the onboard equipment(OBE) are specified. In addition, the Applications Layer (ISO model Layer 7) services and protocols,the RSE resource manager, the corresponding OBE command interpreter, and the application-spe-cific messages are all specified. Standard supports and guidelines are provided for implementingsecure DSRC systems. &quot;<br />\n
          \t\t\t\t<br />\n
          Research, compile, and consolidate information leading to the publication of a standard for exchanging DSRC information, providing for bi-directional message transmission and device control, in a manner which is compatible with but independent of the ASTM efforts to specify DSRC Layers 1 and 2. This will entail specifying the transponder resources, the transponder resource manager, the application message sets, and the sighals and services such as the Electronic Toll and Traffic Mgmt User's Group, the ATA, the CVO community, the vendor community, and other standards bodies to synthesize existing messaging requirements into a single, open industry standard which supports non-interfereing and interoperable DSRC implementations by the various user agencies.<br />\n
          The ETTM field is rapidly emerging with multiple technologies and incompatible products. In addition, the emergence of the ASTM standard for Layers 1 and 2 has created the potential for significant interference between RF compatible systems. The lack of standard message sets, lower layer protocols, and transponder resource definitions threatens to postpone the deployment of this critical technology to the marketplace. The effort behind this PAR will consolidate and publish a standard to support Commercial Vehicle Operation and ETTM. The open nature of the developed interface will ensure that it is extensible to other DSRC areas, e.g. CVO credential information exchange, pre-clearance screening, fleet management and private messaging.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Sets for Vehicle/Roadside Communications"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94958 …}
    #channels: Doctrine\ORM\PersistentCollection {#94952 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94956 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94954 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94966 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94905
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94855
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @937692000 {#94898
      date: 1999-09-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1149717600 {#94904
      date: 2006-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1455"
    -bookCollection: ""
    -pageCount: 134
    -documents: Doctrine\ORM\PersistentCollection {#94964 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94962 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#94885
    #id: 9368
    #code: "IEEE00002171"
    #attributes: Doctrine\ORM\PersistentCollection {#94950 …}
    #variants: Doctrine\ORM\PersistentCollection {#94948 …}
    #options: Doctrine\ORM\PersistentCollection {#94944 …}
    #associations: Doctrine\ORM\PersistentCollection {#94946 …}
    #createdAt: DateTime @1751038207 {#94865
      date: 2025-06-27 17:30:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94900
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94960 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95241
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94885}
        #id: 32481
        #name: "IEEE 1455:1999 (R2006)"
        #slug: "ieee-1455-1999-r2006-ieee00002171-241020"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          &quot; Those characteristics of a dedicated short-range communications (DSRC) system thetare independent of the Physical and Data Link Layers (ISO model Layers 1 and 2) are specified.The required and optional features of the roadside equipment (RSE) and the onboard equipment(OBE) are specified. In addition, the Applications Layer (ISO model Layer 7) services and protocols,the RSE resource manager, the corresponding OBE command interpreter, and the application-spe-cific messages are all specified. Standard supports and guidelines are provided for implementingsecure DSRC systems. &quot;<br />\n
          \t\t\t\t<br />\n
          Research, compile, and consolidate information leading to the publication of a standard for exchanging DSRC information, providing for bi-directional message transmission and device control, in a manner which is compatible with but independent of the ASTM efforts to specify DSRC Layers 1 and 2. This will entail specifying the transponder resources, the transponder resource manager, the application message sets, and the sighals and services such as the Electronic Toll and Traffic Mgmt User's Group, the ATA, the CVO community, the vendor community, and other standards bodies to synthesize existing messaging requirements into a single, open industry standard which supports non-interfereing and interoperable DSRC implementations by the various user agencies.<br />\n
          The ETTM field is rapidly emerging with multiple technologies and incompatible products. In addition, the emergence of the ASTM standard for Layers 1 and 2 has created the potential for significant interference between RF compatible systems. The lack of standard message sets, lower layer protocols, and transponder resource definitions threatens to postpone the deployment of this critical technology to the marketplace. The effort behind this PAR will consolidate and publish a standard to support Commercial Vehicle Operation and ETTM. The open nature of the developed interface will ensure that it is extensible to other DSRC areas, e.g. CVO credential information exchange, pre-clearance screening, fleet management and private messaging.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Sets for Vehicle/Roadside Communications"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94958 …}
    #channels: Doctrine\ORM\PersistentCollection {#94952 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94956 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94954 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94966 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94905
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94855
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @937692000 {#94898
      date: 1999-09-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1149717600 {#94904
      date: 2006-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1455"
    -bookCollection: ""
    -pageCount: 134
    -documents: Doctrine\ORM\PersistentCollection {#94964 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94962 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#95248
  +product: App\Entity\Product\Product {#94885
    #id: 9368
    #code: "IEEE00002171"
    #attributes: Doctrine\ORM\PersistentCollection {#94950 …}
    #variants: Doctrine\ORM\PersistentCollection {#94948 …}
    #options: Doctrine\ORM\PersistentCollection {#94944 …}
    #associations: Doctrine\ORM\PersistentCollection {#94946 …}
    #createdAt: DateTime @1751038207 {#94865
      date: 2025-06-27 17:30:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94900
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94960 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95241
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94885}
        #id: 32481
        #name: "IEEE 1455:1999 (R2006)"
        #slug: "ieee-1455-1999-r2006-ieee00002171-241020"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          &quot; Those characteristics of a dedicated short-range communications (DSRC) system thetare independent of the Physical and Data Link Layers (ISO model Layers 1 and 2) are specified.The required and optional features of the roadside equipment (RSE) and the onboard equipment(OBE) are specified. In addition, the Applications Layer (ISO model Layer 7) services and protocols,the RSE resource manager, the corresponding OBE command interpreter, and the application-spe-cific messages are all specified. Standard supports and guidelines are provided for implementingsecure DSRC systems. &quot;<br />\n
          \t\t\t\t<br />\n
          Research, compile, and consolidate information leading to the publication of a standard for exchanging DSRC information, providing for bi-directional message transmission and device control, in a manner which is compatible with but independent of the ASTM efforts to specify DSRC Layers 1 and 2. This will entail specifying the transponder resources, the transponder resource manager, the application message sets, and the sighals and services such as the Electronic Toll and Traffic Mgmt User's Group, the ATA, the CVO community, the vendor community, and other standards bodies to synthesize existing messaging requirements into a single, open industry standard which supports non-interfereing and interoperable DSRC implementations by the various user agencies.<br />\n
          The ETTM field is rapidly emerging with multiple technologies and incompatible products. In addition, the emergence of the ASTM standard for Layers 1 and 2 has created the potential for significant interference between RF compatible systems. The lack of standard message sets, lower layer protocols, and transponder resource definitions threatens to postpone the deployment of this critical technology to the marketplace. The effort behind this PAR will consolidate and publish a standard to support Commercial Vehicle Operation and ETTM. The open nature of the developed interface will ensure that it is extensible to other DSRC areas, e.g. CVO credential information exchange, pre-clearance screening, fleet management and private messaging.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Sets for Vehicle/Roadside Communications"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94958 …}
    #channels: Doctrine\ORM\PersistentCollection {#94952 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94956 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94954 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94966 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94905
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94855
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @937692000 {#94898
      date: 1999-09-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1149717600 {#94904
      date: 2006-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1455"
    -bookCollection: ""
    -pageCount: 134
    -documents: Doctrine\ORM\PersistentCollection {#94964 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94962 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#94885
    #id: 9368
    #code: "IEEE00002171"
    #attributes: Doctrine\ORM\PersistentCollection {#94950 …}
    #variants: Doctrine\ORM\PersistentCollection {#94948 …}
    #options: Doctrine\ORM\PersistentCollection {#94944 …}
    #associations: Doctrine\ORM\PersistentCollection {#94946 …}
    #createdAt: DateTime @1751038207 {#94865
      date: 2025-06-27 17:30:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94900
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94960 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95241
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94885}
        #id: 32481
        #name: "IEEE 1455:1999 (R2006)"
        #slug: "ieee-1455-1999-r2006-ieee00002171-241020"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          &quot; Those characteristics of a dedicated short-range communications (DSRC) system thetare independent of the Physical and Data Link Layers (ISO model Layers 1 and 2) are specified.The required and optional features of the roadside equipment (RSE) and the onboard equipment(OBE) are specified. In addition, the Applications Layer (ISO model Layer 7) services and protocols,the RSE resource manager, the corresponding OBE command interpreter, and the application-spe-cific messages are all specified. Standard supports and guidelines are provided for implementingsecure DSRC systems. &quot;<br />\n
          \t\t\t\t<br />\n
          Research, compile, and consolidate information leading to the publication of a standard for exchanging DSRC information, providing for bi-directional message transmission and device control, in a manner which is compatible with but independent of the ASTM efforts to specify DSRC Layers 1 and 2. This will entail specifying the transponder resources, the transponder resource manager, the application message sets, and the sighals and services such as the Electronic Toll and Traffic Mgmt User's Group, the ATA, the CVO community, the vendor community, and other standards bodies to synthesize existing messaging requirements into a single, open industry standard which supports non-interfereing and interoperable DSRC implementations by the various user agencies.<br />\n
          The ETTM field is rapidly emerging with multiple technologies and incompatible products. In addition, the emergence of the ASTM standard for Layers 1 and 2 has created the potential for significant interference between RF compatible systems. The lack of standard message sets, lower layer protocols, and transponder resource definitions threatens to postpone the deployment of this critical technology to the marketplace. The effort behind this PAR will consolidate and publish a standard to support Commercial Vehicle Operation and ETTM. The open nature of the developed interface will ensure that it is extensible to other DSRC areas, e.g. CVO credential information exchange, pre-clearance screening, fleet management and private messaging.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Sets for Vehicle/Roadside Communications"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94958 …}
    #channels: Doctrine\ORM\PersistentCollection {#94952 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94956 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94954 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94966 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94905
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94855
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @937692000 {#94898
      date: 1999-09-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1149717600 {#94904
      date: 2006-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1455"
    -bookCollection: ""
    -pageCount: 134
    -documents: Doctrine\ORM\PersistentCollection {#94964 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94962 …}
  }
]

App\Twig\Components\ProductMostRecent {#95342
  +product: App\Entity\Product\Product {#94885
    #id: 9368
    #code: "IEEE00002171"
    #attributes: Doctrine\ORM\PersistentCollection {#94950 …}
    #variants: Doctrine\ORM\PersistentCollection {#94948 …}
    #options: Doctrine\ORM\PersistentCollection {#94944 …}
    #associations: Doctrine\ORM\PersistentCollection {#94946 …}
    #createdAt: DateTime @1751038207 {#94865
      date: 2025-06-27 17:30:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94900
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94960 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95241
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94885}
        #id: 32481
        #name: "IEEE 1455:1999 (R2006)"
        #slug: "ieee-1455-1999-r2006-ieee00002171-241020"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          &quot; Those characteristics of a dedicated short-range communications (DSRC) system thetare independent of the Physical and Data Link Layers (ISO model Layers 1 and 2) are specified.The required and optional features of the roadside equipment (RSE) and the onboard equipment(OBE) are specified. In addition, the Applications Layer (ISO model Layer 7) services and protocols,the RSE resource manager, the corresponding OBE command interpreter, and the application-spe-cific messages are all specified. Standard supports and guidelines are provided for implementingsecure DSRC systems. &quot;<br />\n
          \t\t\t\t<br />\n
          Research, compile, and consolidate information leading to the publication of a standard for exchanging DSRC information, providing for bi-directional message transmission and device control, in a manner which is compatible with but independent of the ASTM efforts to specify DSRC Layers 1 and 2. This will entail specifying the transponder resources, the transponder resource manager, the application message sets, and the sighals and services such as the Electronic Toll and Traffic Mgmt User's Group, the ATA, the CVO community, the vendor community, and other standards bodies to synthesize existing messaging requirements into a single, open industry standard which supports non-interfereing and interoperable DSRC implementations by the various user agencies.<br />\n
          The ETTM field is rapidly emerging with multiple technologies and incompatible products. In addition, the emergence of the ASTM standard for Layers 1 and 2 has created the potential for significant interference between RF compatible systems. The lack of standard message sets, lower layer protocols, and transponder resource definitions threatens to postpone the deployment of this critical technology to the marketplace. The effort behind this PAR will consolidate and publish a standard to support Commercial Vehicle Operation and ETTM. The open nature of the developed interface will ensure that it is extensible to other DSRC areas, e.g. CVO credential information exchange, pre-clearance screening, fleet management and private messaging.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Sets for Vehicle/Roadside Communications"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94958 …}
    #channels: Doctrine\ORM\PersistentCollection {#94952 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94956 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94954 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94966 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94905
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94855
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @937692000 {#94898
      date: 1999-09-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1149717600 {#94904
      date: 2006-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: null
    -edition: null
    -coreDocument: "1455"
    -bookCollection: ""
    -pageCount: 134
    -documents: Doctrine\ORM\PersistentCollection {#94964 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94962 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#94873
    #id: 9989
    #code: "IEEE00003401"
    #attributes: Doctrine\ORM\PersistentCollection {#94933 …}
    #variants: Doctrine\ORM\PersistentCollection {#94935 …}
    #options: Doctrine\ORM\PersistentCollection {#94970 …}
    #associations: Doctrine\ORM\PersistentCollection {#94968 …}
    #createdAt: DateTime @1751038725 {#94942
      date: 2025-06-27 17:38:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94941
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94917 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95555
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94873}
        #id: 34965
        #name: "IEEE 1616:2004 (R2010)"
        #slug: "ieee-1616-2004-r2010-ieee00003401-241641"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to motor vehicle pre-defined events. 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, or how the data are to be collected, recorded and stored. It is applicable to 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
          \t\t\t\t<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. 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: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94925 …}
    #channels: Doctrine\ORM\PersistentCollection {#94931 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94927 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94929 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94896 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94940
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1625176800 {#94939
      date: 2021-07-02 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1107990000 {#94938
      date: 2005-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1269471600 {#94937
      date: 2010-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#94915
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 171
    -documents: Doctrine\ORM\PersistentCollection {#94857 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94893 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#95533
  +product: App\Entity\Product\Product {#94873
    #id: 9989
    #code: "IEEE00003401"
    #attributes: Doctrine\ORM\PersistentCollection {#94933 …}
    #variants: Doctrine\ORM\PersistentCollection {#94935 …}
    #options: Doctrine\ORM\PersistentCollection {#94970 …}
    #associations: Doctrine\ORM\PersistentCollection {#94968 …}
    #createdAt: DateTime @1751038725 {#94942
      date: 2025-06-27 17:38:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94941
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94917 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95555
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94873}
        #id: 34965
        #name: "IEEE 1616:2004 (R2010)"
        #slug: "ieee-1616-2004-r2010-ieee00003401-241641"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to motor vehicle pre-defined events. 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, or how the data are to be collected, recorded and stored. It is applicable to 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
          \t\t\t\t<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. 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: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94925 …}
    #channels: Doctrine\ORM\PersistentCollection {#94931 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94927 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94929 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94896 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94940
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1625176800 {#94939
      date: 2021-07-02 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1107990000 {#94938
      date: 2005-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1269471600 {#94937
      date: 2010-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#94915
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 171
    -documents: Doctrine\ORM\PersistentCollection {#94857 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94893 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#94873
    #id: 9989
    #code: "IEEE00003401"
    #attributes: Doctrine\ORM\PersistentCollection {#94933 …}
    #variants: Doctrine\ORM\PersistentCollection {#94935 …}
    #options: Doctrine\ORM\PersistentCollection {#94970 …}
    #associations: Doctrine\ORM\PersistentCollection {#94968 …}
    #createdAt: DateTime @1751038725 {#94942
      date: 2025-06-27 17:38:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94941
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94917 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95555
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94873}
        #id: 34965
        #name: "IEEE 1616:2004 (R2010)"
        #slug: "ieee-1616-2004-r2010-ieee00003401-241641"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to motor vehicle pre-defined events. 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, or how the data are to be collected, recorded and stored. It is applicable to 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
          \t\t\t\t<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. 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: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94925 …}
    #channels: Doctrine\ORM\PersistentCollection {#94931 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94927 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94929 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94896 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94940
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1625176800 {#94939
      date: 2021-07-02 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1107990000 {#94938
      date: 2005-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1269471600 {#94937
      date: 2010-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#94915
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 171
    -documents: Doctrine\ORM\PersistentCollection {#94857 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94893 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#95569
  +product: App\Entity\Product\Product {#94873
    #id: 9989
    #code: "IEEE00003401"
    #attributes: Doctrine\ORM\PersistentCollection {#94933 …}
    #variants: Doctrine\ORM\PersistentCollection {#94935 …}
    #options: Doctrine\ORM\PersistentCollection {#94970 …}
    #associations: Doctrine\ORM\PersistentCollection {#94968 …}
    #createdAt: DateTime @1751038725 {#94942
      date: 2025-06-27 17:38:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94941
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94917 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95555
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94873}
        #id: 34965
        #name: "IEEE 1616:2004 (R2010)"
        #slug: "ieee-1616-2004-r2010-ieee00003401-241641"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to motor vehicle pre-defined events. 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, or how the data are to be collected, recorded and stored. It is applicable to 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
          \t\t\t\t<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. 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: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94925 …}
    #channels: Doctrine\ORM\PersistentCollection {#94931 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94927 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94929 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94896 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94940
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1625176800 {#94939
      date: 2021-07-02 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1107990000 {#94938
      date: 2005-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1269471600 {#94937
      date: 2010-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#94915
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 171
    -documents: Doctrine\ORM\PersistentCollection {#94857 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94893 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#94873
    #id: 9989
    #code: "IEEE00003401"
    #attributes: Doctrine\ORM\PersistentCollection {#94933 …}
    #variants: Doctrine\ORM\PersistentCollection {#94935 …}
    #options: Doctrine\ORM\PersistentCollection {#94970 …}
    #associations: Doctrine\ORM\PersistentCollection {#94968 …}
    #createdAt: DateTime @1751038725 {#94942
      date: 2025-06-27 17:38:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94941
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94917 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95555
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94873}
        #id: 34965
        #name: "IEEE 1616:2004 (R2010)"
        #slug: "ieee-1616-2004-r2010-ieee00003401-241641"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to motor vehicle pre-defined events. 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, or how the data are to be collected, recorded and stored. It is applicable to 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
          \t\t\t\t<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. 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: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94925 …}
    #channels: Doctrine\ORM\PersistentCollection {#94931 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94927 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94929 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94896 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94940
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1625176800 {#94939
      date: 2021-07-02 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1107990000 {#94938
      date: 2005-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1269471600 {#94937
      date: 2010-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#94915
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 171
    -documents: Doctrine\ORM\PersistentCollection {#94857 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94893 …}
  }
]

App\Twig\Components\ProductMostRecent {#95642
  +product: App\Entity\Product\Product {#94873
    #id: 9989
    #code: "IEEE00003401"
    #attributes: Doctrine\ORM\PersistentCollection {#94933 …}
    #variants: Doctrine\ORM\PersistentCollection {#94935 …}
    #options: Doctrine\ORM\PersistentCollection {#94970 …}
    #associations: Doctrine\ORM\PersistentCollection {#94968 …}
    #createdAt: DateTime @1751038725 {#94942
      date: 2025-06-27 17:38:45.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94941
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94917 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95555
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94873}
        #id: 34965
        #name: "IEEE 1616:2004 (R2010)"
        #slug: "ieee-1616-2004-r2010-ieee00003401-241641"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to motor vehicle pre-defined events. 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, or how the data are to be collected, recorded and stored. It is applicable to 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
          \t\t\t\t<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. 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: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94925 …}
    #channels: Doctrine\ORM\PersistentCollection {#94931 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94927 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94929 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94896 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94940
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1625176800 {#94939
      date: 2021-07-02 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1107990000 {#94938
      date: 2005-02-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1269471600 {#94937
      date: 2010-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#94915
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 171
    -documents: Doctrine\ORM\PersistentCollection {#94857 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94893 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#94978
    #id: 10636
    #code: "IEEE00004745"
    #attributes: Doctrine\ORM\PersistentCollection {#94995 …}
    #variants: Doctrine\ORM\PersistentCollection {#94997 …}
    #options: Doctrine\ORM\PersistentCollection {#95001 …}
    #associations: Doctrine\ORM\PersistentCollection {#94999 …}
    #createdAt: DateTime @1751039188 {#94972
      date: 2025-06-27 17:46:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94973
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94985 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95784
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94978}
        #id: 37553
        #name: "IEEE 1616a:2010"
        #slug: "ieee-1616a-2010-ieee00004745-242288"
        #description: """
          Amendment Standard - Inactive-Reserved.<br />\n
          This amendment adds information pertaining to motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) by revision.<br />\n
          \t\t\t\t<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to pre-defined events in usage history. This amendment defines a lockout protocol for MVEDR output data accessibility 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 but 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 means of maintaining data security on the vehicle via a motor vehicle DLC connector lockout apparatus (MVEDRCLA). The MVEDRCLA is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public highways.<br />\n
          Change the purpose as follows:<br />\n
          Many light-duty 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 [Bxx] (ISO 15031-3:2004 [Bxx]) vehicle DLC has a common design and pinout, and is thus<br />\n
          universally used to access event data recorder information.2 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<br />\n
          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<br />\n
          provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA which 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<br />\n
          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<br />\n
          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 Recorders (MVEDRs) Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94987 …}
    #channels: Doctrine\ORM\PersistentCollection {#94993 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94989 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94991 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94979 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94974
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1641337200 {#94975
      date: 2022-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1273183200 {#94976
      date: 2010-05-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#94977
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 19
    -documents: Doctrine\ORM\PersistentCollection {#94981 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94983 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#95764
  +product: App\Entity\Product\Product {#94978
    #id: 10636
    #code: "IEEE00004745"
    #attributes: Doctrine\ORM\PersistentCollection {#94995 …}
    #variants: Doctrine\ORM\PersistentCollection {#94997 …}
    #options: Doctrine\ORM\PersistentCollection {#95001 …}
    #associations: Doctrine\ORM\PersistentCollection {#94999 …}
    #createdAt: DateTime @1751039188 {#94972
      date: 2025-06-27 17:46:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94973
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94985 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95784
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94978}
        #id: 37553
        #name: "IEEE 1616a:2010"
        #slug: "ieee-1616a-2010-ieee00004745-242288"
        #description: """
          Amendment Standard - Inactive-Reserved.<br />\n
          This amendment adds information pertaining to motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) by revision.<br />\n
          \t\t\t\t<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to pre-defined events in usage history. This amendment defines a lockout protocol for MVEDR output data accessibility 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 but 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 means of maintaining data security on the vehicle via a motor vehicle DLC connector lockout apparatus (MVEDRCLA). The MVEDRCLA is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public highways.<br />\n
          Change the purpose as follows:<br />\n
          Many light-duty 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 [Bxx] (ISO 15031-3:2004 [Bxx]) vehicle DLC has a common design and pinout, and is thus<br />\n
          universally used to access event data recorder information.2 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<br />\n
          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<br />\n
          provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA which 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<br />\n
          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<br />\n
          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 Recorders (MVEDRs) Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94987 …}
    #channels: Doctrine\ORM\PersistentCollection {#94993 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94989 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94991 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94979 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94974
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1641337200 {#94975
      date: 2022-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1273183200 {#94976
      date: 2010-05-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#94977
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 19
    -documents: Doctrine\ORM\PersistentCollection {#94981 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94983 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#94978
    #id: 10636
    #code: "IEEE00004745"
    #attributes: Doctrine\ORM\PersistentCollection {#94995 …}
    #variants: Doctrine\ORM\PersistentCollection {#94997 …}
    #options: Doctrine\ORM\PersistentCollection {#95001 …}
    #associations: Doctrine\ORM\PersistentCollection {#94999 …}
    #createdAt: DateTime @1751039188 {#94972
      date: 2025-06-27 17:46:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94973
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94985 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95784
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94978}
        #id: 37553
        #name: "IEEE 1616a:2010"
        #slug: "ieee-1616a-2010-ieee00004745-242288"
        #description: """
          Amendment Standard - Inactive-Reserved.<br />\n
          This amendment adds information pertaining to motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) by revision.<br />\n
          \t\t\t\t<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to pre-defined events in usage history. This amendment defines a lockout protocol for MVEDR output data accessibility 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 but 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 means of maintaining data security on the vehicle via a motor vehicle DLC connector lockout apparatus (MVEDRCLA). The MVEDRCLA is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public highways.<br />\n
          Change the purpose as follows:<br />\n
          Many light-duty 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 [Bxx] (ISO 15031-3:2004 [Bxx]) vehicle DLC has a common design and pinout, and is thus<br />\n
          universally used to access event data recorder information.2 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<br />\n
          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<br />\n
          provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA which 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<br />\n
          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<br />\n
          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 Recorders (MVEDRs) Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94987 …}
    #channels: Doctrine\ORM\PersistentCollection {#94993 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94989 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94991 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94979 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94974
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1641337200 {#94975
      date: 2022-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1273183200 {#94976
      date: 2010-05-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#94977
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 19
    -documents: Doctrine\ORM\PersistentCollection {#94981 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94983 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#95798
  +product: App\Entity\Product\Product {#94978
    #id: 10636
    #code: "IEEE00004745"
    #attributes: Doctrine\ORM\PersistentCollection {#94995 …}
    #variants: Doctrine\ORM\PersistentCollection {#94997 …}
    #options: Doctrine\ORM\PersistentCollection {#95001 …}
    #associations: Doctrine\ORM\PersistentCollection {#94999 …}
    #createdAt: DateTime @1751039188 {#94972
      date: 2025-06-27 17:46:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94973
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94985 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95784
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94978}
        #id: 37553
        #name: "IEEE 1616a:2010"
        #slug: "ieee-1616a-2010-ieee00004745-242288"
        #description: """
          Amendment Standard - Inactive-Reserved.<br />\n
          This amendment adds information pertaining to motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) by revision.<br />\n
          \t\t\t\t<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to pre-defined events in usage history. This amendment defines a lockout protocol for MVEDR output data accessibility 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 but 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 means of maintaining data security on the vehicle via a motor vehicle DLC connector lockout apparatus (MVEDRCLA). The MVEDRCLA is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public highways.<br />\n
          Change the purpose as follows:<br />\n
          Many light-duty 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 [Bxx] (ISO 15031-3:2004 [Bxx]) vehicle DLC has a common design and pinout, and is thus<br />\n
          universally used to access event data recorder information.2 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<br />\n
          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<br />\n
          provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA which 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<br />\n
          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<br />\n
          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 Recorders (MVEDRs) Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94987 …}
    #channels: Doctrine\ORM\PersistentCollection {#94993 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94989 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94991 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94979 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94974
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1641337200 {#94975
      date: 2022-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1273183200 {#94976
      date: 2010-05-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#94977
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 19
    -documents: Doctrine\ORM\PersistentCollection {#94981 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94983 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#94978
    #id: 10636
    #code: "IEEE00004745"
    #attributes: Doctrine\ORM\PersistentCollection {#94995 …}
    #variants: Doctrine\ORM\PersistentCollection {#94997 …}
    #options: Doctrine\ORM\PersistentCollection {#95001 …}
    #associations: Doctrine\ORM\PersistentCollection {#94999 …}
    #createdAt: DateTime @1751039188 {#94972
      date: 2025-06-27 17:46:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94973
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94985 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95784
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94978}
        #id: 37553
        #name: "IEEE 1616a:2010"
        #slug: "ieee-1616a-2010-ieee00004745-242288"
        #description: """
          Amendment Standard - Inactive-Reserved.<br />\n
          This amendment adds information pertaining to motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) by revision.<br />\n
          \t\t\t\t<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to pre-defined events in usage history. This amendment defines a lockout protocol for MVEDR output data accessibility 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 but 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 means of maintaining data security on the vehicle via a motor vehicle DLC connector lockout apparatus (MVEDRCLA). The MVEDRCLA is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public highways.<br />\n
          Change the purpose as follows:<br />\n
          Many light-duty 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 [Bxx] (ISO 15031-3:2004 [Bxx]) vehicle DLC has a common design and pinout, and is thus<br />\n
          universally used to access event data recorder information.2 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<br />\n
          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<br />\n
          provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA which 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<br />\n
          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<br />\n
          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 Recorders (MVEDRs) Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94987 …}
    #channels: Doctrine\ORM\PersistentCollection {#94993 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94989 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94991 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94979 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94974
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1641337200 {#94975
      date: 2022-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1273183200 {#94976
      date: 2010-05-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#94977
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 19
    -documents: Doctrine\ORM\PersistentCollection {#94981 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94983 …}
  }
]

App\Twig\Components\ProductMostRecent {#95872
  +product: App\Entity\Product\Product {#94978
    #id: 10636
    #code: "IEEE00004745"
    #attributes: Doctrine\ORM\PersistentCollection {#94995 …}
    #variants: Doctrine\ORM\PersistentCollection {#94997 …}
    #options: Doctrine\ORM\PersistentCollection {#95001 …}
    #associations: Doctrine\ORM\PersistentCollection {#94999 …}
    #createdAt: DateTime @1751039188 {#94972
      date: 2025-06-27 17:46:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94973
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94985 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95784
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94978}
        #id: 37553
        #name: "IEEE 1616a:2010"
        #slug: "ieee-1616a-2010-ieee00004745-242288"
        #description: """
          Amendment Standard - Inactive-Reserved.<br />\n
          This amendment adds information pertaining to motor vehicle event data recorder connector lockout apparatus (MVEDRCLA) by revision.<br />\n
          \t\t\t\t<br />\n
          Motor Vehicle Event Data Recorders (MVEDRs) collect, record, store and export data related to pre-defined events in usage history. This amendment defines a lockout protocol for MVEDR output data accessibility 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 but 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 means of maintaining data security on the vehicle via a motor vehicle DLC connector lockout apparatus (MVEDRCLA). The MVEDRCLA is applicable to vehicles and their respective event data recorders for all types of motor vehicles licensed to operate on public highways.<br />\n
          Change the purpose as follows:<br />\n
          Many light-duty 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 [Bxx] (ISO 15031-3:2004 [Bxx]) vehicle DLC has a common design and pinout, and is thus<br />\n
          universally used to access event data recorder information.2 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<br />\n
          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<br />\n
          provides an opportunity to voluntarily achieve DLC security by standardizing a MVEDRCLA which 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<br />\n
          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<br />\n
          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 Recorders (MVEDRs) Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94987 …}
    #channels: Doctrine\ORM\PersistentCollection {#94993 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94989 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94991 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94979 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94974
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1641337200 {#94975
      date: 2022-01-05 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1273183200 {#94976
      date: 2010-05-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#94977
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1616"
    -bookCollection: ""
    -pageCount: 19
    -documents: Doctrine\ORM\PersistentCollection {#94981 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94983 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95009
    #id: 10750
    #code: "IEEE00004950"
    #attributes: Doctrine\ORM\PersistentCollection {#95026 …}
    #variants: Doctrine\ORM\PersistentCollection {#95028 …}
    #options: Doctrine\ORM\PersistentCollection {#95032 …}
    #associations: Doctrine\ORM\PersistentCollection {#95030 …}
    #createdAt: DateTime @1751039260 {#95003
      date: 2025-06-27 17:47:40.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95004
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95016 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95009}
        #id: 38009
        #name: "IEEE 1609.11:2010"
        #slug: "ieee-1609-11-2010-ieee00004950-242402"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard specifies the electronic payment service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability (vehicle-to-roadside) for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU) using WAVE. It does not provide a full solution for interoperability, and it does not define other parts of the electronic<br />\n
          payment system, other services, other technologies and non-technical elements of payment interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization), nor the applications using the payment service.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the application service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications using IEEE Std 802.11(TM) and IEEE 1609 protocols in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU). It does not provide a full solution for interoperability, and it does not define other parts of the electronic payment-system, other services, other technologies, and non-technical elements of interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization).<br />\n
          This standard provides an open standard for the relevant interface in WAVE-based transaction systems, providing a common interoperable service for device identity and payment authentication, and payment<br />\n
          data transfer. This allows for interoperability between systems of different vendors and/or operators.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)-- Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95018 …}
    #channels: Doctrine\ORM\PersistentCollection {#95024 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95020 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95022 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95010 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95005
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1627682400 {#95006
      date: 2021-07-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1294527600 {#95007
      date: 2011-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#95008
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.11"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95012 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95014 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96002
  +product: App\Entity\Product\Product {#95009
    #id: 10750
    #code: "IEEE00004950"
    #attributes: Doctrine\ORM\PersistentCollection {#95026 …}
    #variants: Doctrine\ORM\PersistentCollection {#95028 …}
    #options: Doctrine\ORM\PersistentCollection {#95032 …}
    #associations: Doctrine\ORM\PersistentCollection {#95030 …}
    #createdAt: DateTime @1751039260 {#95003
      date: 2025-06-27 17:47:40.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95004
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95016 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95009}
        #id: 38009
        #name: "IEEE 1609.11:2010"
        #slug: "ieee-1609-11-2010-ieee00004950-242402"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard specifies the electronic payment service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability (vehicle-to-roadside) for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU) using WAVE. It does not provide a full solution for interoperability, and it does not define other parts of the electronic<br />\n
          payment system, other services, other technologies and non-technical elements of payment interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization), nor the applications using the payment service.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the application service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications using IEEE Std 802.11(TM) and IEEE 1609 protocols in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU). It does not provide a full solution for interoperability, and it does not define other parts of the electronic payment-system, other services, other technologies, and non-technical elements of interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization).<br />\n
          This standard provides an open standard for the relevant interface in WAVE-based transaction systems, providing a common interoperable service for device identity and payment authentication, and payment<br />\n
          data transfer. This allows for interoperability between systems of different vendors and/or operators.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)-- Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95018 …}
    #channels: Doctrine\ORM\PersistentCollection {#95024 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95020 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95022 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95010 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95005
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1627682400 {#95006
      date: 2021-07-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1294527600 {#95007
      date: 2011-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#95008
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.11"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95012 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95014 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95009
    #id: 10750
    #code: "IEEE00004950"
    #attributes: Doctrine\ORM\PersistentCollection {#95026 …}
    #variants: Doctrine\ORM\PersistentCollection {#95028 …}
    #options: Doctrine\ORM\PersistentCollection {#95032 …}
    #associations: Doctrine\ORM\PersistentCollection {#95030 …}
    #createdAt: DateTime @1751039260 {#95003
      date: 2025-06-27 17:47:40.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95004
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95016 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95009}
        #id: 38009
        #name: "IEEE 1609.11:2010"
        #slug: "ieee-1609-11-2010-ieee00004950-242402"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard specifies the electronic payment service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability (vehicle-to-roadside) for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU) using WAVE. It does not provide a full solution for interoperability, and it does not define other parts of the electronic<br />\n
          payment system, other services, other technologies and non-technical elements of payment interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization), nor the applications using the payment service.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the application service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications using IEEE Std 802.11(TM) and IEEE 1609 protocols in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU). It does not provide a full solution for interoperability, and it does not define other parts of the electronic payment-system, other services, other technologies, and non-technical elements of interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization).<br />\n
          This standard provides an open standard for the relevant interface in WAVE-based transaction systems, providing a common interoperable service for device identity and payment authentication, and payment<br />\n
          data transfer. This allows for interoperability between systems of different vendors and/or operators.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)-- Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95018 …}
    #channels: Doctrine\ORM\PersistentCollection {#95024 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95020 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95022 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95010 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95005
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1627682400 {#95006
      date: 2021-07-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1294527600 {#95007
      date: 2011-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#95008
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.11"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95012 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95014 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96036
  +product: App\Entity\Product\Product {#95009
    #id: 10750
    #code: "IEEE00004950"
    #attributes: Doctrine\ORM\PersistentCollection {#95026 …}
    #variants: Doctrine\ORM\PersistentCollection {#95028 …}
    #options: Doctrine\ORM\PersistentCollection {#95032 …}
    #associations: Doctrine\ORM\PersistentCollection {#95030 …}
    #createdAt: DateTime @1751039260 {#95003
      date: 2025-06-27 17:47:40.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95004
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95016 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95009}
        #id: 38009
        #name: "IEEE 1609.11:2010"
        #slug: "ieee-1609-11-2010-ieee00004950-242402"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard specifies the electronic payment service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability (vehicle-to-roadside) for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU) using WAVE. It does not provide a full solution for interoperability, and it does not define other parts of the electronic<br />\n
          payment system, other services, other technologies and non-technical elements of payment interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization), nor the applications using the payment service.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the application service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications using IEEE Std 802.11(TM) and IEEE 1609 protocols in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU). It does not provide a full solution for interoperability, and it does not define other parts of the electronic payment-system, other services, other technologies, and non-technical elements of interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization).<br />\n
          This standard provides an open standard for the relevant interface in WAVE-based transaction systems, providing a common interoperable service for device identity and payment authentication, and payment<br />\n
          data transfer. This allows for interoperability between systems of different vendors and/or operators.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)-- Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95018 …}
    #channels: Doctrine\ORM\PersistentCollection {#95024 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95020 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95022 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95010 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95005
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1627682400 {#95006
      date: 2021-07-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1294527600 {#95007
      date: 2011-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#95008
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.11"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95012 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95014 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95009
    #id: 10750
    #code: "IEEE00004950"
    #attributes: Doctrine\ORM\PersistentCollection {#95026 …}
    #variants: Doctrine\ORM\PersistentCollection {#95028 …}
    #options: Doctrine\ORM\PersistentCollection {#95032 …}
    #associations: Doctrine\ORM\PersistentCollection {#95030 …}
    #createdAt: DateTime @1751039260 {#95003
      date: 2025-06-27 17:47:40.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95004
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95016 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95009}
        #id: 38009
        #name: "IEEE 1609.11:2010"
        #slug: "ieee-1609-11-2010-ieee00004950-242402"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard specifies the electronic payment service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability (vehicle-to-roadside) for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU) using WAVE. It does not provide a full solution for interoperability, and it does not define other parts of the electronic<br />\n
          payment system, other services, other technologies and non-technical elements of payment interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization), nor the applications using the payment service.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the application service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications using IEEE Std 802.11(TM) and IEEE 1609 protocols in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU). It does not provide a full solution for interoperability, and it does not define other parts of the electronic payment-system, other services, other technologies, and non-technical elements of interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization).<br />\n
          This standard provides an open standard for the relevant interface in WAVE-based transaction systems, providing a common interoperable service for device identity and payment authentication, and payment<br />\n
          data transfer. This allows for interoperability between systems of different vendors and/or operators.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)-- Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95018 …}
    #channels: Doctrine\ORM\PersistentCollection {#95024 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95020 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95022 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95010 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95005
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1627682400 {#95006
      date: 2021-07-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1294527600 {#95007
      date: 2011-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#95008
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.11"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95012 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95014 …}
  }
]

App\Twig\Components\ProductMostRecent {#96109
  +product: App\Entity\Product\Product {#95009
    #id: 10750
    #code: "IEEE00004950"
    #attributes: Doctrine\ORM\PersistentCollection {#95026 …}
    #variants: Doctrine\ORM\PersistentCollection {#95028 …}
    #options: Doctrine\ORM\PersistentCollection {#95032 …}
    #associations: Doctrine\ORM\PersistentCollection {#95030 …}
    #createdAt: DateTime @1751039260 {#95003
      date: 2025-06-27 17:47:40.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95004
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95016 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96022
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95009}
        #id: 38009
        #name: "IEEE 1609.11:2010"
        #slug: "ieee-1609-11-2010-ieee00004950-242402"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard specifies the electronic payment service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability (vehicle-to-roadside) for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU) using WAVE. It does not provide a full solution for interoperability, and it does not define other parts of the electronic<br />\n
          payment system, other services, other technologies and non-technical elements of payment interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization), nor the applications using the payment service.<br />\n
          \t\t\t\t<br />\n
          This standard specifies the application service layer and profile for Payment and Identity authentication, and Payment Data transfer for Dedicated Short Range Communication (DSRC) based applications using IEEE Std 802.11(TM) and IEEE 1609 protocols in Wireless Access in Vehicular Environments. This standard defines a basic level of technical interoperability for electronic payment equipment, i.e., onboard unit (OBU) and roadside unit (RSU). It does not provide a full solution for interoperability, and it does not define other parts of the electronic payment-system, other services, other technologies, and non-technical elements of interoperability. This standard is not intended to define technology and processes to activate and store data into the OBU (personalization).<br />\n
          This standard provides an open standard for the relevant interface in WAVE-based transaction systems, providing a common interoperable service for device identity and payment authentication, and payment<br />\n
          data transfer. This allows for interoperability between systems of different vendors and/or operators.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)-- Over-the-Air Electronic Payment Data Exchange Protocol for Intelligent Transportation Systems (ITS)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95018 …}
    #channels: Doctrine\ORM\PersistentCollection {#95024 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95020 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95022 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95010 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95005
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1627682400 {#95006
      date: 2021-07-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1294527600 {#95007
      date: 2011-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1616626800 {#95008
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1609.11"
    -bookCollection: ""
    -pageCount: 62
    -documents: Doctrine\ORM\PersistentCollection {#95012 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95014 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95039
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95056 …}
    #variants: Doctrine\ORM\PersistentCollection {#95058 …}
    #options: Doctrine\ORM\PersistentCollection {#95062 …}
    #associations: Doctrine\ORM\PersistentCollection {#95060 …}
    #createdAt: DateTime @1751040556 {#95034
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95035
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95046 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96251
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95039}
        #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 {#95048 …}
    #channels: Doctrine\ORM\PersistentCollection {#95054 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95050 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95052 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95040 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95036
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95037
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95038
      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 {#95042 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95044 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96231
  +product: App\Entity\Product\Product {#95039
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95056 …}
    #variants: Doctrine\ORM\PersistentCollection {#95058 …}
    #options: Doctrine\ORM\PersistentCollection {#95062 …}
    #associations: Doctrine\ORM\PersistentCollection {#95060 …}
    #createdAt: DateTime @1751040556 {#95034
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95035
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95046 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96251
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95039}
        #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 {#95048 …}
    #channels: Doctrine\ORM\PersistentCollection {#95054 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95050 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95052 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95040 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95036
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95037
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95038
      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 {#95042 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95044 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#95039
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95056 …}
    #variants: Doctrine\ORM\PersistentCollection {#95058 …}
    #options: Doctrine\ORM\PersistentCollection {#95062 …}
    #associations: Doctrine\ORM\PersistentCollection {#95060 …}
    #createdAt: DateTime @1751040556 {#95034
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95035
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95046 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96251
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95039}
        #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 {#95048 …}
    #channels: Doctrine\ORM\PersistentCollection {#95054 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95050 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95052 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95040 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95036
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95037
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95038
      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 {#95042 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95044 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96269
  +product: App\Entity\Product\Product {#95039
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95056 …}
    #variants: Doctrine\ORM\PersistentCollection {#95058 …}
    #options: Doctrine\ORM\PersistentCollection {#95062 …}
    #associations: Doctrine\ORM\PersistentCollection {#95060 …}
    #createdAt: DateTime @1751040556 {#95034
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95035
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95046 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96251
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95039}
        #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 {#95048 …}
    #channels: Doctrine\ORM\PersistentCollection {#95054 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95050 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95052 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95040 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95036
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95037
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95038
      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 {#95042 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95044 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95039
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95056 …}
    #variants: Doctrine\ORM\PersistentCollection {#95058 …}
    #options: Doctrine\ORM\PersistentCollection {#95062 …}
    #associations: Doctrine\ORM\PersistentCollection {#95060 …}
    #createdAt: DateTime @1751040556 {#95034
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95035
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95046 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96251
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95039}
        #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 {#95048 …}
    #channels: Doctrine\ORM\PersistentCollection {#95054 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95050 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95052 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95040 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95036
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95037
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95038
      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 {#95042 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95044 …}
  }
]

App\Twig\Components\ProductMostRecent {#96343
  +product: App\Entity\Product\Product {#95039
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#95056 …}
    #variants: Doctrine\ORM\PersistentCollection {#95058 …}
    #options: Doctrine\ORM\PersistentCollection {#95062 …}
    #associations: Doctrine\ORM\PersistentCollection {#95060 …}
    #createdAt: DateTime @1751040556 {#95034
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#95035
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95046 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96251
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95039}
        #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 {#95048 …}
    #channels: Doctrine\ORM\PersistentCollection {#95054 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95050 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95052 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95040 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95036
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#95037
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#95038
      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 {#95042 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95044 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#95070
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#95087 …}
    #variants: Doctrine\ORM\PersistentCollection {#95089 …}
    #options: Doctrine\ORM\PersistentCollection {#95093 …}
    #associations: Doctrine\ORM\PersistentCollection {#95091 …}
    #createdAt: DateTime @1751040738 {#95064
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95065
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95077 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96502
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95070}
        #id: 46649
        #name: "IEEE 1616.1:2023"
        #slug: "ieee-1616-1-2023-ieee00010939-244568"
        #description: """
          New IEEE Standard - Active.<br />\n
          The goals and metrics of a data storage system for automated driving (DSSAD) are defined in this standard. Functions and common technical requirements for data storage are identified. Data elements relevant to automated driving system (ADS) Level 3, Level 4 and Level 5 are defined. The usage of data among diverse end users is also defined. A compendium of data elements used in vehicles of categories M1 and N1 regarding their EDR and DSSAD for partial and fully automated vehicles is provided in this standard. An on-board diagnostic (OBD) port lockout/near field communication (NFC) protocol for protection against data manipulation via the vehicle diagnostic port is provided. This standard is made available without prejudice to national and regional laws related to data privacy, protection, and personal data processing. Users are responsible for compliance with all such laws and regulations. This standard may be frequently updated to include relevant data definitions and data elements toward the development of automated vehicles. The overall goal is to create a data collection standard for automated driving that includes functional requirements for automated vehicle gateways and security guidelines for cloud-based automotive data recorder requirements.<br />\n
          \t\t\t\t<br />\n
          This standard defines requirements and metrics for data storage in a data storage system for automated driving (DSSAD), as well as related functions and common technical requirements. A DSSAD is a device or function that records and stores a data set (“timestamped flags”) during the automated driving sequences of any vehicle equipped with Level 3, Level 4, or Level 5 automated driving systems (ADS). The standard conforms to a compendium of data elements used in vehicles of categories M1 (used for the carriage of passengers) and N1 [used for the carriage of goods (trucks)] regarding their event data recorder (EDR) and DSSAD for partial and fully automated vehicles, including relevant data elements to ADS Level 3, Level 4, and Level 5 (see Figure 1 for all ADS levels). This standard explains the means by whereby an EDR and a DSSAD interact. This standard is made available without prejudice to national, local, and regional laws and regulations related to data privacy, data protection, and personal data processing. Users are responsible for compliance with all such laws and regulations. This standard defines an onboard diagnostic connector (OBD-II) port lockout and near field communication (NFC) protocol for protection against data manipulation of EDR and DSSAD data via the vehicle diagnostic link connector (DLC). This standard does not include specifications for data retrieval tools and methods as that is subject to national and regional requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Data Storage Systems for Automated Driving"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95079 …}
    #channels: Doctrine\ORM\PersistentCollection {#95085 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95081 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95083 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95071 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95066
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#95067
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#95068
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#95069
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#95073 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95075 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#96482
  +product: App\Entity\Product\Product {#95070
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#95087 …}
    #variants: Doctrine\ORM\PersistentCollection {#95089 …}
    #options: Doctrine\ORM\PersistentCollection {#95093 …}
    #associations: Doctrine\ORM\PersistentCollection {#95091 …}
    #createdAt: DateTime @1751040738 {#95064
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#95065
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95077 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96502
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95070}
        #id: 46649
        #name: "IEEE 1616.1:2023"
        #slug: "ieee-1616-1-2023-ieee00010939-244568"
        #description: """
          New IEEE Standard - Active.<br />\n
          The goals and metrics of a data storage system for automated driving (DSSAD) are defined in this standard. Functions and common technical requirements for data storage are identified. Data elements relevant to automated driving system (ADS) Level 3, Level 4 and Level 5 are defined. The usage of data among diverse end users is also defined. A compendium of data elements used in vehicles of categories M1 and N1 regarding their EDR and DSSAD for partial and fully automated vehicles is provided in this standard. An on-board diagnostic (OBD) port lockout/near field communication (NFC) protocol for protection against data manipulation via the vehicle diagnostic port is provided. This standard is made available without prejudice to national and regional laws related to data privacy, protection, and personal data processing. Users are responsible for compliance with all such laws and regulations. This standard may be frequently updated to include relevant data definitions and data elements toward the development of automated vehicles. The overall goal is to create a data collection standard for automated driving that includes functional requirements for automated vehicle gateways and security guidelines for cloud-based automotive data recorder requirements.<br />\n
          \t\t\t\t<br />\n
          This standard defines requirements and metrics for data storage in a data storage system for automated driving (DSSAD), as well as related functions and common technical requirements. A DSSAD is a device or function that records and stores a data set (“timestamped flags”) during the automated driving sequences of any vehicle equipped with Level 3, Level 4, or Level 5 automated driving systems (ADS). The standard conforms to a compendium of data elements used in vehicles of categories M1 (used for the carriage of passengers) and N1 [used for the carriage of goods (trucks)] regarding their event data recorder (EDR) and DSSAD for partial and fully automated vehicles, including relevant data elements to ADS Level 3, Level 4, and Level 5 (see Figure 1 for all ADS levels). This standard explains the means by whereby an EDR and a DSSAD interact. This standard is made available without prejudice to national, local, and regional laws and regulations related to data privacy, data protection, and personal data processing. Users are responsible for compliance with all such laws and regulations. This standard defines an onboard diagnostic connector (OBD-II) port lockout and near field communication (NFC) protocol for protection against data manipulation of EDR and DSSAD data via the vehicle diagnostic link connector (DLC). This standard does not include specifications for data retrieval tools and methods as that is subject to national and regional requirements.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Data Storage Systems for Automated Driving"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95079 …}
    #channels: Doctrine\ORM\PersistentCollection {#95085 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95081 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95083 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94967 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95071 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95066
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#95067
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#95068
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#95069
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#95073 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95075 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}