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

Response
200 OK
IP
216.73.216.149
Profiled on
Token
35a023

Components

4 Twig Components
8 Render Count
11 ms Render Time
120.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		3 0.79ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		3 2.63ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.39ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 8.82ms

Render calls

ProductState App\Twig\Components\ProductState 120.0 MiB 0.31 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93054
  +product: App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 120.0 MiB 0.39 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93234
  +product: App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 120.0 MiB 1.01 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93309
  +product: App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 120.0 MiB 0.21 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100265
  +product: App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 120.0 MiB 0.72 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100349
  +product: App\Entity\Product\Product {#7310
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751040419 {#7274
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 44685
        #name: "IEEE 2839:2021"
        #slug: "ieee-2839-2021-ieee00007666-244072"
        #description: """
          New IEEE Standard - Active.<br />\n
          Requirements for functions, performance, and interface and environmental conditions for vital computers used in rail safety-related systems are established in this recommended practice. Vital computer functions are developed based on the technology of computer systems, communication, and functional safety as well as security considerations. A vital computer is composed with basic functional modules such as main process, input, output, and communication. This recommended practice can be applied to vital computers for onboard and wayside equipment in rail applications. Application systems which are developed based on vital computers are not covered, but safety-related conditions for application systems are proposed. The internal structure and the technical realization of the vital computer are not constrained in this recommended practice.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines the functions, performance, interface, and environmental conditions of vital computers used in rail transportation systems such as railways, metros, light transport, and trams.<br />\n
          This recommended practice is applicable to vital computers for onboard and wayside equipment.<br />\n
          This recommended practice is not applicable to the application systems which are developed based on vital computers and does not define specific safety targets for application systems, but the safety-related conditions for application systems are proposed.<br />\n
          It is difficult to regulate internal structure and technical realization of vital computers, because of the great diversity that exists. In order to encourage technical competition and prompt the development of technology and industry, this recommended practice does not constrain or recommend the internal structure and technical realization of vital computers.<br />\n
          Only the preliminary interface is defined in this recommended practice, on a function level. The detailed interface of a vital computer is not covered and can be defined in the form of external interface specifications.<br />\n
          Compliance with the provisions of this recommended practice does not guarantee or ensure safety, security,health, or environmental protection. Users are responsible for observing all applicable legal and regulatory requirements.<br />\n
          The purpose of this recommended practice is to establish general requirements for vital computers, promote unified functions, performance, and interfaces to increase interchangeability of vital computers and compatibility between vital computers and systems, simplify system design and reduce the overall cost of manufacturing, operating, and maintaining systems.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Vital Computer for Rail Safety-Related Application"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#7292
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#7318
      date: 2021-09-23 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2839"
    -bookCollection: ""
    -pageCount: 29
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 120.0 MiB 8.82 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121623
    #id: 12094
    #code: "IEEE00007071"
    #attributes: Doctrine\ORM\PersistentCollection {#121606 …}
    #variants: Doctrine\ORM\PersistentCollection {#121604 …}
    #options: Doctrine\ORM\PersistentCollection {#121599 …}
    #associations: Doctrine\ORM\PersistentCollection {#121601 …}
    #createdAt: DateTime @1751040195 {#121596
      date: 2025-06-27 18:03:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121589
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121617 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121623}
        #id: 43385
        #name: "IEEE 802.3:2018"
        #slug: "ieee-802-3-2018-ieee00007071-243746"
        #description: """
          Revision Standard - Superseded.<br />\n
          Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 400 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) allow use of selected Physical Layer devices (PHY) for operation over coaxial, twisted pair or fiber optic cables, or electrical backplanes. System considerations for multisegment shared access networks describe the use of Repeaters that are defined for operational speeds up to 1000 Mb/s. Local Area Network (LAN) operation is supported at all speeds. Other specified capabilities include: various PHY types for access networks, PHYs suitable for metropolitan area network applications, and the provision of power over selected twisted pair PHY types.<br />\n
          \t\t\t\t<br />\n
          This standard defines Ethernet local area, access and metropolitan area networks. Ethernet is specified at selected speeds of operation; and uses a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) provide an architectural and optional implementation interface to selected Physical Layer entities (PHY). The Physical Layer encodes frames for transmission and decodes received frames with the modulation specified for the speed of operation, transmission medium and supported link length. Other specified capabilities include: control and management protocols, and the provision of power over selected twisted pair PHY types.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Ethernet"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121615 …}
    #channels: Doctrine\ORM\PersistentCollection {#121608 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121610 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121582
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1675033200 {#121631
      date: 2023-01-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1535666400 {#121602
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1535666400 {#121583
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "802.3"
    -bookCollection: ""
    -pageCount: 5600
    -documents: Doctrine\ORM\PersistentCollection {#121621 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121619 …}
  }
  "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 {#121679
  +product: App\Entity\Product\Product {#121623
    #id: 12094
    #code: "IEEE00007071"
    #attributes: Doctrine\ORM\PersistentCollection {#121606 …}
    #variants: Doctrine\ORM\PersistentCollection {#121604 …}
    #options: Doctrine\ORM\PersistentCollection {#121599 …}
    #associations: Doctrine\ORM\PersistentCollection {#121601 …}
    #createdAt: DateTime @1751040195 {#121596
      date: 2025-06-27 18:03:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121589
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121617 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121623}
        #id: 43385
        #name: "IEEE 802.3:2018"
        #slug: "ieee-802-3-2018-ieee00007071-243746"
        #description: """
          Revision Standard - Superseded.<br />\n
          Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 400 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) allow use of selected Physical Layer devices (PHY) for operation over coaxial, twisted pair or fiber optic cables, or electrical backplanes. System considerations for multisegment shared access networks describe the use of Repeaters that are defined for operational speeds up to 1000 Mb/s. Local Area Network (LAN) operation is supported at all speeds. Other specified capabilities include: various PHY types for access networks, PHYs suitable for metropolitan area network applications, and the provision of power over selected twisted pair PHY types.<br />\n
          \t\t\t\t<br />\n
          This standard defines Ethernet local area, access and metropolitan area networks. Ethernet is specified at selected speeds of operation; and uses a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) provide an architectural and optional implementation interface to selected Physical Layer entities (PHY). The Physical Layer encodes frames for transmission and decodes received frames with the modulation specified for the speed of operation, transmission medium and supported link length. Other specified capabilities include: control and management protocols, and the provision of power over selected twisted pair PHY types.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Ethernet"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121615 …}
    #channels: Doctrine\ORM\PersistentCollection {#121608 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121610 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121582
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1675033200 {#121631
      date: 2023-01-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1535666400 {#121602
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1535666400 {#121583
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "802.3"
    -bookCollection: ""
    -pageCount: 5600
    -documents: Doctrine\ORM\PersistentCollection {#121621 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121619 …}
  }
  +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 120.0 MiB 0.27 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121623
    #id: 12094
    #code: "IEEE00007071"
    #attributes: Doctrine\ORM\PersistentCollection {#121606 …}
    #variants: Doctrine\ORM\PersistentCollection {#121604 …}
    #options: Doctrine\ORM\PersistentCollection {#121599 …}
    #associations: Doctrine\ORM\PersistentCollection {#121601 …}
    #createdAt: DateTime @1751040195 {#121596
      date: 2025-06-27 18:03:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121589
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121617 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121623}
        #id: 43385
        #name: "IEEE 802.3:2018"
        #slug: "ieee-802-3-2018-ieee00007071-243746"
        #description: """
          Revision Standard - Superseded.<br />\n
          Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 400 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) allow use of selected Physical Layer devices (PHY) for operation over coaxial, twisted pair or fiber optic cables, or electrical backplanes. System considerations for multisegment shared access networks describe the use of Repeaters that are defined for operational speeds up to 1000 Mb/s. Local Area Network (LAN) operation is supported at all speeds. Other specified capabilities include: various PHY types for access networks, PHYs suitable for metropolitan area network applications, and the provision of power over selected twisted pair PHY types.<br />\n
          \t\t\t\t<br />\n
          This standard defines Ethernet local area, access and metropolitan area networks. Ethernet is specified at selected speeds of operation; and uses a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) provide an architectural and optional implementation interface to selected Physical Layer entities (PHY). The Physical Layer encodes frames for transmission and decodes received frames with the modulation specified for the speed of operation, transmission medium and supported link length. Other specified capabilities include: control and management protocols, and the provision of power over selected twisted pair PHY types.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Ethernet"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121615 …}
    #channels: Doctrine\ORM\PersistentCollection {#121608 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121610 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121582
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1675033200 {#121631
      date: 2023-01-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1535666400 {#121602
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1535666400 {#121583
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "802.3"
    -bookCollection: ""
    -pageCount: 5600
    -documents: Doctrine\ORM\PersistentCollection {#121621 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121619 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#121723
  +product: App\Entity\Product\Product {#121623
    #id: 12094
    #code: "IEEE00007071"
    #attributes: Doctrine\ORM\PersistentCollection {#121606 …}
    #variants: Doctrine\ORM\PersistentCollection {#121604 …}
    #options: Doctrine\ORM\PersistentCollection {#121599 …}
    #associations: Doctrine\ORM\PersistentCollection {#121601 …}
    #createdAt: DateTime @1751040195 {#121596
      date: 2025-06-27 18:03:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121589
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121617 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121623}
        #id: 43385
        #name: "IEEE 802.3:2018"
        #slug: "ieee-802-3-2018-ieee00007071-243746"
        #description: """
          Revision Standard - Superseded.<br />\n
          Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 400 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) allow use of selected Physical Layer devices (PHY) for operation over coaxial, twisted pair or fiber optic cables, or electrical backplanes. System considerations for multisegment shared access networks describe the use of Repeaters that are defined for operational speeds up to 1000 Mb/s. Local Area Network (LAN) operation is supported at all speeds. Other specified capabilities include: various PHY types for access networks, PHYs suitable for metropolitan area network applications, and the provision of power over selected twisted pair PHY types.<br />\n
          \t\t\t\t<br />\n
          This standard defines Ethernet local area, access and metropolitan area networks. Ethernet is specified at selected speeds of operation; and uses a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) provide an architectural and optional implementation interface to selected Physical Layer entities (PHY). The Physical Layer encodes frames for transmission and decodes received frames with the modulation specified for the speed of operation, transmission medium and supported link length. Other specified capabilities include: control and management protocols, and the provision of power over selected twisted pair PHY types.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Ethernet"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121615 …}
    #channels: Doctrine\ORM\PersistentCollection {#121608 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121610 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121582
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1675033200 {#121631
      date: 2023-01-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1535666400 {#121602
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1535666400 {#121583
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "802.3"
    -bookCollection: ""
    -pageCount: 5600
    -documents: Doctrine\ORM\PersistentCollection {#121621 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121619 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 120.0 MiB 0.90 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121623
    #id: 12094
    #code: "IEEE00007071"
    #attributes: Doctrine\ORM\PersistentCollection {#121606 …}
    #variants: Doctrine\ORM\PersistentCollection {#121604 …}
    #options: Doctrine\ORM\PersistentCollection {#121599 …}
    #associations: Doctrine\ORM\PersistentCollection {#121601 …}
    #createdAt: DateTime @1751040195 {#121596
      date: 2025-06-27 18:03:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121589
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121617 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121623}
        #id: 43385
        #name: "IEEE 802.3:2018"
        #slug: "ieee-802-3-2018-ieee00007071-243746"
        #description: """
          Revision Standard - Superseded.<br />\n
          Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 400 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) allow use of selected Physical Layer devices (PHY) for operation over coaxial, twisted pair or fiber optic cables, or electrical backplanes. System considerations for multisegment shared access networks describe the use of Repeaters that are defined for operational speeds up to 1000 Mb/s. Local Area Network (LAN) operation is supported at all speeds. Other specified capabilities include: various PHY types for access networks, PHYs suitable for metropolitan area network applications, and the provision of power over selected twisted pair PHY types.<br />\n
          \t\t\t\t<br />\n
          This standard defines Ethernet local area, access and metropolitan area networks. Ethernet is specified at selected speeds of operation; and uses a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) provide an architectural and optional implementation interface to selected Physical Layer entities (PHY). The Physical Layer encodes frames for transmission and decodes received frames with the modulation specified for the speed of operation, transmission medium and supported link length. Other specified capabilities include: control and management protocols, and the provision of power over selected twisted pair PHY types.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Ethernet"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121615 …}
    #channels: Doctrine\ORM\PersistentCollection {#121608 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121610 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121582
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1675033200 {#121631
      date: 2023-01-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1535666400 {#121602
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1535666400 {#121583
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "802.3"
    -bookCollection: ""
    -pageCount: 5600
    -documents: Doctrine\ORM\PersistentCollection {#121621 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121619 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#121800
  +product: App\Entity\Product\Product {#121623
    #id: 12094
    #code: "IEEE00007071"
    #attributes: Doctrine\ORM\PersistentCollection {#121606 …}
    #variants: Doctrine\ORM\PersistentCollection {#121604 …}
    #options: Doctrine\ORM\PersistentCollection {#121599 …}
    #associations: Doctrine\ORM\PersistentCollection {#121601 …}
    #createdAt: DateTime @1751040195 {#121596
      date: 2025-06-27 18:03:15.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#121589
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121617 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121721
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121623}
        #id: 43385
        #name: "IEEE 802.3:2018"
        #slug: "ieee-802-3-2018-ieee00007071-243746"
        #description: """
          Revision Standard - Superseded.<br />\n
          Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 400 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) allow use of selected Physical Layer devices (PHY) for operation over coaxial, twisted pair or fiber optic cables, or electrical backplanes. System considerations for multisegment shared access networks describe the use of Repeaters that are defined for operational speeds up to 1000 Mb/s. Local Area Network (LAN) operation is supported at all speeds. Other specified capabilities include: various PHY types for access networks, PHYs suitable for metropolitan area network applications, and the provision of power over selected twisted pair PHY types.<br />\n
          \t\t\t\t<br />\n
          This standard defines Ethernet local area, access and metropolitan area networks. Ethernet is specified at selected speeds of operation; and uses a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) provide an architectural and optional implementation interface to selected Physical Layer entities (PHY). The Physical Layer encodes frames for transmission and decodes received frames with the modulation specified for the speed of operation, transmission medium and supported link length. Other specified capabilities include: control and management protocols, and the provision of power over selected twisted pair PHY types.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Ethernet"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121615 …}
    #channels: Doctrine\ORM\PersistentCollection {#121608 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121610 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121625 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121582
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1675033200 {#121631
      date: 2023-01-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1535666400 {#121602
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1535666400 {#121583
      date: 2018-08-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "802.3"
    -bookCollection: ""
    -pageCount: 5600
    -documents: Doctrine\ORM\PersistentCollection {#121621 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121619 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}