GET https://dev.normadoc.fr/_fragment?_path=_format%3Dhtml%26_locale%3Den_US%26_controller%3Dsylius.controller.shop.security_widget%253A%253ArenderAction

Response
200 OK
IP
216.73.216.149
Profiled on
Token
13e8e3

Components

5 Twig Components
8 Render Count
26 ms Render Time
74.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		2 20.53ms
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		2 0.49ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		2 1.77ms
PageBanner 
"App\Twig\Components\PageBanner"
components/PageBanner.html.twig 		1 5.25ms
BackButton 
"App\Twig\Components\BackButton"
components/BackButton.html.twig 		1 0.26ms

Render calls

PageBanner App\Twig\Components\PageBanner 72.0 MiB 5.25 ms
Input props 
[
  "backLabel" => "45 : Railway engineering"
  "backUrl" => "/taxons/main/ics-2277/45-railway-engineering-5721"
  "paddingClasses" => "p-2 px-lg-5 py-lg-0"
  "searchPlaceholder" => "sylius.ui.search"
  "showSearch" => "true"
  "title" => "45.020 : Railway engineering in general"
]
Attributes 
[]
Component 
App\Twig\Components\PageBanner {#94209
  +supTitle: null
  +title: "45.020 : Railway engineering in general"
  +subTitle: null
  +backUrl: "/taxons/main/ics-2277/45-railway-engineering-5721"
  +backLabel: "45 : Railway engineering"
  +customClasses: null
  +backgroundType: null
  +centered: true
  +showSearch: true
  +searchPlaceholder: "sylius.ui.search"
  +searchValue: null
  +paddingClasses: "p-2 px-lg-5 py-lg-0"
}
BackButton App\Twig\Components\BackButton 72.0 MiB 0.26 ms
Input props 
[
  "url" => "/taxons/main/ics-2277/45-railway-engineering-5721"
  "label" => "45 : Railway engineering"
]
Attributes 
[]
Component 
App\Twig\Components\BackButton {#94300
  +label: "45 : Railway engineering"
  +url: "/taxons/main/ics-2277/45-railway-engineering-5721"
}
ProductCard App\Twig\Components\ProductCard 74.0 MiB 13.04 ms
Input props 
[
  "product" => App\Entity\Product\Product {#94786
    #id: 9421
    #code: "IEEE00002296"
    #attributes: Doctrine\ORM\PersistentCollection {#94849 …}
    #variants: Doctrine\ORM\PersistentCollection {#94847 …}
    #options: Doctrine\ORM\PersistentCollection {#94843 …}
    #associations: Doctrine\ORM\PersistentCollection {#94845 …}
    #createdAt: DateTime @1751038250 {#94780
      date: 2025-06-27 17:30:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#94788
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94859 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#94989
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94786}
        #id: 32693
        #name: "IEEE 1558:2004"
        #slug: "ieee-1558-2004-ieee00002296-241073"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard provides an outline for the software documentation that shall be developed and delivered for rail equipment and systems.<br />\n
          \t\t\t\t<br />\n
          This standard establishes the minimum requirements for application software documentation throughout the software development life cycle for rail equipment and systems including associated test and maintenance equipment.<br />\n
          Many different requirements for application software documentation are presently being specified for software used in rail equipment and systems and for related applications. This has led to a lack of standardization in the information provided on equipment and systems incorporating software. This standard, when used by the authority having jurisdiction, car builders and system/subsystem suppliers is intended to specify documents which improve the understanding of software functionality, facilitate software corrections and upgrades, improve on-time delivery, assist the development of quality software, and lower software acquisition and maintenance costs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Documentation for Rail Equipment and Systems"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94857 …}
    #channels: Doctrine\ORM\PersistentCollection {#94851 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94855 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94853 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94865 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581548400 {#94800
      date: 2020-02-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1111532400 {#94796
      date: 2005-03-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#94797
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1558"
    -bookCollection: ""
    -pageCount: 42
    -documents: Doctrine\ORM\PersistentCollection {#94863 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94861 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#94885
  +product: App\Entity\Product\Product {#94786
    #id: 9421
    #code: "IEEE00002296"
    #attributes: Doctrine\ORM\PersistentCollection {#94849 …}
    #variants: Doctrine\ORM\PersistentCollection {#94847 …}
    #options: Doctrine\ORM\PersistentCollection {#94843 …}
    #associations: Doctrine\ORM\PersistentCollection {#94845 …}
    #createdAt: DateTime @1751038250 {#94780
      date: 2025-06-27 17:30:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#94788
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94859 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#94989
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94786}
        #id: 32693
        #name: "IEEE 1558:2004"
        #slug: "ieee-1558-2004-ieee00002296-241073"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard provides an outline for the software documentation that shall be developed and delivered for rail equipment and systems.<br />\n
          \t\t\t\t<br />\n
          This standard establishes the minimum requirements for application software documentation throughout the software development life cycle for rail equipment and systems including associated test and maintenance equipment.<br />\n
          Many different requirements for application software documentation are presently being specified for software used in rail equipment and systems and for related applications. This has led to a lack of standardization in the information provided on equipment and systems incorporating software. This standard, when used by the authority having jurisdiction, car builders and system/subsystem suppliers is intended to specify documents which improve the understanding of software functionality, facilitate software corrections and upgrades, improve on-time delivery, assist the development of quality software, and lower software acquisition and maintenance costs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Documentation for Rail Equipment and Systems"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94857 …}
    #channels: Doctrine\ORM\PersistentCollection {#94851 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94855 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94853 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94865 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581548400 {#94800
      date: 2020-02-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1111532400 {#94796
      date: 2005-03-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#94797
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1558"
    -bookCollection: ""
    -pageCount: 42
    -documents: Doctrine\ORM\PersistentCollection {#94863 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94861 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 72.0 MiB 0.29 ms
Input props 
[
  "product" => App\Entity\Product\Product {#94786
    #id: 9421
    #code: "IEEE00002296"
    #attributes: Doctrine\ORM\PersistentCollection {#94849 …}
    #variants: Doctrine\ORM\PersistentCollection {#94847 …}
    #options: Doctrine\ORM\PersistentCollection {#94843 …}
    #associations: Doctrine\ORM\PersistentCollection {#94845 …}
    #createdAt: DateTime @1751038250 {#94780
      date: 2025-06-27 17:30:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#94788
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94859 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#94989
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94786}
        #id: 32693
        #name: "IEEE 1558:2004"
        #slug: "ieee-1558-2004-ieee00002296-241073"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard provides an outline for the software documentation that shall be developed and delivered for rail equipment and systems.<br />\n
          \t\t\t\t<br />\n
          This standard establishes the minimum requirements for application software documentation throughout the software development life cycle for rail equipment and systems including associated test and maintenance equipment.<br />\n
          Many different requirements for application software documentation are presently being specified for software used in rail equipment and systems and for related applications. This has led to a lack of standardization in the information provided on equipment and systems incorporating software. This standard, when used by the authority having jurisdiction, car builders and system/subsystem suppliers is intended to specify documents which improve the understanding of software functionality, facilitate software corrections and upgrades, improve on-time delivery, assist the development of quality software, and lower software acquisition and maintenance costs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Documentation for Rail Equipment and Systems"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94857 …}
    #channels: Doctrine\ORM\PersistentCollection {#94851 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94855 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94853 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94865 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581548400 {#94800
      date: 2020-02-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1111532400 {#94796
      date: 2005-03-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#94797
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1558"
    -bookCollection: ""
    -pageCount: 42
    -documents: Doctrine\ORM\PersistentCollection {#94863 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94861 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#94996
  +product: App\Entity\Product\Product {#94786
    #id: 9421
    #code: "IEEE00002296"
    #attributes: Doctrine\ORM\PersistentCollection {#94849 …}
    #variants: Doctrine\ORM\PersistentCollection {#94847 …}
    #options: Doctrine\ORM\PersistentCollection {#94843 …}
    #associations: Doctrine\ORM\PersistentCollection {#94845 …}
    #createdAt: DateTime @1751038250 {#94780
      date: 2025-06-27 17:30:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#94788
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94859 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#94989
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94786}
        #id: 32693
        #name: "IEEE 1558:2004"
        #slug: "ieee-1558-2004-ieee00002296-241073"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard provides an outline for the software documentation that shall be developed and delivered for rail equipment and systems.<br />\n
          \t\t\t\t<br />\n
          This standard establishes the minimum requirements for application software documentation throughout the software development life cycle for rail equipment and systems including associated test and maintenance equipment.<br />\n
          Many different requirements for application software documentation are presently being specified for software used in rail equipment and systems and for related applications. This has led to a lack of standardization in the information provided on equipment and systems incorporating software. This standard, when used by the authority having jurisdiction, car builders and system/subsystem suppliers is intended to specify documents which improve the understanding of software functionality, facilitate software corrections and upgrades, improve on-time delivery, assist the development of quality software, and lower software acquisition and maintenance costs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Documentation for Rail Equipment and Systems"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94857 …}
    #channels: Doctrine\ORM\PersistentCollection {#94851 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94855 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94853 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94865 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581548400 {#94800
      date: 2020-02-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1111532400 {#94796
      date: 2005-03-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#94797
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1558"
    -bookCollection: ""
    -pageCount: 42
    -documents: Doctrine\ORM\PersistentCollection {#94863 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94861 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 74.0 MiB 1.03 ms
Input props 
[
  "product" => App\Entity\Product\Product {#94786
    #id: 9421
    #code: "IEEE00002296"
    #attributes: Doctrine\ORM\PersistentCollection {#94849 …}
    #variants: Doctrine\ORM\PersistentCollection {#94847 …}
    #options: Doctrine\ORM\PersistentCollection {#94843 …}
    #associations: Doctrine\ORM\PersistentCollection {#94845 …}
    #createdAt: DateTime @1751038250 {#94780
      date: 2025-06-27 17:30:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#94788
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94859 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#94989
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94786}
        #id: 32693
        #name: "IEEE 1558:2004"
        #slug: "ieee-1558-2004-ieee00002296-241073"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard provides an outline for the software documentation that shall be developed and delivered for rail equipment and systems.<br />\n
          \t\t\t\t<br />\n
          This standard establishes the minimum requirements for application software documentation throughout the software development life cycle for rail equipment and systems including associated test and maintenance equipment.<br />\n
          Many different requirements for application software documentation are presently being specified for software used in rail equipment and systems and for related applications. This has led to a lack of standardization in the information provided on equipment and systems incorporating software. This standard, when used by the authority having jurisdiction, car builders and system/subsystem suppliers is intended to specify documents which improve the understanding of software functionality, facilitate software corrections and upgrades, improve on-time delivery, assist the development of quality software, and lower software acquisition and maintenance costs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Documentation for Rail Equipment and Systems"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94857 …}
    #channels: Doctrine\ORM\PersistentCollection {#94851 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94855 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94853 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94865 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581548400 {#94800
      date: 2020-02-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1111532400 {#94796
      date: 2005-03-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#94797
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1558"
    -bookCollection: ""
    -pageCount: 42
    -documents: Doctrine\ORM\PersistentCollection {#94863 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94861 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#95089
  +product: App\Entity\Product\Product {#94786
    #id: 9421
    #code: "IEEE00002296"
    #attributes: Doctrine\ORM\PersistentCollection {#94849 …}
    #variants: Doctrine\ORM\PersistentCollection {#94847 …}
    #options: Doctrine\ORM\PersistentCollection {#94843 …}
    #associations: Doctrine\ORM\PersistentCollection {#94845 …}
    #createdAt: DateTime @1751038250 {#94780
      date: 2025-06-27 17:30:50.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#94788
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94859 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#94989
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94786}
        #id: 32693
        #name: "IEEE 1558:2004"
        #slug: "ieee-1558-2004-ieee00002296-241073"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This standard provides an outline for the software documentation that shall be developed and delivered for rail equipment and systems.<br />\n
          \t\t\t\t<br />\n
          This standard establishes the minimum requirements for application software documentation throughout the software development life cycle for rail equipment and systems including associated test and maintenance equipment.<br />\n
          Many different requirements for application software documentation are presently being specified for software used in rail equipment and systems and for related applications. This has led to a lack of standardization in the information provided on equipment and systems incorporating software. This standard, when used by the authority having jurisdiction, car builders and system/subsystem suppliers is intended to specify documents which improve the understanding of software functionality, facilitate software corrections and upgrades, improve on-time delivery, assist the development of quality software, and lower software acquisition and maintenance costs.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Software Documentation for Rail Equipment and Systems"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94857 …}
    #channels: Doctrine\ORM\PersistentCollection {#94851 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94855 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94853 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94865 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94795
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581548400 {#94800
      date: 2020-02-13 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1111532400 {#94796
      date: 2005-03-23 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#94797
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1558"
    -bookCollection: ""
    -pageCount: 42
    -documents: Doctrine\ORM\PersistentCollection {#94863 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94861 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 74.0 MiB 7.49 ms
Input props 
[
  "product" => App\Entity\Product\Product {#94836
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#94830 …}
    #variants: Doctrine\ORM\PersistentCollection {#94832 …}
    #options: Doctrine\ORM\PersistentCollection {#94867 …}
    #associations: Doctrine\ORM\PersistentCollection {#94834 …}
    #createdAt: DateTime @1751040419 {#94841
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#94840
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95319
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94836}
        #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 {#94816 …}
    #channels: Doctrine\ORM\PersistentCollection {#94828 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94824 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94826 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94814 …}
    -apiLastModifiedAt: DateTime @1743289200 {#94839
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#94838
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#94837
      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 {#94811 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94807 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#95297
  +product: App\Entity\Product\Product {#94836
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#94830 …}
    #variants: Doctrine\ORM\PersistentCollection {#94832 …}
    #options: Doctrine\ORM\PersistentCollection {#94867 …}
    #associations: Doctrine\ORM\PersistentCollection {#94834 …}
    #createdAt: DateTime @1751040419 {#94841
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#94840
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95319
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94836}
        #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 {#94816 …}
    #channels: Doctrine\ORM\PersistentCollection {#94828 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94824 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94826 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94814 …}
    -apiLastModifiedAt: DateTime @1743289200 {#94839
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#94838
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#94837
      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 {#94811 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94807 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}
ProductState App\Twig\Components\ProductState 74.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#94836
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#94830 …}
    #variants: Doctrine\ORM\PersistentCollection {#94832 …}
    #options: Doctrine\ORM\PersistentCollection {#94867 …}
    #associations: Doctrine\ORM\PersistentCollection {#94834 …}
    #createdAt: DateTime @1751040419 {#94841
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#94840
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95319
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94836}
        #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 {#94816 …}
    #channels: Doctrine\ORM\PersistentCollection {#94828 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94824 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94826 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94814 …}
    -apiLastModifiedAt: DateTime @1743289200 {#94839
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#94838
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#94837
      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 {#94811 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94807 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#95333
  +product: App\Entity\Product\Product {#94836
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#94830 …}
    #variants: Doctrine\ORM\PersistentCollection {#94832 …}
    #options: Doctrine\ORM\PersistentCollection {#94867 …}
    #associations: Doctrine\ORM\PersistentCollection {#94834 …}
    #createdAt: DateTime @1751040419 {#94841
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#94840
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95319
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94836}
        #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 {#94816 …}
    #channels: Doctrine\ORM\PersistentCollection {#94828 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94824 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94826 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94814 …}
    -apiLastModifiedAt: DateTime @1743289200 {#94839
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#94838
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#94837
      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 {#94811 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94807 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 74.0 MiB 0.73 ms
Input props 
[
  "product" => App\Entity\Product\Product {#94836
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#94830 …}
    #variants: Doctrine\ORM\PersistentCollection {#94832 …}
    #options: Doctrine\ORM\PersistentCollection {#94867 …}
    #associations: Doctrine\ORM\PersistentCollection {#94834 …}
    #createdAt: DateTime @1751040419 {#94841
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#94840
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95319
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94836}
        #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 {#94816 …}
    #channels: Doctrine\ORM\PersistentCollection {#94828 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94824 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94826 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94814 …}
    -apiLastModifiedAt: DateTime @1743289200 {#94839
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#94838
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#94837
      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 {#94811 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94807 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#95407
  +product: App\Entity\Product\Product {#94836
    #id: 12419
    #code: "IEEE00007666"
    #attributes: Doctrine\ORM\PersistentCollection {#94830 …}
    #variants: Doctrine\ORM\PersistentCollection {#94832 …}
    #options: Doctrine\ORM\PersistentCollection {#94867 …}
    #associations: Doctrine\ORM\PersistentCollection {#94834 …}
    #createdAt: DateTime @1751040419 {#94841
      date: 2025-06-27 18:06:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#94840
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94805 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95319
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94836}
        #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 {#94816 …}
    #channels: Doctrine\ORM\PersistentCollection {#94828 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94824 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94826 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94866 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94814 …}
    -apiLastModifiedAt: DateTime @1743289200 {#94839
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1635112800 {#94838
      date: 2021-10-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1632348000 {#94837
      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 {#94811 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94807 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}