Symfony Profiler

[
  "paddingClasses" => "p-2 px-lg-5 py-lg-0"
  "searchPlaceholder" => "sylius.ui.search"
  "showSearch" => "true"
  "searchValue" => "IEEE/ISO/IEC 15068-2:1999"
  "title" => "Search results"
]

App\Twig\Components\PageBanner {#94652
  +supTitle: null
  +title: "Search results"
  +subTitle: null
  +backUrl: null
  +backLabel: null
  +customClasses: null
  +backgroundType: null
  +centered: true
  +showSearch: true
  +searchPlaceholder: "sylius.ui.search"
  +searchValue: "IEEE/ISO/IEC 15068-2:1999"
  +paddingClasses: "p-2 px-lg-5 py-lg-0"
}

[
  "product" => App\Entity\Product\Product {#97251
    #id: 12935
    #code: "IEEE00011003"
    #attributes: Doctrine\ORM\PersistentCollection {#97268 …}
    #variants: Doctrine\ORM\PersistentCollection {#97270 …}
    #options: Doctrine\ORM\PersistentCollection {#97274 …}
    #associations: Doctrine\ORM\PersistentCollection {#97272 …}
    #createdAt: DateTime @1751040755 {#97245
      date: 2025-06-27 18:12:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97246
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97400
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97251}
        #id: 46749
        #name: "IEEE 1202:2023"
        #slug: "ieee-1202-2023-ieee00011003-244593"
        #description: """
          Revision Standard - Active.<br />\n
          Standardization of cable flame propagation testing is beneficial to cable manufacturers, distributors, and users. Uniform procedures; consistent, repeatable results; and measurable test acceptance criteria are required to allow comparisons among competing products and to allow selection of the correct product for the application. These criteria are detailed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides a protocol for exposing cable samples to a theoretical 20 kW (70 000 BTU/h) flaming ignition source for a 20-min test duration. The test determines the flame propagation tendency of single-conductor and multi-conductor cables intended for use in cable trays.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Flame-Propagation Testing of Wire and Cable"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97260 …}
    #channels: Doctrine\ORM\PersistentCollection {#97266 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97262 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97264 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97252 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97247
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1713304800 {#97248
      date: 2024-04-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1702940400 {#97249
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1702940400 {#97250
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1202"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#97254 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97256 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#95379
  +product: App\Entity\Product\Product {#97251
    #id: 12935
    #code: "IEEE00011003"
    #attributes: Doctrine\ORM\PersistentCollection {#97268 …}
    #variants: Doctrine\ORM\PersistentCollection {#97270 …}
    #options: Doctrine\ORM\PersistentCollection {#97274 …}
    #associations: Doctrine\ORM\PersistentCollection {#97272 …}
    #createdAt: DateTime @1751040755 {#97245
      date: 2025-06-27 18:12:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97246
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97400
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97251}
        #id: 46749
        #name: "IEEE 1202:2023"
        #slug: "ieee-1202-2023-ieee00011003-244593"
        #description: """
          Revision Standard - Active.<br />\n
          Standardization of cable flame propagation testing is beneficial to cable manufacturers, distributors, and users. Uniform procedures; consistent, repeatable results; and measurable test acceptance criteria are required to allow comparisons among competing products and to allow selection of the correct product for the application. These criteria are detailed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides a protocol for exposing cable samples to a theoretical 20 kW (70 000 BTU/h) flaming ignition source for a 20-min test duration. The test determines the flame propagation tendency of single-conductor and multi-conductor cables intended for use in cable trays.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Flame-Propagation Testing of Wire and Cable"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97260 …}
    #channels: Doctrine\ORM\PersistentCollection {#97266 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97262 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97264 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97252 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97247
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1713304800 {#97248
      date: 2024-04-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1702940400 {#97249
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1702940400 {#97250
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1202"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#97254 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97256 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#97251
    #id: 12935
    #code: "IEEE00011003"
    #attributes: Doctrine\ORM\PersistentCollection {#97268 …}
    #variants: Doctrine\ORM\PersistentCollection {#97270 …}
    #options: Doctrine\ORM\PersistentCollection {#97274 …}
    #associations: Doctrine\ORM\PersistentCollection {#97272 …}
    #createdAt: DateTime @1751040755 {#97245
      date: 2025-06-27 18:12:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97246
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97400
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97251}
        #id: 46749
        #name: "IEEE 1202:2023"
        #slug: "ieee-1202-2023-ieee00011003-244593"
        #description: """
          Revision Standard - Active.<br />\n
          Standardization of cable flame propagation testing is beneficial to cable manufacturers, distributors, and users. Uniform procedures; consistent, repeatable results; and measurable test acceptance criteria are required to allow comparisons among competing products and to allow selection of the correct product for the application. These criteria are detailed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides a protocol for exposing cable samples to a theoretical 20 kW (70 000 BTU/h) flaming ignition source for a 20-min test duration. The test determines the flame propagation tendency of single-conductor and multi-conductor cables intended for use in cable trays.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Flame-Propagation Testing of Wire and Cable"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97260 …}
    #channels: Doctrine\ORM\PersistentCollection {#97266 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97262 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97264 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97252 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97247
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1713304800 {#97248
      date: 2024-04-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1702940400 {#97249
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1702940400 {#97250
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1202"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#97254 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97256 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#97407
  +product: App\Entity\Product\Product {#97251
    #id: 12935
    #code: "IEEE00011003"
    #attributes: Doctrine\ORM\PersistentCollection {#97268 …}
    #variants: Doctrine\ORM\PersistentCollection {#97270 …}
    #options: Doctrine\ORM\PersistentCollection {#97274 …}
    #associations: Doctrine\ORM\PersistentCollection {#97272 …}
    #createdAt: DateTime @1751040755 {#97245
      date: 2025-06-27 18:12:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97246
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97400
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97251}
        #id: 46749
        #name: "IEEE 1202:2023"
        #slug: "ieee-1202-2023-ieee00011003-244593"
        #description: """
          Revision Standard - Active.<br />\n
          Standardization of cable flame propagation testing is beneficial to cable manufacturers, distributors, and users. Uniform procedures; consistent, repeatable results; and measurable test acceptance criteria are required to allow comparisons among competing products and to allow selection of the correct product for the application. These criteria are detailed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides a protocol for exposing cable samples to a theoretical 20 kW (70 000 BTU/h) flaming ignition source for a 20-min test duration. The test determines the flame propagation tendency of single-conductor and multi-conductor cables intended for use in cable trays.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Flame-Propagation Testing of Wire and Cable"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97260 …}
    #channels: Doctrine\ORM\PersistentCollection {#97266 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97262 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97264 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97252 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97247
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1713304800 {#97248
      date: 2024-04-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1702940400 {#97249
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1702940400 {#97250
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1202"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#97254 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97256 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97251
    #id: 12935
    #code: "IEEE00011003"
    #attributes: Doctrine\ORM\PersistentCollection {#97268 …}
    #variants: Doctrine\ORM\PersistentCollection {#97270 …}
    #options: Doctrine\ORM\PersistentCollection {#97274 …}
    #associations: Doctrine\ORM\PersistentCollection {#97272 …}
    #createdAt: DateTime @1751040755 {#97245
      date: 2025-06-27 18:12:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97246
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97400
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97251}
        #id: 46749
        #name: "IEEE 1202:2023"
        #slug: "ieee-1202-2023-ieee00011003-244593"
        #description: """
          Revision Standard - Active.<br />\n
          Standardization of cable flame propagation testing is beneficial to cable manufacturers, distributors, and users. Uniform procedures; consistent, repeatable results; and measurable test acceptance criteria are required to allow comparisons among competing products and to allow selection of the correct product for the application. These criteria are detailed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides a protocol for exposing cable samples to a theoretical 20 kW (70 000 BTU/h) flaming ignition source for a 20-min test duration. The test determines the flame propagation tendency of single-conductor and multi-conductor cables intended for use in cable trays.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Flame-Propagation Testing of Wire and Cable"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97260 …}
    #channels: Doctrine\ORM\PersistentCollection {#97266 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97262 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97264 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97252 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97247
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1713304800 {#97248
      date: 2024-04-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1702940400 {#97249
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1702940400 {#97250
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1202"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#97254 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97256 …}
  }
]

App\Twig\Components\ProductMostRecent {#97501
  +product: App\Entity\Product\Product {#97251
    #id: 12935
    #code: "IEEE00011003"
    #attributes: Doctrine\ORM\PersistentCollection {#97268 …}
    #variants: Doctrine\ORM\PersistentCollection {#97270 …}
    #options: Doctrine\ORM\PersistentCollection {#97274 …}
    #associations: Doctrine\ORM\PersistentCollection {#97272 …}
    #createdAt: DateTime @1751040755 {#97245
      date: 2025-06-27 18:12:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97246
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97258 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97400
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97251}
        #id: 46749
        #name: "IEEE 1202:2023"
        #slug: "ieee-1202-2023-ieee00011003-244593"
        #description: """
          Revision Standard - Active.<br />\n
          Standardization of cable flame propagation testing is beneficial to cable manufacturers, distributors, and users. Uniform procedures; consistent, repeatable results; and measurable test acceptance criteria are required to allow comparisons among competing products and to allow selection of the correct product for the application. These criteria are detailed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard provides a protocol for exposing cable samples to a theoretical 20 kW (70 000 BTU/h) flaming ignition source for a 20-min test duration. The test determines the flame propagation tendency of single-conductor and multi-conductor cables intended for use in cable trays.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Flame-Propagation Testing of Wire and Cable"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97260 …}
    #channels: Doctrine\ORM\PersistentCollection {#97266 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97262 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97264 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97252 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97247
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1713304800 {#97248
      date: 2024-04-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1702940400 {#97249
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1702940400 {#97250
      date: 2023-12-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1202"
    -bookCollection: ""
    -pageCount: 39
    -documents: Doctrine\ORM\PersistentCollection {#97254 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97256 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97190
    #id: 12933
    #code: "IEEE00010998"
    #attributes: Doctrine\ORM\PersistentCollection {#97207 …}
    #variants: Doctrine\ORM\PersistentCollection {#97209 …}
    #options: Doctrine\ORM\PersistentCollection {#97213 …}
    #associations: Doctrine\ORM\PersistentCollection {#97211 …}
    #createdAt: DateTime @1751040754 {#97184
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#97185
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97197 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97749
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97190}
        #id: 46741
        #name: "IEEE White Paper : Cybersecurity Guidelines Cloud Access:2022"
        #slug: "ieee-white-paper-cybersecurity-guidelines-cloud-access-2022-ieee00010998-244591"
        #description: """
           - Active.<br />\n
          Organizations demand immediate, uninterrupted access for their users, no matter where they are located. Digital business transformation efforts, adopting Software as a Service (SaaS), working from home (especially following the COVID-19 pandemic), and emerging edge computing platforms have changed how enterprises work. Digital business transformation requires anywhere, anytime access to applications and services--many of which are located in the cloud.<br />\n
          The enterprise perimeter can now be everywhere--a dynamically created, policy-based secure access service edge. Enterprises want to protect their assets from unauthorized entities. Still, they also want to keep business continuity by allowing trusted devices and users to access applications hosted on-premises or in the cloud. To achieve this, one of the most critical security layers is secure remote access. This paper presents the cloud security guidelines and best practices, emphasizing secure remote access.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Cybersecurity in Agile Cloud Computing--Cybersecurity Guidelines for Cloud Access"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97199 …}
    #channels: Doctrine\ORM\PersistentCollection {#97205 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97201 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97203 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97191 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97186
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664748000 {#97187
      date: 2022-10-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1664316000 {#97188
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1664316000 {#97189
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : Cybersecurity Guidelines Cloud "
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#97193 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97195 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#97727
  +product: App\Entity\Product\Product {#97190
    #id: 12933
    #code: "IEEE00010998"
    #attributes: Doctrine\ORM\PersistentCollection {#97207 …}
    #variants: Doctrine\ORM\PersistentCollection {#97209 …}
    #options: Doctrine\ORM\PersistentCollection {#97213 …}
    #associations: Doctrine\ORM\PersistentCollection {#97211 …}
    #createdAt: DateTime @1751040754 {#97184
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#97185
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97197 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97749
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97190}
        #id: 46741
        #name: "IEEE White Paper : Cybersecurity Guidelines Cloud Access:2022"
        #slug: "ieee-white-paper-cybersecurity-guidelines-cloud-access-2022-ieee00010998-244591"
        #description: """
           - Active.<br />\n
          Organizations demand immediate, uninterrupted access for their users, no matter where they are located. Digital business transformation efforts, adopting Software as a Service (SaaS), working from home (especially following the COVID-19 pandemic), and emerging edge computing platforms have changed how enterprises work. Digital business transformation requires anywhere, anytime access to applications and services--many of which are located in the cloud.<br />\n
          The enterprise perimeter can now be everywhere--a dynamically created, policy-based secure access service edge. Enterprises want to protect their assets from unauthorized entities. Still, they also want to keep business continuity by allowing trusted devices and users to access applications hosted on-premises or in the cloud. To achieve this, one of the most critical security layers is secure remote access. This paper presents the cloud security guidelines and best practices, emphasizing secure remote access.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Cybersecurity in Agile Cloud Computing--Cybersecurity Guidelines for Cloud Access"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97199 …}
    #channels: Doctrine\ORM\PersistentCollection {#97205 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97201 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97203 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97191 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97186
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664748000 {#97187
      date: 2022-10-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1664316000 {#97188
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1664316000 {#97189
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : Cybersecurity Guidelines Cloud "
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#97193 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97195 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#97190
    #id: 12933
    #code: "IEEE00010998"
    #attributes: Doctrine\ORM\PersistentCollection {#97207 …}
    #variants: Doctrine\ORM\PersistentCollection {#97209 …}
    #options: Doctrine\ORM\PersistentCollection {#97213 …}
    #associations: Doctrine\ORM\PersistentCollection {#97211 …}
    #createdAt: DateTime @1751040754 {#97184
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#97185
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97197 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97749
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97190}
        #id: 46741
        #name: "IEEE White Paper : Cybersecurity Guidelines Cloud Access:2022"
        #slug: "ieee-white-paper-cybersecurity-guidelines-cloud-access-2022-ieee00010998-244591"
        #description: """
           - Active.<br />\n
          Organizations demand immediate, uninterrupted access for their users, no matter where they are located. Digital business transformation efforts, adopting Software as a Service (SaaS), working from home (especially following the COVID-19 pandemic), and emerging edge computing platforms have changed how enterprises work. Digital business transformation requires anywhere, anytime access to applications and services--many of which are located in the cloud.<br />\n
          The enterprise perimeter can now be everywhere--a dynamically created, policy-based secure access service edge. Enterprises want to protect their assets from unauthorized entities. Still, they also want to keep business continuity by allowing trusted devices and users to access applications hosted on-premises or in the cloud. To achieve this, one of the most critical security layers is secure remote access. This paper presents the cloud security guidelines and best practices, emphasizing secure remote access.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Cybersecurity in Agile Cloud Computing--Cybersecurity Guidelines for Cloud Access"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97199 …}
    #channels: Doctrine\ORM\PersistentCollection {#97205 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97201 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97203 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97191 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97186
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664748000 {#97187
      date: 2022-10-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1664316000 {#97188
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1664316000 {#97189
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : Cybersecurity Guidelines Cloud "
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#97193 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97195 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#97756
  +product: App\Entity\Product\Product {#97190
    #id: 12933
    #code: "IEEE00010998"
    #attributes: Doctrine\ORM\PersistentCollection {#97207 …}
    #variants: Doctrine\ORM\PersistentCollection {#97209 …}
    #options: Doctrine\ORM\PersistentCollection {#97213 …}
    #associations: Doctrine\ORM\PersistentCollection {#97211 …}
    #createdAt: DateTime @1751040754 {#97184
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#97185
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97197 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97749
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97190}
        #id: 46741
        #name: "IEEE White Paper : Cybersecurity Guidelines Cloud Access:2022"
        #slug: "ieee-white-paper-cybersecurity-guidelines-cloud-access-2022-ieee00010998-244591"
        #description: """
           - Active.<br />\n
          Organizations demand immediate, uninterrupted access for their users, no matter where they are located. Digital business transformation efforts, adopting Software as a Service (SaaS), working from home (especially following the COVID-19 pandemic), and emerging edge computing platforms have changed how enterprises work. Digital business transformation requires anywhere, anytime access to applications and services--many of which are located in the cloud.<br />\n
          The enterprise perimeter can now be everywhere--a dynamically created, policy-based secure access service edge. Enterprises want to protect their assets from unauthorized entities. Still, they also want to keep business continuity by allowing trusted devices and users to access applications hosted on-premises or in the cloud. To achieve this, one of the most critical security layers is secure remote access. This paper presents the cloud security guidelines and best practices, emphasizing secure remote access.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Cybersecurity in Agile Cloud Computing--Cybersecurity Guidelines for Cloud Access"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97199 …}
    #channels: Doctrine\ORM\PersistentCollection {#97205 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97201 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97203 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97191 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97186
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664748000 {#97187
      date: 2022-10-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1664316000 {#97188
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1664316000 {#97189
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : Cybersecurity Guidelines Cloud "
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#97193 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97195 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97190
    #id: 12933
    #code: "IEEE00010998"
    #attributes: Doctrine\ORM\PersistentCollection {#97207 …}
    #variants: Doctrine\ORM\PersistentCollection {#97209 …}
    #options: Doctrine\ORM\PersistentCollection {#97213 …}
    #associations: Doctrine\ORM\PersistentCollection {#97211 …}
    #createdAt: DateTime @1751040754 {#97184
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#97185
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97197 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97749
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97190}
        #id: 46741
        #name: "IEEE White Paper : Cybersecurity Guidelines Cloud Access:2022"
        #slug: "ieee-white-paper-cybersecurity-guidelines-cloud-access-2022-ieee00010998-244591"
        #description: """
           - Active.<br />\n
          Organizations demand immediate, uninterrupted access for their users, no matter where they are located. Digital business transformation efforts, adopting Software as a Service (SaaS), working from home (especially following the COVID-19 pandemic), and emerging edge computing platforms have changed how enterprises work. Digital business transformation requires anywhere, anytime access to applications and services--many of which are located in the cloud.<br />\n
          The enterprise perimeter can now be everywhere--a dynamically created, policy-based secure access service edge. Enterprises want to protect their assets from unauthorized entities. Still, they also want to keep business continuity by allowing trusted devices and users to access applications hosted on-premises or in the cloud. To achieve this, one of the most critical security layers is secure remote access. This paper presents the cloud security guidelines and best practices, emphasizing secure remote access.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Cybersecurity in Agile Cloud Computing--Cybersecurity Guidelines for Cloud Access"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97199 …}
    #channels: Doctrine\ORM\PersistentCollection {#97205 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97201 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97203 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97191 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97186
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664748000 {#97187
      date: 2022-10-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1664316000 {#97188
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1664316000 {#97189
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : Cybersecurity Guidelines Cloud "
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#97193 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97195 …}
  }
]

App\Twig\Components\ProductMostRecent {#97833
  +product: App\Entity\Product\Product {#97190
    #id: 12933
    #code: "IEEE00010998"
    #attributes: Doctrine\ORM\PersistentCollection {#97207 …}
    #variants: Doctrine\ORM\PersistentCollection {#97209 …}
    #options: Doctrine\ORM\PersistentCollection {#97213 …}
    #associations: Doctrine\ORM\PersistentCollection {#97211 …}
    #createdAt: DateTime @1751040754 {#97184
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#97185
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97197 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97749
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97190}
        #id: 46741
        #name: "IEEE White Paper : Cybersecurity Guidelines Cloud Access:2022"
        #slug: "ieee-white-paper-cybersecurity-guidelines-cloud-access-2022-ieee00010998-244591"
        #description: """
           - Active.<br />\n
          Organizations demand immediate, uninterrupted access for their users, no matter where they are located. Digital business transformation efforts, adopting Software as a Service (SaaS), working from home (especially following the COVID-19 pandemic), and emerging edge computing platforms have changed how enterprises work. Digital business transformation requires anywhere, anytime access to applications and services--many of which are located in the cloud.<br />\n
          The enterprise perimeter can now be everywhere--a dynamically created, policy-based secure access service edge. Enterprises want to protect their assets from unauthorized entities. Still, they also want to keep business continuity by allowing trusted devices and users to access applications hosted on-premises or in the cloud. To achieve this, one of the most critical security layers is secure remote access. This paper presents the cloud security guidelines and best practices, emphasizing secure remote access.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Cybersecurity in Agile Cloud Computing--Cybersecurity Guidelines for Cloud Access"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97199 …}
    #channels: Doctrine\ORM\PersistentCollection {#97205 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97201 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97203 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97191 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97186
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664748000 {#97187
      date: 2022-10-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1664316000 {#97188
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1664316000 {#97189
      date: 2022-09-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : Cybersecurity Guidelines Cloud "
    -bookCollection: ""
    -pageCount: 36
    -documents: Doctrine\ORM\PersistentCollection {#97193 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97195 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97220
    #id: 12934
    #code: "IEEE00011001"
    #attributes: Doctrine\ORM\PersistentCollection {#97237 …}
    #variants: Doctrine\ORM\PersistentCollection {#97239 …}
    #options: Doctrine\ORM\PersistentCollection {#97243 …}
    #associations: Doctrine\ORM\PersistentCollection {#97241 …}
    #createdAt: DateTime @1751040754 {#97215
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97216
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97227 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97955
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97220}
        #id: 46745
        #name: "IEEE 1451.0:2024"
        #slug: "ieee-1451-0-2024-ieee00011001-244592"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This standard provides the common functions, network services, transducer services, and Transducer Electronic Data Sheet (TEDS) formats for members of the IEEE 1451 family of standards to be interoperable in both network interface and transducer interface. It defines the common functions and characteristics that are to be performed by a network capable application processor (NCAP) which is a 1451 server, and all devices that implement the NCAP. It defines a set of network services that include a set of commands and replies to access transducer data and TEDS data from the NCAP (1451 server) by the Internet of Things (IoT) applications (APPs) that are 1451 clients. Application programming interfaces (APIs) of network services are defined to facilitate communications between the APPs (1451 clients) and NCAPs. It also defines the common functions and characteristics that are to be performed by a transducer interface module (TIM) and all devices that implement the TIM. It defines a set of transducer services that include a set of commands and replies to facilitate the setup and control of the TIM as well as reading and writing the data used by the NCAP. APIs of transducer services are defined to facilitate communications between the NCAPs and TIMs. It specifies the formats for a TEDS and methods to access the TEDS. It also defines the common functions and characteristics that are to be performed by an APP and all devices that implement the APP.<br />\n
          \t\t\t\t<br />\n
          This standard develops a set of common functionality and Transducer Electronic Data Sheet (TEDS) formats for the family of IEEE 1451 smart transducer interface standards. This functionality is independent of the physical communications media and includes the common network services and transducer services required to control and manage smart transducers and TEDS. It defines a set of implementation-independent Application Programming Interfaces (APIs). This standard also defines universal unique identification, time synchronization, and security for the IEEE 1451 standards family. This project does not specify signal conditioning and conversion, physical media, or how the transducer data and TEDS data are used in applications.<br />\n
          There are several standards in the IEEE 1451 family that all share certain characteristics, but there exists no common set of network services, transducer services, and TEDS formats that facilitate interoperability among these standards. The purpose of this standard is to define a set of common network services, transducer services, and TEDS formats for IEEE 1451 smart transducers to achieve smart transducer interoperability and facilitate interoperability among the 1451 standards family. The IEEE 1451.0-2007 standard is revised to address the needs of new technologies, such as Cyber-Physical Systems (CPS) and Internet of Things (IoT) for smart cities and smart grids.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Approved Draft Standard for a Smart Transducer Interface for Sensors, Actuators, Devices, and Systems - Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97229 …}
    #channels: Doctrine\ORM\PersistentCollection {#97235 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97231 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97233 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97221 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97217
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740006000 {#97218
      date: 2025-02-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719352800 {#97219
      date: 2024-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1451.0"
    -bookCollection: ""
    -pageCount: 429
    -documents: Doctrine\ORM\PersistentCollection {#97223 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97225 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#97903
  +product: App\Entity\Product\Product {#97220
    #id: 12934
    #code: "IEEE00011001"
    #attributes: Doctrine\ORM\PersistentCollection {#97237 …}
    #variants: Doctrine\ORM\PersistentCollection {#97239 …}
    #options: Doctrine\ORM\PersistentCollection {#97243 …}
    #associations: Doctrine\ORM\PersistentCollection {#97241 …}
    #createdAt: DateTime @1751040754 {#97215
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97216
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97227 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97955
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97220}
        #id: 46745
        #name: "IEEE 1451.0:2024"
        #slug: "ieee-1451-0-2024-ieee00011001-244592"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This standard provides the common functions, network services, transducer services, and Transducer Electronic Data Sheet (TEDS) formats for members of the IEEE 1451 family of standards to be interoperable in both network interface and transducer interface. It defines the common functions and characteristics that are to be performed by a network capable application processor (NCAP) which is a 1451 server, and all devices that implement the NCAP. It defines a set of network services that include a set of commands and replies to access transducer data and TEDS data from the NCAP (1451 server) by the Internet of Things (IoT) applications (APPs) that are 1451 clients. Application programming interfaces (APIs) of network services are defined to facilitate communications between the APPs (1451 clients) and NCAPs. It also defines the common functions and characteristics that are to be performed by a transducer interface module (TIM) and all devices that implement the TIM. It defines a set of transducer services that include a set of commands and replies to facilitate the setup and control of the TIM as well as reading and writing the data used by the NCAP. APIs of transducer services are defined to facilitate communications between the NCAPs and TIMs. It specifies the formats for a TEDS and methods to access the TEDS. It also defines the common functions and characteristics that are to be performed by an APP and all devices that implement the APP.<br />\n
          \t\t\t\t<br />\n
          This standard develops a set of common functionality and Transducer Electronic Data Sheet (TEDS) formats for the family of IEEE 1451 smart transducer interface standards. This functionality is independent of the physical communications media and includes the common network services and transducer services required to control and manage smart transducers and TEDS. It defines a set of implementation-independent Application Programming Interfaces (APIs). This standard also defines universal unique identification, time synchronization, and security for the IEEE 1451 standards family. This project does not specify signal conditioning and conversion, physical media, or how the transducer data and TEDS data are used in applications.<br />\n
          There are several standards in the IEEE 1451 family that all share certain characteristics, but there exists no common set of network services, transducer services, and TEDS formats that facilitate interoperability among these standards. The purpose of this standard is to define a set of common network services, transducer services, and TEDS formats for IEEE 1451 smart transducers to achieve smart transducer interoperability and facilitate interoperability among the 1451 standards family. The IEEE 1451.0-2007 standard is revised to address the needs of new technologies, such as Cyber-Physical Systems (CPS) and Internet of Things (IoT) for smart cities and smart grids.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Approved Draft Standard for a Smart Transducer Interface for Sensors, Actuators, Devices, and Systems - Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97229 …}
    #channels: Doctrine\ORM\PersistentCollection {#97235 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97231 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97233 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97221 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97217
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740006000 {#97218
      date: 2025-02-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719352800 {#97219
      date: 2024-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1451.0"
    -bookCollection: ""
    -pageCount: 429
    -documents: Doctrine\ORM\PersistentCollection {#97223 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97225 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#97220
    #id: 12934
    #code: "IEEE00011001"
    #attributes: Doctrine\ORM\PersistentCollection {#97237 …}
    #variants: Doctrine\ORM\PersistentCollection {#97239 …}
    #options: Doctrine\ORM\PersistentCollection {#97243 …}
    #associations: Doctrine\ORM\PersistentCollection {#97241 …}
    #createdAt: DateTime @1751040754 {#97215
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97216
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97227 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97955
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97220}
        #id: 46745
        #name: "IEEE 1451.0:2024"
        #slug: "ieee-1451-0-2024-ieee00011001-244592"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This standard provides the common functions, network services, transducer services, and Transducer Electronic Data Sheet (TEDS) formats for members of the IEEE 1451 family of standards to be interoperable in both network interface and transducer interface. It defines the common functions and characteristics that are to be performed by a network capable application processor (NCAP) which is a 1451 server, and all devices that implement the NCAP. It defines a set of network services that include a set of commands and replies to access transducer data and TEDS data from the NCAP (1451 server) by the Internet of Things (IoT) applications (APPs) that are 1451 clients. Application programming interfaces (APIs) of network services are defined to facilitate communications between the APPs (1451 clients) and NCAPs. It also defines the common functions and characteristics that are to be performed by a transducer interface module (TIM) and all devices that implement the TIM. It defines a set of transducer services that include a set of commands and replies to facilitate the setup and control of the TIM as well as reading and writing the data used by the NCAP. APIs of transducer services are defined to facilitate communications between the NCAPs and TIMs. It specifies the formats for a TEDS and methods to access the TEDS. It also defines the common functions and characteristics that are to be performed by an APP and all devices that implement the APP.<br />\n
          \t\t\t\t<br />\n
          This standard develops a set of common functionality and Transducer Electronic Data Sheet (TEDS) formats for the family of IEEE 1451 smart transducer interface standards. This functionality is independent of the physical communications media and includes the common network services and transducer services required to control and manage smart transducers and TEDS. It defines a set of implementation-independent Application Programming Interfaces (APIs). This standard also defines universal unique identification, time synchronization, and security for the IEEE 1451 standards family. This project does not specify signal conditioning and conversion, physical media, or how the transducer data and TEDS data are used in applications.<br />\n
          There are several standards in the IEEE 1451 family that all share certain characteristics, but there exists no common set of network services, transducer services, and TEDS formats that facilitate interoperability among these standards. The purpose of this standard is to define a set of common network services, transducer services, and TEDS formats for IEEE 1451 smart transducers to achieve smart transducer interoperability and facilitate interoperability among the 1451 standards family. The IEEE 1451.0-2007 standard is revised to address the needs of new technologies, such as Cyber-Physical Systems (CPS) and Internet of Things (IoT) for smart cities and smart grids.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Approved Draft Standard for a Smart Transducer Interface for Sensors, Actuators, Devices, and Systems - Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97229 …}
    #channels: Doctrine\ORM\PersistentCollection {#97235 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97231 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97233 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97221 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97217
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740006000 {#97218
      date: 2025-02-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719352800 {#97219
      date: 2024-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1451.0"
    -bookCollection: ""
    -pageCount: 429
    -documents: Doctrine\ORM\PersistentCollection {#97223 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97225 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#97969
  +product: App\Entity\Product\Product {#97220
    #id: 12934
    #code: "IEEE00011001"
    #attributes: Doctrine\ORM\PersistentCollection {#97237 …}
    #variants: Doctrine\ORM\PersistentCollection {#97239 …}
    #options: Doctrine\ORM\PersistentCollection {#97243 …}
    #associations: Doctrine\ORM\PersistentCollection {#97241 …}
    #createdAt: DateTime @1751040754 {#97215
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97216
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97227 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97955
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97220}
        #id: 46745
        #name: "IEEE 1451.0:2024"
        #slug: "ieee-1451-0-2024-ieee00011001-244592"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This standard provides the common functions, network services, transducer services, and Transducer Electronic Data Sheet (TEDS) formats for members of the IEEE 1451 family of standards to be interoperable in both network interface and transducer interface. It defines the common functions and characteristics that are to be performed by a network capable application processor (NCAP) which is a 1451 server, and all devices that implement the NCAP. It defines a set of network services that include a set of commands and replies to access transducer data and TEDS data from the NCAP (1451 server) by the Internet of Things (IoT) applications (APPs) that are 1451 clients. Application programming interfaces (APIs) of network services are defined to facilitate communications between the APPs (1451 clients) and NCAPs. It also defines the common functions and characteristics that are to be performed by a transducer interface module (TIM) and all devices that implement the TIM. It defines a set of transducer services that include a set of commands and replies to facilitate the setup and control of the TIM as well as reading and writing the data used by the NCAP. APIs of transducer services are defined to facilitate communications between the NCAPs and TIMs. It specifies the formats for a TEDS and methods to access the TEDS. It also defines the common functions and characteristics that are to be performed by an APP and all devices that implement the APP.<br />\n
          \t\t\t\t<br />\n
          This standard develops a set of common functionality and Transducer Electronic Data Sheet (TEDS) formats for the family of IEEE 1451 smart transducer interface standards. This functionality is independent of the physical communications media and includes the common network services and transducer services required to control and manage smart transducers and TEDS. It defines a set of implementation-independent Application Programming Interfaces (APIs). This standard also defines universal unique identification, time synchronization, and security for the IEEE 1451 standards family. This project does not specify signal conditioning and conversion, physical media, or how the transducer data and TEDS data are used in applications.<br />\n
          There are several standards in the IEEE 1451 family that all share certain characteristics, but there exists no common set of network services, transducer services, and TEDS formats that facilitate interoperability among these standards. The purpose of this standard is to define a set of common network services, transducer services, and TEDS formats for IEEE 1451 smart transducers to achieve smart transducer interoperability and facilitate interoperability among the 1451 standards family. The IEEE 1451.0-2007 standard is revised to address the needs of new technologies, such as Cyber-Physical Systems (CPS) and Internet of Things (IoT) for smart cities and smart grids.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Approved Draft Standard for a Smart Transducer Interface for Sensors, Actuators, Devices, and Systems - Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97229 …}
    #channels: Doctrine\ORM\PersistentCollection {#97235 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97231 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97233 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97221 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97217
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740006000 {#97218
      date: 2025-02-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719352800 {#97219
      date: 2024-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1451.0"
    -bookCollection: ""
    -pageCount: 429
    -documents: Doctrine\ORM\PersistentCollection {#97223 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97225 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97220
    #id: 12934
    #code: "IEEE00011001"
    #attributes: Doctrine\ORM\PersistentCollection {#97237 …}
    #variants: Doctrine\ORM\PersistentCollection {#97239 …}
    #options: Doctrine\ORM\PersistentCollection {#97243 …}
    #associations: Doctrine\ORM\PersistentCollection {#97241 …}
    #createdAt: DateTime @1751040754 {#97215
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97216
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97227 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97955
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97220}
        #id: 46745
        #name: "IEEE 1451.0:2024"
        #slug: "ieee-1451-0-2024-ieee00011001-244592"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This standard provides the common functions, network services, transducer services, and Transducer Electronic Data Sheet (TEDS) formats for members of the IEEE 1451 family of standards to be interoperable in both network interface and transducer interface. It defines the common functions and characteristics that are to be performed by a network capable application processor (NCAP) which is a 1451 server, and all devices that implement the NCAP. It defines a set of network services that include a set of commands and replies to access transducer data and TEDS data from the NCAP (1451 server) by the Internet of Things (IoT) applications (APPs) that are 1451 clients. Application programming interfaces (APIs) of network services are defined to facilitate communications between the APPs (1451 clients) and NCAPs. It also defines the common functions and characteristics that are to be performed by a transducer interface module (TIM) and all devices that implement the TIM. It defines a set of transducer services that include a set of commands and replies to facilitate the setup and control of the TIM as well as reading and writing the data used by the NCAP. APIs of transducer services are defined to facilitate communications between the NCAPs and TIMs. It specifies the formats for a TEDS and methods to access the TEDS. It also defines the common functions and characteristics that are to be performed by an APP and all devices that implement the APP.<br />\n
          \t\t\t\t<br />\n
          This standard develops a set of common functionality and Transducer Electronic Data Sheet (TEDS) formats for the family of IEEE 1451 smart transducer interface standards. This functionality is independent of the physical communications media and includes the common network services and transducer services required to control and manage smart transducers and TEDS. It defines a set of implementation-independent Application Programming Interfaces (APIs). This standard also defines universal unique identification, time synchronization, and security for the IEEE 1451 standards family. This project does not specify signal conditioning and conversion, physical media, or how the transducer data and TEDS data are used in applications.<br />\n
          There are several standards in the IEEE 1451 family that all share certain characteristics, but there exists no common set of network services, transducer services, and TEDS formats that facilitate interoperability among these standards. The purpose of this standard is to define a set of common network services, transducer services, and TEDS formats for IEEE 1451 smart transducers to achieve smart transducer interoperability and facilitate interoperability among the 1451 standards family. The IEEE 1451.0-2007 standard is revised to address the needs of new technologies, such as Cyber-Physical Systems (CPS) and Internet of Things (IoT) for smart cities and smart grids.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Approved Draft Standard for a Smart Transducer Interface for Sensors, Actuators, Devices, and Systems - Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97229 …}
    #channels: Doctrine\ORM\PersistentCollection {#97235 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97231 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97233 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97221 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97217
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740006000 {#97218
      date: 2025-02-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719352800 {#97219
      date: 2024-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1451.0"
    -bookCollection: ""
    -pageCount: 429
    -documents: Doctrine\ORM\PersistentCollection {#97223 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97225 …}
  }
]

App\Twig\Components\ProductMostRecent {#98044
  +product: App\Entity\Product\Product {#97220
    #id: 12934
    #code: "IEEE00011001"
    #attributes: Doctrine\ORM\PersistentCollection {#97237 …}
    #variants: Doctrine\ORM\PersistentCollection {#97239 …}
    #options: Doctrine\ORM\PersistentCollection {#97243 …}
    #associations: Doctrine\ORM\PersistentCollection {#97241 …}
    #createdAt: DateTime @1751040754 {#97215
      date: 2025-06-27 18:12:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97216
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97227 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97955
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97220}
        #id: 46745
        #name: "IEEE 1451.0:2024"
        #slug: "ieee-1451-0-2024-ieee00011001-244592"
        #description: """
          Revision Standard - Active - Draft.<br />\n
          This standard provides the common functions, network services, transducer services, and Transducer Electronic Data Sheet (TEDS) formats for members of the IEEE 1451 family of standards to be interoperable in both network interface and transducer interface. It defines the common functions and characteristics that are to be performed by a network capable application processor (NCAP) which is a 1451 server, and all devices that implement the NCAP. It defines a set of network services that include a set of commands and replies to access transducer data and TEDS data from the NCAP (1451 server) by the Internet of Things (IoT) applications (APPs) that are 1451 clients. Application programming interfaces (APIs) of network services are defined to facilitate communications between the APPs (1451 clients) and NCAPs. It also defines the common functions and characteristics that are to be performed by a transducer interface module (TIM) and all devices that implement the TIM. It defines a set of transducer services that include a set of commands and replies to facilitate the setup and control of the TIM as well as reading and writing the data used by the NCAP. APIs of transducer services are defined to facilitate communications between the NCAPs and TIMs. It specifies the formats for a TEDS and methods to access the TEDS. It also defines the common functions and characteristics that are to be performed by an APP and all devices that implement the APP.<br />\n
          \t\t\t\t<br />\n
          This standard develops a set of common functionality and Transducer Electronic Data Sheet (TEDS) formats for the family of IEEE 1451 smart transducer interface standards. This functionality is independent of the physical communications media and includes the common network services and transducer services required to control and manage smart transducers and TEDS. It defines a set of implementation-independent Application Programming Interfaces (APIs). This standard also defines universal unique identification, time synchronization, and security for the IEEE 1451 standards family. This project does not specify signal conditioning and conversion, physical media, or how the transducer data and TEDS data are used in applications.<br />\n
          There are several standards in the IEEE 1451 family that all share certain characteristics, but there exists no common set of network services, transducer services, and TEDS formats that facilitate interoperability among these standards. The purpose of this standard is to define a set of common network services, transducer services, and TEDS formats for IEEE 1451 smart transducers to achieve smart transducer interoperability and facilitate interoperability among the 1451 standards family. The IEEE 1451.0-2007 standard is revised to address the needs of new technologies, such as Cyber-Physical Systems (CPS) and Internet of Things (IoT) for smart cities and smart grids.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Approved Draft Standard for a Smart Transducer Interface for Sensors, Actuators, Devices, and Systems - Common Functions, Communication Protocols, and Transducer Electronic Data Sheet (TEDS) Formats"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97229 …}
    #channels: Doctrine\ORM\PersistentCollection {#97235 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97231 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97233 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97221 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97217
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1740006000 {#97218
      date: 2025-02-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1719352800 {#97219
      date: 2024-06-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "IEEE 1451.0"
    -bookCollection: ""
    -pageCount: 429
    -documents: Doctrine\ORM\PersistentCollection {#97223 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97225 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97159
    #id: 12932
    #code: "IEEE00010996"
    #attributes: Doctrine\ORM\PersistentCollection {#97176 …}
    #variants: Doctrine\ORM\PersistentCollection {#97178 …}
    #options: Doctrine\ORM\PersistentCollection {#97182 …}
    #associations: Doctrine\ORM\PersistentCollection {#97180 …}
    #createdAt: DateTime @1751040753 {#97154
      date: 2025-06-27 18:12:33.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97155
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97166 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98186
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97159}
        #id: 46737
        #name: "IEEE C63.4:1981"
        #slug: "ieee-c63-4-1981-ieee00010996-244590"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard sets forth uniform methods of measurement of radio noise emitted from lowvoltage electrical and electronic equipment in the frequency range of 10 kHz to 1 GHz. Methods for the measurement of radiated and powerline conducted radio noise are covered and may be applied to any such equipment unless otherwise specified by individual equipment requirements. These methods apply to the measurement of individual components, units, or systems comprised of components and units. Additional methods may be added to this standard to fulfill future requirements as needed. Unless specifically called out, this standard is not intended for certification/approval of avionic equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard methods of measurement of readio-noise emissions from low-voltage electrical and electronic equipment in the range of 10 kHz to 1 GHz"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97168 …}
    #channels: Doctrine\ORM\PersistentCollection {#97174 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97170 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97172 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97160 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97156
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1662501600 {#97157
      date: 2022-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @354837600 {#97158
      date: 1981-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C63.4"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#97162 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97164 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#98166
  +product: App\Entity\Product\Product {#97159
    #id: 12932
    #code: "IEEE00010996"
    #attributes: Doctrine\ORM\PersistentCollection {#97176 …}
    #variants: Doctrine\ORM\PersistentCollection {#97178 …}
    #options: Doctrine\ORM\PersistentCollection {#97182 …}
    #associations: Doctrine\ORM\PersistentCollection {#97180 …}
    #createdAt: DateTime @1751040753 {#97154
      date: 2025-06-27 18:12:33.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97155
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97166 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98186
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97159}
        #id: 46737
        #name: "IEEE C63.4:1981"
        #slug: "ieee-c63-4-1981-ieee00010996-244590"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard sets forth uniform methods of measurement of radio noise emitted from lowvoltage electrical and electronic equipment in the frequency range of 10 kHz to 1 GHz. Methods for the measurement of radiated and powerline conducted radio noise are covered and may be applied to any such equipment unless otherwise specified by individual equipment requirements. These methods apply to the measurement of individual components, units, or systems comprised of components and units. Additional methods may be added to this standard to fulfill future requirements as needed. Unless specifically called out, this standard is not intended for certification/approval of avionic equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard methods of measurement of readio-noise emissions from low-voltage electrical and electronic equipment in the range of 10 kHz to 1 GHz"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97168 …}
    #channels: Doctrine\ORM\PersistentCollection {#97174 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97170 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97172 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97160 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97156
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1662501600 {#97157
      date: 2022-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @354837600 {#97158
      date: 1981-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C63.4"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#97162 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97164 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#97159
    #id: 12932
    #code: "IEEE00010996"
    #attributes: Doctrine\ORM\PersistentCollection {#97176 …}
    #variants: Doctrine\ORM\PersistentCollection {#97178 …}
    #options: Doctrine\ORM\PersistentCollection {#97182 …}
    #associations: Doctrine\ORM\PersistentCollection {#97180 …}
    #createdAt: DateTime @1751040753 {#97154
      date: 2025-06-27 18:12:33.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97155
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97166 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98186
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97159}
        #id: 46737
        #name: "IEEE C63.4:1981"
        #slug: "ieee-c63-4-1981-ieee00010996-244590"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard sets forth uniform methods of measurement of radio noise emitted from lowvoltage electrical and electronic equipment in the frequency range of 10 kHz to 1 GHz. Methods for the measurement of radiated and powerline conducted radio noise are covered and may be applied to any such equipment unless otherwise specified by individual equipment requirements. These methods apply to the measurement of individual components, units, or systems comprised of components and units. Additional methods may be added to this standard to fulfill future requirements as needed. Unless specifically called out, this standard is not intended for certification/approval of avionic equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard methods of measurement of readio-noise emissions from low-voltage electrical and electronic equipment in the range of 10 kHz to 1 GHz"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97168 …}
    #channels: Doctrine\ORM\PersistentCollection {#97174 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97170 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97172 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97160 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97156
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1662501600 {#97157
      date: 2022-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @354837600 {#97158
      date: 1981-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C63.4"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#97162 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97164 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#98193
  +product: App\Entity\Product\Product {#97159
    #id: 12932
    #code: "IEEE00010996"
    #attributes: Doctrine\ORM\PersistentCollection {#97176 …}
    #variants: Doctrine\ORM\PersistentCollection {#97178 …}
    #options: Doctrine\ORM\PersistentCollection {#97182 …}
    #associations: Doctrine\ORM\PersistentCollection {#97180 …}
    #createdAt: DateTime @1751040753 {#97154
      date: 2025-06-27 18:12:33.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97155
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97166 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98186
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97159}
        #id: 46737
        #name: "IEEE C63.4:1981"
        #slug: "ieee-c63-4-1981-ieee00010996-244590"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard sets forth uniform methods of measurement of radio noise emitted from lowvoltage electrical and electronic equipment in the frequency range of 10 kHz to 1 GHz. Methods for the measurement of radiated and powerline conducted radio noise are covered and may be applied to any such equipment unless otherwise specified by individual equipment requirements. These methods apply to the measurement of individual components, units, or systems comprised of components and units. Additional methods may be added to this standard to fulfill future requirements as needed. Unless specifically called out, this standard is not intended for certification/approval of avionic equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard methods of measurement of readio-noise emissions from low-voltage electrical and electronic equipment in the range of 10 kHz to 1 GHz"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97168 …}
    #channels: Doctrine\ORM\PersistentCollection {#97174 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97170 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97172 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97160 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97156
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1662501600 {#97157
      date: 2022-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @354837600 {#97158
      date: 1981-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C63.4"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#97162 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97164 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97159
    #id: 12932
    #code: "IEEE00010996"
    #attributes: Doctrine\ORM\PersistentCollection {#97176 …}
    #variants: Doctrine\ORM\PersistentCollection {#97178 …}
    #options: Doctrine\ORM\PersistentCollection {#97182 …}
    #associations: Doctrine\ORM\PersistentCollection {#97180 …}
    #createdAt: DateTime @1751040753 {#97154
      date: 2025-06-27 18:12:33.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97155
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97166 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98186
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97159}
        #id: 46737
        #name: "IEEE C63.4:1981"
        #slug: "ieee-c63-4-1981-ieee00010996-244590"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard sets forth uniform methods of measurement of radio noise emitted from lowvoltage electrical and electronic equipment in the frequency range of 10 kHz to 1 GHz. Methods for the measurement of radiated and powerline conducted radio noise are covered and may be applied to any such equipment unless otherwise specified by individual equipment requirements. These methods apply to the measurement of individual components, units, or systems comprised of components and units. Additional methods may be added to this standard to fulfill future requirements as needed. Unless specifically called out, this standard is not intended for certification/approval of avionic equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard methods of measurement of readio-noise emissions from low-voltage electrical and electronic equipment in the range of 10 kHz to 1 GHz"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97168 …}
    #channels: Doctrine\ORM\PersistentCollection {#97174 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97170 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97172 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97160 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97156
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1662501600 {#97157
      date: 2022-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @354837600 {#97158
      date: 1981-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C63.4"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#97162 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97164 …}
  }
]

App\Twig\Components\ProductMostRecent {#98269
  +product: App\Entity\Product\Product {#97159
    #id: 12932
    #code: "IEEE00010996"
    #attributes: Doctrine\ORM\PersistentCollection {#97176 …}
    #variants: Doctrine\ORM\PersistentCollection {#97178 …}
    #options: Doctrine\ORM\PersistentCollection {#97182 …}
    #associations: Doctrine\ORM\PersistentCollection {#97180 …}
    #createdAt: DateTime @1751040753 {#97154
      date: 2025-06-27 18:12:33.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97155
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97166 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98186
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97159}
        #id: 46737
        #name: "IEEE C63.4:1981"
        #slug: "ieee-c63-4-1981-ieee00010996-244590"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This standard sets forth uniform methods of measurement of radio noise emitted from lowvoltage electrical and electronic equipment in the frequency range of 10 kHz to 1 GHz. Methods for the measurement of radiated and powerline conducted radio noise are covered and may be applied to any such equipment unless otherwise specified by individual equipment requirements. These methods apply to the measurement of individual components, units, or systems comprised of components and units. Additional methods may be added to this standard to fulfill future requirements as needed. Unless specifically called out, this standard is not intended for certification/approval of avionic equipment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "American National Standard methods of measurement of readio-noise emissions from low-voltage electrical and electronic equipment in the range of 10 kHz to 1 GHz"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97168 …}
    #channels: Doctrine\ORM\PersistentCollection {#97174 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97170 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97172 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97160 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97156
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1662501600 {#97157
      date: 2022-09-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @354837600 {#97158
      date: 1981-03-31 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C63.4"
    -bookCollection: ""
    -pageCount: 16
    -documents: Doctrine\ORM\PersistentCollection {#97162 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97164 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97129
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#97146 …}
    #variants: Doctrine\ORM\PersistentCollection {#97148 …}
    #options: Doctrine\ORM\PersistentCollection {#97152 …}
    #associations: Doctrine\ORM\PersistentCollection {#97150 …}
    #createdAt: DateTime @1751040752 {#97124
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97125
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97136 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98394
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97129}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97138 …}
    #channels: Doctrine\ORM\PersistentCollection {#97144 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97140 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97142 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97130 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97126
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#97127
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#97128
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#97132 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97134 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#98374
  +product: App\Entity\Product\Product {#97129
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#97146 …}
    #variants: Doctrine\ORM\PersistentCollection {#97148 …}
    #options: Doctrine\ORM\PersistentCollection {#97152 …}
    #associations: Doctrine\ORM\PersistentCollection {#97150 …}
    #createdAt: DateTime @1751040752 {#97124
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97125
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97136 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98394
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97129}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97138 …}
    #channels: Doctrine\ORM\PersistentCollection {#97144 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97140 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97142 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97130 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97126
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#97127
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#97128
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#97132 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97134 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#97129
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#97146 …}
    #variants: Doctrine\ORM\PersistentCollection {#97148 …}
    #options: Doctrine\ORM\PersistentCollection {#97152 …}
    #associations: Doctrine\ORM\PersistentCollection {#97150 …}
    #createdAt: DateTime @1751040752 {#97124
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97125
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97136 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98394
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97129}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97138 …}
    #channels: Doctrine\ORM\PersistentCollection {#97144 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97140 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97142 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97130 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97126
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#97127
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#97128
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#97132 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97134 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#98408
  +product: App\Entity\Product\Product {#97129
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#97146 …}
    #variants: Doctrine\ORM\PersistentCollection {#97148 …}
    #options: Doctrine\ORM\PersistentCollection {#97152 …}
    #associations: Doctrine\ORM\PersistentCollection {#97150 …}
    #createdAt: DateTime @1751040752 {#97124
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97125
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97136 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98394
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97129}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97138 …}
    #channels: Doctrine\ORM\PersistentCollection {#97144 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97140 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97142 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97130 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97126
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#97127
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#97128
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#97132 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97134 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97129
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#97146 …}
    #variants: Doctrine\ORM\PersistentCollection {#97148 …}
    #options: Doctrine\ORM\PersistentCollection {#97152 …}
    #associations: Doctrine\ORM\PersistentCollection {#97150 …}
    #createdAt: DateTime @1751040752 {#97124
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97125
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97136 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98394
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97129}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97138 …}
    #channels: Doctrine\ORM\PersistentCollection {#97144 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97140 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97142 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97130 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97126
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#97127
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#97128
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#97132 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97134 …}
  }
]

App\Twig\Components\ProductMostRecent {#98482
  +product: App\Entity\Product\Product {#97129
    #id: 12931
    #code: "IEEE00010995"
    #attributes: Doctrine\ORM\PersistentCollection {#97146 …}
    #variants: Doctrine\ORM\PersistentCollection {#97148 …}
    #options: Doctrine\ORM\PersistentCollection {#97152 …}
    #associations: Doctrine\ORM\PersistentCollection {#97150 …}
    #createdAt: DateTime @1751040752 {#97124
      date: 2025-06-27 18:12:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97125
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97136 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98394
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97129}
        #id: 46733
        #name: "IEEE/ISO/IEC 32675:2021"
        #slug: "ieee-iso-iec-32675-2021-ieee00010995-244589"
        #description: """
          Adoption Standard - Active.<br />\n
          Technical principles and processes to build, package, and deploy systems and applications in a reliable and secure way are specified. Establishing effective compliance and information technology (IT) controls is the focus. DevOps principles presented include mission first, customer focus, left-shift, continuous everything, and systems thinking. How stakeholders, including developers and operations staff, can collaborate and communicate effectively is described. The process outcomes and activities herein are aligned with the process model specified in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.<br />\n
          \t\t\t\t<br />\n
          This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.<br />\n
          The purpose of this standard is to specify required practices for operations, development, and other key stakeholders to collaborate and communicate to deploy systems and applications in a secure and reliable way. This document provides a defined set of processes and methods to facilitate DevOps principles and practices, including improved communication between stakeholders throughout the systems life cycle, not just during development and operations. This document is written for DevOps stakeholders, which includes, but is not limited to, acquirers, suppliers, developers, integrators, operators, maintainers, managers, quality assurance managers, compliance managers, auditors, and users of software systems, products, and services. It can be used by a single organization in a self-imposed mode or in a multi-party situation. Parties can be from the same organization or from different organizations, and the situation can range from an informal agreement to a formal contract. The processes in this document can be used as a basis for implementing DevOps while establishing organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. The processes in this document provide guidance on the use of DevOps principles and practices for processes used by an organization to construct software life cycle models appropriate to its products and services. An organization, depending on its purpose, can select and apply an appropriate subset to fulfill that purpose. This document can be used in one or more of the following modes:<br />\n
          a) By an organization--to establish DevOps principles and practices in support of an environment of desired processes. These processes can be supported by an infrastructure of methods, procedures, techniques, tools, and trained personnel. The organization may then employ this environment to perform and manage its projects and progress software systems through their life cycle stages. In this mode, this document is used to assess conformance of a declared, established environment to its provisions. b) By a project--to establish DevOps principles and practices to help select, structure, and employ the elements of an established environment to provide products and services. In this mode, this document is used in the assessment of conformance of the project to the declared and established environment.<br />\n
          c) By an acquirer and a supplier--to establish DevOps principles and practices to help develop an agreement concerning processes and activities. Via the agreement, the processes and activities in this document are selected, negotiated, agreed to, and performed. The acquirer and supplier can be part of the same organization or separate organizations.<br />\n
          d) By process assessors--to establish DevOps principles and practices in a process reference model for use in the performance of process assessments that may be used to support organizational process improvement.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard--Information technology--DevOps--Building reliable and secure systems including application build, package and deployment"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97138 …}
    #channels: Doctrine\ORM\PersistentCollection {#97144 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97140 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97142 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97130 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97126
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1664143200 {#97127
      date: 2022-09-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1662588000 {#97128
      date: 2022-09-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "32675"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#97132 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97134 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#97099
    #id: 12930
    #code: "IEEE00010993"
    #attributes: Doctrine\ORM\PersistentCollection {#97116 …}
    #variants: Doctrine\ORM\PersistentCollection {#97118 …}
    #options: Doctrine\ORM\PersistentCollection {#97122 …}
    #associations: Doctrine\ORM\PersistentCollection {#97120 …}
    #createdAt: DateTime @1751040751 {#97093
      date: 2025-06-27 18:12:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97094
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97106 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98624
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97099}
        #id: 46729
        #name: "IEEE White Paper : AI Maturity Levels:2022"
        #slug: "ieee-white-paper-ai-maturity-levels-2022-ieee00010993-244588"
        #description: """
           - Active.<br />\n
          This white paper touches upon some important focus areas that can be of help in establishing a framework for determining industrial AI maturity levels. This includes establishing both technical as well as organizational readiness and sub-criteria therein for various AI maturity phases starting from exploration, experimentation, stabilization, expansion, and leading to AI enabled transformation. This sets the tone for setting up more detailed explorations to develop specific standards in this area, which will help in bridging gaps in expectations across multiple AI stakeholders, primarily the AI application providers and users/customers.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Industry Connections Program--Need for Establishing Industrial AI Maturity Levels"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97108 …}
    #channels: Doctrine\ORM\PersistentCollection {#97114 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97110 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97112 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97100 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97095
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1660082400 {#97096
      date: 2022-08-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1659650400 {#97097
      date: 2022-08-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1659650400 {#97098
      date: 2022-08-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : AI Maturity Levels"
    -bookCollection: ""
    -pageCount: 12
    -documents: Doctrine\ORM\PersistentCollection {#97102 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97104 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#98604
  +product: App\Entity\Product\Product {#97099
    #id: 12930
    #code: "IEEE00010993"
    #attributes: Doctrine\ORM\PersistentCollection {#97116 …}
    #variants: Doctrine\ORM\PersistentCollection {#97118 …}
    #options: Doctrine\ORM\PersistentCollection {#97122 …}
    #associations: Doctrine\ORM\PersistentCollection {#97120 …}
    #createdAt: DateTime @1751040751 {#97093
      date: 2025-06-27 18:12:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97094
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97106 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98624
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97099}
        #id: 46729
        #name: "IEEE White Paper : AI Maturity Levels:2022"
        #slug: "ieee-white-paper-ai-maturity-levels-2022-ieee00010993-244588"
        #description: """
           - Active.<br />\n
          This white paper touches upon some important focus areas that can be of help in establishing a framework for determining industrial AI maturity levels. This includes establishing both technical as well as organizational readiness and sub-criteria therein for various AI maturity phases starting from exploration, experimentation, stabilization, expansion, and leading to AI enabled transformation. This sets the tone for setting up more detailed explorations to develop specific standards in this area, which will help in bridging gaps in expectations across multiple AI stakeholders, primarily the AI application providers and users/customers.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Industry Connections Program--Need for Establishing Industrial AI Maturity Levels"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97108 …}
    #channels: Doctrine\ORM\PersistentCollection {#97114 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97110 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97112 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97100 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97095
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1660082400 {#97096
      date: 2022-08-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1659650400 {#97097
      date: 2022-08-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1659650400 {#97098
      date: 2022-08-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : AI Maturity Levels"
    -bookCollection: ""
    -pageCount: 12
    -documents: Doctrine\ORM\PersistentCollection {#97102 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97104 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#97099
    #id: 12930
    #code: "IEEE00010993"
    #attributes: Doctrine\ORM\PersistentCollection {#97116 …}
    #variants: Doctrine\ORM\PersistentCollection {#97118 …}
    #options: Doctrine\ORM\PersistentCollection {#97122 …}
    #associations: Doctrine\ORM\PersistentCollection {#97120 …}
    #createdAt: DateTime @1751040751 {#97093
      date: 2025-06-27 18:12:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#97094
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#97106 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#98624
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#97099}
        #id: 46729
        #name: "IEEE White Paper : AI Maturity Levels:2022"
        #slug: "ieee-white-paper-ai-maturity-levels-2022-ieee00010993-244588"
        #description: """
           - Active.<br />\n
          This white paper touches upon some important focus areas that can be of help in establishing a framework for determining industrial AI maturity levels. This includes establishing both technical as well as organizational readiness and sub-criteria therein for various AI maturity phases starting from exploration, experimentation, stabilization, expansion, and leading to AI enabled transformation. This sets the tone for setting up more detailed explorations to develop specific standards in this area, which will help in bridging gaps in expectations across multiple AI stakeholders, primarily the AI application providers and users/customers.<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Industry Connections Program--Need for Establishing Industrial AI Maturity Levels"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#97108 …}
    #channels: Doctrine\ORM\PersistentCollection {#97114 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#97110 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#97112 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95511 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#97100 …}
    -apiLastModifiedAt: DateTime @1754517600 {#97095
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1660082400 {#97096
      date: 2022-08-10 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1659650400 {#97097
      date: 2022-08-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1659650400 {#97098
      date: 2022-08-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "IEEE White Paper : AI Maturity Levels"
    -bookCollection: ""
    -pageCount: 12
    -documents: Doctrine\ORM\PersistentCollection {#97102 …}
    -favorites: Doctrine\ORM\PersistentCollection {#97104 …}
  }
]