GET https://dev.normadoc.fr/_partial/product/IEEE00010939/features

Response
200 OK
IP
216.73.216.149
Profiled on
Token
ddc63b

Components

4 Twig Components
8 Render Count
13 ms Render Time
278.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		3 0.82ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		3 2.46ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.22ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 10.55ms

Render calls

ProductState App\Twig\Components\ProductState 278.0 MiB 0.31 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93055
  +product: App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 278.0 MiB 0.22 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93235
  +product: App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 278.0 MiB 0.69 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93310
  +product: App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 278.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100266
  +product: App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 278.0 MiB 0.73 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100350
  +product: App\Entity\Product\Product {#7311
    #id: 12910
    #code: "IEEE00010939"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040738 {#7274
      date: 2025-06-27 18:12:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #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 {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1738796400 {#7292
      date: 2025-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1691100000 {#7318
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1691100000 {#7316
      date: 2023-08-04 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "1616.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 278.0 MiB 10.55 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121754
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#121759 …}
    #variants: Doctrine\ORM\PersistentCollection {#121757 …}
    #options: Doctrine\ORM\PersistentCollection {#121752 …}
    #associations: Doctrine\ORM\PersistentCollection {#121755 …}
    #createdAt: DateTime @1751040556 {#121748
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#121783
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121770 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121876
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121754}
        #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 {#121768 …}
    #channels: Doctrine\ORM\PersistentCollection {#121761 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121765 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121763 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121775 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121734
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#121782
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#121741
      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 {#121774 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121772 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#121827
  +product: App\Entity\Product\Product {#121754
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#121759 …}
    #variants: Doctrine\ORM\PersistentCollection {#121757 …}
    #options: Doctrine\ORM\PersistentCollection {#121752 …}
    #associations: Doctrine\ORM\PersistentCollection {#121755 …}
    #createdAt: DateTime @1751040556 {#121748
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#121783
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121770 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121876
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121754}
        #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 {#121768 …}
    #channels: Doctrine\ORM\PersistentCollection {#121761 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121765 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121763 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121775 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121734
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#121782
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#121741
      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 {#121774 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121772 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}
ProductState App\Twig\Components\ProductState 278.0 MiB 0.30 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121754
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#121759 …}
    #variants: Doctrine\ORM\PersistentCollection {#121757 …}
    #options: Doctrine\ORM\PersistentCollection {#121752 …}
    #associations: Doctrine\ORM\PersistentCollection {#121755 …}
    #createdAt: DateTime @1751040556 {#121748
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#121783
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121770 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121876
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121754}
        #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 {#121768 …}
    #channels: Doctrine\ORM\PersistentCollection {#121761 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121765 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121763 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121775 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121734
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#121782
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#121741
      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 {#121774 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121772 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#121878
  +product: App\Entity\Product\Product {#121754
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#121759 …}
    #variants: Doctrine\ORM\PersistentCollection {#121757 …}
    #options: Doctrine\ORM\PersistentCollection {#121752 …}
    #associations: Doctrine\ORM\PersistentCollection {#121755 …}
    #createdAt: DateTime @1751040556 {#121748
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#121783
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121770 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121876
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121754}
        #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 {#121768 …}
    #channels: Doctrine\ORM\PersistentCollection {#121761 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121765 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121763 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121775 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121734
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#121782
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#121741
      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 {#121774 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121772 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 278.0 MiB 1.05 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121754
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#121759 …}
    #variants: Doctrine\ORM\PersistentCollection {#121757 …}
    #options: Doctrine\ORM\PersistentCollection {#121752 …}
    #associations: Doctrine\ORM\PersistentCollection {#121755 …}
    #createdAt: DateTime @1751040556 {#121748
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#121783
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121770 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121876
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121754}
        #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 {#121768 …}
    #channels: Doctrine\ORM\PersistentCollection {#121761 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121765 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121763 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121775 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121734
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#121782
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#121741
      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 {#121774 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121772 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#121955
  +product: App\Entity\Product\Product {#121754
    #id: 12626
    #code: "IEEE00010329"
    #attributes: Doctrine\ORM\PersistentCollection {#121759 …}
    #variants: Doctrine\ORM\PersistentCollection {#121757 …}
    #options: Doctrine\ORM\PersistentCollection {#121752 …}
    #associations: Doctrine\ORM\PersistentCollection {#121755 …}
    #createdAt: DateTime @1751040556 {#121748
      date: 2025-06-27 18:09:16.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608642 {#121783
      date: 2025-08-08 01:17:22.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121770 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121876
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121754}
        #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 {#121768 …}
    #channels: Doctrine\ORM\PersistentCollection {#121761 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121765 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121763 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121775 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121734
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1650232800 {#121782
      date: 2022-04-18 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1639695600 {#121741
      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 {#121774 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121772 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}