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 {#94536
  +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 {#95449
    #id: 9878
    #code: "IEEE00003142"
    #attributes: Doctrine\ORM\PersistentCollection {#95466 …}
    #variants: Doctrine\ORM\PersistentCollection {#95468 …}
    #options: Doctrine\ORM\PersistentCollection {#95472 …}
    #associations: Doctrine\ORM\PersistentCollection {#95470 …}
    #createdAt: DateTime @1751038632 {#95442
      date: 2025-06-27 17:37:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95443
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95456 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95871
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95449}
        #id: 34521
        #name: "IEEE 95:2002 (R2012)"
        #slug: "ieee-95-2002-r2012-ieee00003142-241530"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This recommended practice provides information on the use of high direct voltage forproof tests and for periodic diagnostic tests on the groundwall insulation of stator (armature) wind-ings in ac electric machines.<br />\n
          \t\t\t\t<br />\n
          This project will present uniform methods for testing insulation with direct voltages. It applies to AC electric machines. It covers acceptance testing of new equipment in the factory or in the field after erection and routine maintenance testing of machines that have been in service.<br />\n
          The purpose of this project is to bring IEEE Std 95 up to the state of the art since it has been in use for more than five years.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Insulation Testing of AC Electric Machinery (2300 V and Above) With High Direct Voltage"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95458 …}
    #channels: Doctrine\ORM\PersistentCollection {#95464 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95460 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95462 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95450 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95444
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1684274400 {#95445
      date: 2023-05-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1018562400 {#95446
      date: 2002-04-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1346277600 {#95447
      date: 2012-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#95448
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "95"
    -bookCollection: ""
    -pageCount: 56
    -documents: Doctrine\ORM\PersistentCollection {#95452 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95454 …}
  }
  "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 {#95751
  +product: App\Entity\Product\Product {#95449
    #id: 9878
    #code: "IEEE00003142"
    #attributes: Doctrine\ORM\PersistentCollection {#95466 …}
    #variants: Doctrine\ORM\PersistentCollection {#95468 …}
    #options: Doctrine\ORM\PersistentCollection {#95472 …}
    #associations: Doctrine\ORM\PersistentCollection {#95470 …}
    #createdAt: DateTime @1751038632 {#95442
      date: 2025-06-27 17:37:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95443
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95456 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95871
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95449}
        #id: 34521
        #name: "IEEE 95:2002 (R2012)"
        #slug: "ieee-95-2002-r2012-ieee00003142-241530"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This recommended practice provides information on the use of high direct voltage forproof tests and for periodic diagnostic tests on the groundwall insulation of stator (armature) wind-ings in ac electric machines.<br />\n
          \t\t\t\t<br />\n
          This project will present uniform methods for testing insulation with direct voltages. It applies to AC electric machines. It covers acceptance testing of new equipment in the factory or in the field after erection and routine maintenance testing of machines that have been in service.<br />\n
          The purpose of this project is to bring IEEE Std 95 up to the state of the art since it has been in use for more than five years.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Insulation Testing of AC Electric Machinery (2300 V and Above) With High Direct Voltage"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95458 …}
    #channels: Doctrine\ORM\PersistentCollection {#95464 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95460 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95462 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95450 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95444
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1684274400 {#95445
      date: 2023-05-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1018562400 {#95446
      date: 2002-04-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1346277600 {#95447
      date: 2012-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#95448
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "95"
    -bookCollection: ""
    -pageCount: 56
    -documents: Doctrine\ORM\PersistentCollection {#95452 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95454 …}
  }
  +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 {#95449
    #id: 9878
    #code: "IEEE00003142"
    #attributes: Doctrine\ORM\PersistentCollection {#95466 …}
    #variants: Doctrine\ORM\PersistentCollection {#95468 …}
    #options: Doctrine\ORM\PersistentCollection {#95472 …}
    #associations: Doctrine\ORM\PersistentCollection {#95470 …}
    #createdAt: DateTime @1751038632 {#95442
      date: 2025-06-27 17:37:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95443
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95456 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95871
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95449}
        #id: 34521
        #name: "IEEE 95:2002 (R2012)"
        #slug: "ieee-95-2002-r2012-ieee00003142-241530"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This recommended practice provides information on the use of high direct voltage forproof tests and for periodic diagnostic tests on the groundwall insulation of stator (armature) wind-ings in ac electric machines.<br />\n
          \t\t\t\t<br />\n
          This project will present uniform methods for testing insulation with direct voltages. It applies to AC electric machines. It covers acceptance testing of new equipment in the factory or in the field after erection and routine maintenance testing of machines that have been in service.<br />\n
          The purpose of this project is to bring IEEE Std 95 up to the state of the art since it has been in use for more than five years.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Insulation Testing of AC Electric Machinery (2300 V and Above) With High Direct Voltage"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95458 …}
    #channels: Doctrine\ORM\PersistentCollection {#95464 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95460 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95462 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95450 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95444
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1684274400 {#95445
      date: 2023-05-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1018562400 {#95446
      date: 2002-04-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1346277600 {#95447
      date: 2012-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#95448
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "95"
    -bookCollection: ""
    -pageCount: 56
    -documents: Doctrine\ORM\PersistentCollection {#95452 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95454 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#95878
  +product: App\Entity\Product\Product {#95449
    #id: 9878
    #code: "IEEE00003142"
    #attributes: Doctrine\ORM\PersistentCollection {#95466 …}
    #variants: Doctrine\ORM\PersistentCollection {#95468 …}
    #options: Doctrine\ORM\PersistentCollection {#95472 …}
    #associations: Doctrine\ORM\PersistentCollection {#95470 …}
    #createdAt: DateTime @1751038632 {#95442
      date: 2025-06-27 17:37:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95443
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95456 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95871
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95449}
        #id: 34521
        #name: "IEEE 95:2002 (R2012)"
        #slug: "ieee-95-2002-r2012-ieee00003142-241530"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This recommended practice provides information on the use of high direct voltage forproof tests and for periodic diagnostic tests on the groundwall insulation of stator (armature) wind-ings in ac electric machines.<br />\n
          \t\t\t\t<br />\n
          This project will present uniform methods for testing insulation with direct voltages. It applies to AC electric machines. It covers acceptance testing of new equipment in the factory or in the field after erection and routine maintenance testing of machines that have been in service.<br />\n
          The purpose of this project is to bring IEEE Std 95 up to the state of the art since it has been in use for more than five years.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Insulation Testing of AC Electric Machinery (2300 V and Above) With High Direct Voltage"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95458 …}
    #channels: Doctrine\ORM\PersistentCollection {#95464 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95460 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95462 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95450 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95444
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1684274400 {#95445
      date: 2023-05-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1018562400 {#95446
      date: 2002-04-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1346277600 {#95447
      date: 2012-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#95448
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "95"
    -bookCollection: ""
    -pageCount: 56
    -documents: Doctrine\ORM\PersistentCollection {#95452 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95454 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95449
    #id: 9878
    #code: "IEEE00003142"
    #attributes: Doctrine\ORM\PersistentCollection {#95466 …}
    #variants: Doctrine\ORM\PersistentCollection {#95468 …}
    #options: Doctrine\ORM\PersistentCollection {#95472 …}
    #associations: Doctrine\ORM\PersistentCollection {#95470 …}
    #createdAt: DateTime @1751038632 {#95442
      date: 2025-06-27 17:37:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95443
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95456 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95871
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95449}
        #id: 34521
        #name: "IEEE 95:2002 (R2012)"
        #slug: "ieee-95-2002-r2012-ieee00003142-241530"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This recommended practice provides information on the use of high direct voltage forproof tests and for periodic diagnostic tests on the groundwall insulation of stator (armature) wind-ings in ac electric machines.<br />\n
          \t\t\t\t<br />\n
          This project will present uniform methods for testing insulation with direct voltages. It applies to AC electric machines. It covers acceptance testing of new equipment in the factory or in the field after erection and routine maintenance testing of machines that have been in service.<br />\n
          The purpose of this project is to bring IEEE Std 95 up to the state of the art since it has been in use for more than five years.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Insulation Testing of AC Electric Machinery (2300 V and Above) With High Direct Voltage"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95458 …}
    #channels: Doctrine\ORM\PersistentCollection {#95464 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95460 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95462 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95450 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95444
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1684274400 {#95445
      date: 2023-05-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1018562400 {#95446
      date: 2002-04-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1346277600 {#95447
      date: 2012-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#95448
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "95"
    -bookCollection: ""
    -pageCount: 56
    -documents: Doctrine\ORM\PersistentCollection {#95452 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95454 …}
  }
]

App\Twig\Components\ProductMostRecent {#95971
  +product: App\Entity\Product\Product {#95449
    #id: 9878
    #code: "IEEE00003142"
    #attributes: Doctrine\ORM\PersistentCollection {#95466 …}
    #variants: Doctrine\ORM\PersistentCollection {#95468 …}
    #options: Doctrine\ORM\PersistentCollection {#95472 …}
    #associations: Doctrine\ORM\PersistentCollection {#95470 …}
    #createdAt: DateTime @1751038632 {#95442
      date: 2025-06-27 17:37:12.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95443
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95456 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95871
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95449}
        #id: 34521
        #name: "IEEE 95:2002 (R2012)"
        #slug: "ieee-95-2002-r2012-ieee00003142-241530"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This recommended practice provides information on the use of high direct voltage forproof tests and for periodic diagnostic tests on the groundwall insulation of stator (armature) wind-ings in ac electric machines.<br />\n
          \t\t\t\t<br />\n
          This project will present uniform methods for testing insulation with direct voltages. It applies to AC electric machines. It covers acceptance testing of new equipment in the factory or in the field after erection and routine maintenance testing of machines that have been in service.<br />\n
          The purpose of this project is to bring IEEE Std 95 up to the state of the art since it has been in use for more than five years.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Insulation Testing of AC Electric Machinery (2300 V and Above) With High Direct Voltage"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95458 …}
    #channels: Doctrine\ORM\PersistentCollection {#95464 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95460 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95462 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95450 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95444
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1684274400 {#95445
      date: 2023-05-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1018562400 {#95446
      date: 2002-04-12 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1346277600 {#95447
      date: 2012-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#95448
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "95"
    -bookCollection: ""
    -pageCount: 56
    -documents: Doctrine\ORM\PersistentCollection {#95452 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95454 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95481
    #id: 9955
    #code: "IEEE00003336"
    #attributes: Doctrine\ORM\PersistentCollection {#95498 …}
    #variants: Doctrine\ORM\PersistentCollection {#95500 …}
    #options: Doctrine\ORM\PersistentCollection {#95504 …}
    #associations: Doctrine\ORM\PersistentCollection {#95502 …}
    #createdAt: DateTime @1751038698 {#95474
      date: 2025-06-27 17:38:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95475
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95488 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96202
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95481}
        #id: 34829
        #name: "IEEE C62.21:2003 (R2009)"
        #slug: "ieee-c62-21-2003-r2009-ieee00003336-241607"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Project scope: This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors. Project purpose: This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.<br />\n
          \t\t\t\t<br />\n
          This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors.<br />\n
          This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Application of Surge Voltage Protective Equipment on AC Rotating Machinery 1000 Volts and Greater"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95490 …}
    #channels: Doctrine\ORM\PersistentCollection {#95496 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95492 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95494 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95482 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95476
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1622671200 {#95477
      date: 2021-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1083103200 {#95478
      date: 2004-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1237417200 {#95479
      date: 2009-03-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#95480
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C62.21"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95484 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95486 …}
  }
  "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 {#96180
  +product: App\Entity\Product\Product {#95481
    #id: 9955
    #code: "IEEE00003336"
    #attributes: Doctrine\ORM\PersistentCollection {#95498 …}
    #variants: Doctrine\ORM\PersistentCollection {#95500 …}
    #options: Doctrine\ORM\PersistentCollection {#95504 …}
    #associations: Doctrine\ORM\PersistentCollection {#95502 …}
    #createdAt: DateTime @1751038698 {#95474
      date: 2025-06-27 17:38:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95475
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95488 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96202
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95481}
        #id: 34829
        #name: "IEEE C62.21:2003 (R2009)"
        #slug: "ieee-c62-21-2003-r2009-ieee00003336-241607"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Project scope: This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors. Project purpose: This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.<br />\n
          \t\t\t\t<br />\n
          This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors.<br />\n
          This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Application of Surge Voltage Protective Equipment on AC Rotating Machinery 1000 Volts and Greater"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95490 …}
    #channels: Doctrine\ORM\PersistentCollection {#95496 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95492 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95494 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95482 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95476
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1622671200 {#95477
      date: 2021-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1083103200 {#95478
      date: 2004-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1237417200 {#95479
      date: 2009-03-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#95480
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C62.21"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95484 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95486 …}
  }
  +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 {#95481
    #id: 9955
    #code: "IEEE00003336"
    #attributes: Doctrine\ORM\PersistentCollection {#95498 …}
    #variants: Doctrine\ORM\PersistentCollection {#95500 …}
    #options: Doctrine\ORM\PersistentCollection {#95504 …}
    #associations: Doctrine\ORM\PersistentCollection {#95502 …}
    #createdAt: DateTime @1751038698 {#95474
      date: 2025-06-27 17:38:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95475
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95488 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96202
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95481}
        #id: 34829
        #name: "IEEE C62.21:2003 (R2009)"
        #slug: "ieee-c62-21-2003-r2009-ieee00003336-241607"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Project scope: This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors. Project purpose: This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.<br />\n
          \t\t\t\t<br />\n
          This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors.<br />\n
          This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Application of Surge Voltage Protective Equipment on AC Rotating Machinery 1000 Volts and Greater"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95490 …}
    #channels: Doctrine\ORM\PersistentCollection {#95496 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95492 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95494 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95482 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95476
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1622671200 {#95477
      date: 2021-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1083103200 {#95478
      date: 2004-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1237417200 {#95479
      date: 2009-03-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#95480
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C62.21"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95484 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95486 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96216
  +product: App\Entity\Product\Product {#95481
    #id: 9955
    #code: "IEEE00003336"
    #attributes: Doctrine\ORM\PersistentCollection {#95498 …}
    #variants: Doctrine\ORM\PersistentCollection {#95500 …}
    #options: Doctrine\ORM\PersistentCollection {#95504 …}
    #associations: Doctrine\ORM\PersistentCollection {#95502 …}
    #createdAt: DateTime @1751038698 {#95474
      date: 2025-06-27 17:38:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95475
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95488 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96202
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95481}
        #id: 34829
        #name: "IEEE C62.21:2003 (R2009)"
        #slug: "ieee-c62-21-2003-r2009-ieee00003336-241607"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Project scope: This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors. Project purpose: This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.<br />\n
          \t\t\t\t<br />\n
          This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors.<br />\n
          This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Application of Surge Voltage Protective Equipment on AC Rotating Machinery 1000 Volts and Greater"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95490 …}
    #channels: Doctrine\ORM\PersistentCollection {#95496 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95492 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95494 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95482 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95476
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1622671200 {#95477
      date: 2021-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1083103200 {#95478
      date: 2004-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1237417200 {#95479
      date: 2009-03-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#95480
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C62.21"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95484 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95486 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95481
    #id: 9955
    #code: "IEEE00003336"
    #attributes: Doctrine\ORM\PersistentCollection {#95498 …}
    #variants: Doctrine\ORM\PersistentCollection {#95500 …}
    #options: Doctrine\ORM\PersistentCollection {#95504 …}
    #associations: Doctrine\ORM\PersistentCollection {#95502 …}
    #createdAt: DateTime @1751038698 {#95474
      date: 2025-06-27 17:38:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95475
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95488 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96202
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95481}
        #id: 34829
        #name: "IEEE C62.21:2003 (R2009)"
        #slug: "ieee-c62-21-2003-r2009-ieee00003336-241607"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Project scope: This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors. Project purpose: This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.<br />\n
          \t\t\t\t<br />\n
          This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors.<br />\n
          This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Application of Surge Voltage Protective Equipment on AC Rotating Machinery 1000 Volts and Greater"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95490 …}
    #channels: Doctrine\ORM\PersistentCollection {#95496 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95492 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95494 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95482 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95476
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1622671200 {#95477
      date: 2021-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1083103200 {#95478
      date: 2004-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1237417200 {#95479
      date: 2009-03-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#95480
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C62.21"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95484 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95486 …}
  }
]

App\Twig\Components\ProductMostRecent {#96290
  +product: App\Entity\Product\Product {#95481
    #id: 9955
    #code: "IEEE00003336"
    #attributes: Doctrine\ORM\PersistentCollection {#95498 …}
    #variants: Doctrine\ORM\PersistentCollection {#95500 …}
    #options: Doctrine\ORM\PersistentCollection {#95504 …}
    #associations: Doctrine\ORM\PersistentCollection {#95502 …}
    #createdAt: DateTime @1751038698 {#95474
      date: 2025-06-27 17:38:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#95475
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95488 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96202
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95481}
        #id: 34829
        #name: "IEEE C62.21:2003 (R2009)"
        #slug: "ieee-c62-21-2003-r2009-ieee00003336-241607"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Project scope: This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors. Project purpose: This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.<br />\n
          \t\t\t\t<br />\n
          This guide covers the application of surge voltage protective equipment to AC rotating machines rated 1000 volts and greater. The guide does not cover motors applied in solid-state switched adjustable speed drives. Part 1 covers the insulation surge withstand strength of motors and generators with windings having form-wound multi-turn coils and the application of surge protection to form-wound multi-turn coil motors. Part 2 will cover application of surge protection to generators with form-wound multi-turn coils, plus insulation surge withstand strength and surge protection of single-turn coil generators and motors.<br />\n
          This guide is intended to aid engineers at all levels of surge protection knowledge in deciding whether particular machines should have surge protection. The guide may be used in estimating the surge withstand capability and switching surge exposure of ac rotating machinery in usual, not extreme exposure, installations. The manufacturer should be contacted for specific insulation surge voltage withstand values for machinery of particular interest or importance. For those machines which should be protected, the purpose is to provide guidance in selecting and applying the protective devices. A simple look-up method using tables and a graph is provided for quick estimation of surge rise times and surge voltage levels, and for general use where accuracies in the order of 10% to 15% are acceptable. This method is based on single-phase analysis, neglecting the influence of ground mode surge propagation. A more complex method is provided by formulas to model the three-phase and ground mode propagation. The formulas can be used with calculators or personal computers.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for the Application of Surge Voltage Protective Equipment on AC Rotating Machinery 1000 Volts and Greater"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95490 …}
    #channels: Doctrine\ORM\PersistentCollection {#95496 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95492 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95494 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95482 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95476
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1622671200 {#95477
      date: 2021-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1083103200 {#95478
      date: 2004-04-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1237417200 {#95479
      date: 2009-03-19 00:00:00.0 Europe/Paris (+01:00)
    }
    -canceledAt: DateTime @1616626800 {#95480
      date: 2021-03-25 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C62.21"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#95484 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95486 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95512
    #id: 10344
    #code: "IEEE00004206"
    #attributes: Doctrine\ORM\PersistentCollection {#95529 …}
    #variants: Doctrine\ORM\PersistentCollection {#95531 …}
    #options: Doctrine\ORM\PersistentCollection {#95535 …}
    #associations: Doctrine\ORM\PersistentCollection {#95533 …}
    #createdAt: DateTime @1751039003 {#95506
      date: 2025-06-27 17:43:23.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95507
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95519 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96440
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95512}
        #id: 36385
        #name: "IEEE 11073-00101:2008"
        #slug: "ieee-11073-00101-2008-ieee00004206-241996"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          &quot;The following Guidance document addresses the use of radio frequency 1 (RF) wireless technology for the transport of medical data both to and from point-of-care (PoC) medical devices. The context of such wireless medical data transport can range from home- or mobile-based healthcare to in hospital ambulatory and stationary situations. The intent of the guidance document is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the US. At the time of this Guidance document several applicable RF wireless technologies exist with a range of capabilities and characteristics, and in different stages of maturity, standardization, and adoption in healthcare. It is recognized that RF technologies are rapidly evolving, and new options may become available (or sufficiently established) after the publication of this Guidance document. The recommendations, therefore, avoid being overly prescriptive and instead attempt to assist medical device manufacturers, wireless equipment manufacturers, healthcare providers, government agencies and any other end-user of this document to make reasonable judgments regarding performance and practical implementation of wireless solutions. The Guidance document defines specific use cases to estimate, compare, and contrast performance of known technologies operating on wireless personal area (WPAN), wireless local area (WLAN), wireless metropolitan area (WMAN), and wireless wide area (WWAN) networks. Major considerations are 1) the quality-of-service (QoS) requirements (reliability, latency, priority, bandwidth) associated with the data being transported, 2) the expected performance (power, link range, throughput, link establishment and maintenance) of the wireless technology, and 3) the specific needs and resources of the end user. Related issues include network architecture, EMI/EMC, coexistence with other data streams, security, cost, power consumption, and technology configurability. Performance summaries for specific wireless technologies that support defined use cases are not intended as an endorsement of optimal solution because different needs, resources, sizes, and environments cannot be comprehensively addressed. This overview document is meant to be a foundation and reference for several follow-on IEEE 11073.3.5.x standards that will profile specific classes of off-the-shelf RF wireless technologies for medical data transport. Importantly, this guidance document is not envisioned to be periodically updated, but instead will act as a source of information for the follow-on IEEE 11073-0305.x standards that will supplant it. Periodic updates will be performed on the IEEE 11073- 0305.x standards only.&quot;<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for using radio frequency (RF) wireless communication technologies for ISO/IEEE 11073 point-of-care (PoC) medical devices that exchange vital signs and other medical device information using shared information technology (IT) infrastructure. Use cases specific to these technologies are evaluated, and key functional and performance criteria are identified, including quality of service (QoS) management, privacy and security, coexistence with other RF wireless technologies, environmental requirements such as electromagnetic interference and compatibility (EMI/EMC), and power management. Guidelines are provided for each of these areas. Technologies include, but are not limited to, the IEEE 802.11 and IEEE 802.15™ technologies. Use case environments include traditional clinical settings as well as personal (home and mobile) healthcare. The intent of guide is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the United States. Importantly, this guide will not be periodically updated, but instead will act as a source of information for follow-on ISO/IEEE 11073 RF wireless transport standards that will supersede it. These ISO/IEEE 11073 RF wireless transport standards will detail the use of specific wireless networked technology for the purpose of transporting medical data. Periodic updates will be performed on the ISO/IEEE 11073 standards only.<br />\n
          In recent years there has been rapid growth of RF technology to support wireless communication and data transport, as evidenced by the growing use of personal communication devices (e.g., mobile phones, WiFi enabled laptop computers). The incorporation of RF technology into PoC medical devices for wireless data transport has the potential to offer significant benefits to healthcare, although there are many issues that need to be understood and managed in order to ensure data transfer to computer servers, healthcare professionals, terminal data collection units, or other medical devices is accurate, efficient and reliable. Specific recommendations are aimed at different stakeholder groups that make up the audience for this guidance document including healthcare providers, medical device manufacturers / vendors, wireless equipment manufacturers / vendors, and relevant agency groups. The different functionality and operating environment of medical devices is addressed, ranging from core hospital equipment providing complex waveform and other physiological data to single parameter, low data rate sensors worn in a mobile health scenario. Further, patients, healthcare workers, medical equipment, and medical data move across different areas of the healthcare topology and necessitate that data track in a seamless and managed manner. Quality of Service (QoS) requirements (e.g., priority, throughput, latency) can vary significantly across different medical data types (e.g., alarms, real time wave forms, chart data, asset tracking, e-prescriptions), and simultaneous transport of different data types on a shared IT infrastructure are considered for the design of appropriate solutions. Other issues associated with operation on standardized &quot;open&quot; networks are security and privacy.<br />\n
          Coexistence becomes a significant issue as a growing number of medical devices from multiple manufacturers, perhaps using multiple technologies (e.g., IEEE 802.15.1(tm) with IEEE 802.11b(tm)), start to crowd the RF spectrum and compete for bandwidth and channel access. Other issues considered include EMI/EMC, cost, power consumption, and technology configurability. Several factors influence the performance of the wireless system itself, including whether it operates on a shared IT network (e.g., WLAN, WWAN) or simply maintains a point-to-point connection. The former example is especially important when considering the operation of multiple medical devices from different manufacturers, each with different QoS requirements.<br />\n
          An overall effort to promote plug-and-play (PnP) operability between commercially available medical devices and wireless systems (i.e., IEEE, ISO, ANSI, ITU-R, ITU-T), is supported in this guidance document, as well as in follow-on IEEE 11073 profile standards. As private homes are increasingly outfitted with wireless networks, and home- and mobile- management of healthcare and chronic conditions becomes increasingly common, additional issues may emerge.<br />\n
          Recommendations provided in this document are not prescriptive, but instead offer general guidance aimed at the different stakeholders to facilitate design and management of wireless medical data transport to support the necessary QoS and performance requirements as well as co-exist in a complex environment with other wireless traffic. Likewise, exercises and comparisons included in this document are not intended to endorse any particular medical device, wireless technology, or data exchange format, but to offer examples for reference and comparison. Ultimate solutions will vary greatly depend greatly on healthcare needs, resources, sizes, and environments.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Health informatics--PoC medical device communication Part 00101: Guide--Guidelines for the use of RF wireless technology"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95521 …}
    #channels: Doctrine\ORM\PersistentCollection {#95527 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95523 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95525 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95513 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95508
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#95509
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1230246000 {#95510
      date: 2008-12-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#95511
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-00101"
    -bookCollection: ""
    -pageCount: 125
    -documents: Doctrine\ORM\PersistentCollection {#95515 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95517 …}
  }
  "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 {#96420
  +product: App\Entity\Product\Product {#95512
    #id: 10344
    #code: "IEEE00004206"
    #attributes: Doctrine\ORM\PersistentCollection {#95529 …}
    #variants: Doctrine\ORM\PersistentCollection {#95531 …}
    #options: Doctrine\ORM\PersistentCollection {#95535 …}
    #associations: Doctrine\ORM\PersistentCollection {#95533 …}
    #createdAt: DateTime @1751039003 {#95506
      date: 2025-06-27 17:43:23.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95507
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95519 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96440
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95512}
        #id: 36385
        #name: "IEEE 11073-00101:2008"
        #slug: "ieee-11073-00101-2008-ieee00004206-241996"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          &quot;The following Guidance document addresses the use of radio frequency 1 (RF) wireless technology for the transport of medical data both to and from point-of-care (PoC) medical devices. The context of such wireless medical data transport can range from home- or mobile-based healthcare to in hospital ambulatory and stationary situations. The intent of the guidance document is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the US. At the time of this Guidance document several applicable RF wireless technologies exist with a range of capabilities and characteristics, and in different stages of maturity, standardization, and adoption in healthcare. It is recognized that RF technologies are rapidly evolving, and new options may become available (or sufficiently established) after the publication of this Guidance document. The recommendations, therefore, avoid being overly prescriptive and instead attempt to assist medical device manufacturers, wireless equipment manufacturers, healthcare providers, government agencies and any other end-user of this document to make reasonable judgments regarding performance and practical implementation of wireless solutions. The Guidance document defines specific use cases to estimate, compare, and contrast performance of known technologies operating on wireless personal area (WPAN), wireless local area (WLAN), wireless metropolitan area (WMAN), and wireless wide area (WWAN) networks. Major considerations are 1) the quality-of-service (QoS) requirements (reliability, latency, priority, bandwidth) associated with the data being transported, 2) the expected performance (power, link range, throughput, link establishment and maintenance) of the wireless technology, and 3) the specific needs and resources of the end user. Related issues include network architecture, EMI/EMC, coexistence with other data streams, security, cost, power consumption, and technology configurability. Performance summaries for specific wireless technologies that support defined use cases are not intended as an endorsement of optimal solution because different needs, resources, sizes, and environments cannot be comprehensively addressed. This overview document is meant to be a foundation and reference for several follow-on IEEE 11073.3.5.x standards that will profile specific classes of off-the-shelf RF wireless technologies for medical data transport. Importantly, this guidance document is not envisioned to be periodically updated, but instead will act as a source of information for the follow-on IEEE 11073-0305.x standards that will supplant it. Periodic updates will be performed on the IEEE 11073- 0305.x standards only.&quot;<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for using radio frequency (RF) wireless communication technologies for ISO/IEEE 11073 point-of-care (PoC) medical devices that exchange vital signs and other medical device information using shared information technology (IT) infrastructure. Use cases specific to these technologies are evaluated, and key functional and performance criteria are identified, including quality of service (QoS) management, privacy and security, coexistence with other RF wireless technologies, environmental requirements such as electromagnetic interference and compatibility (EMI/EMC), and power management. Guidelines are provided for each of these areas. Technologies include, but are not limited to, the IEEE 802.11 and IEEE 802.15™ technologies. Use case environments include traditional clinical settings as well as personal (home and mobile) healthcare. The intent of guide is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the United States. Importantly, this guide will not be periodically updated, but instead will act as a source of information for follow-on ISO/IEEE 11073 RF wireless transport standards that will supersede it. These ISO/IEEE 11073 RF wireless transport standards will detail the use of specific wireless networked technology for the purpose of transporting medical data. Periodic updates will be performed on the ISO/IEEE 11073 standards only.<br />\n
          In recent years there has been rapid growth of RF technology to support wireless communication and data transport, as evidenced by the growing use of personal communication devices (e.g., mobile phones, WiFi enabled laptop computers). The incorporation of RF technology into PoC medical devices for wireless data transport has the potential to offer significant benefits to healthcare, although there are many issues that need to be understood and managed in order to ensure data transfer to computer servers, healthcare professionals, terminal data collection units, or other medical devices is accurate, efficient and reliable. Specific recommendations are aimed at different stakeholder groups that make up the audience for this guidance document including healthcare providers, medical device manufacturers / vendors, wireless equipment manufacturers / vendors, and relevant agency groups. The different functionality and operating environment of medical devices is addressed, ranging from core hospital equipment providing complex waveform and other physiological data to single parameter, low data rate sensors worn in a mobile health scenario. Further, patients, healthcare workers, medical equipment, and medical data move across different areas of the healthcare topology and necessitate that data track in a seamless and managed manner. Quality of Service (QoS) requirements (e.g., priority, throughput, latency) can vary significantly across different medical data types (e.g., alarms, real time wave forms, chart data, asset tracking, e-prescriptions), and simultaneous transport of different data types on a shared IT infrastructure are considered for the design of appropriate solutions. Other issues associated with operation on standardized &quot;open&quot; networks are security and privacy.<br />\n
          Coexistence becomes a significant issue as a growing number of medical devices from multiple manufacturers, perhaps using multiple technologies (e.g., IEEE 802.15.1(tm) with IEEE 802.11b(tm)), start to crowd the RF spectrum and compete for bandwidth and channel access. Other issues considered include EMI/EMC, cost, power consumption, and technology configurability. Several factors influence the performance of the wireless system itself, including whether it operates on a shared IT network (e.g., WLAN, WWAN) or simply maintains a point-to-point connection. The former example is especially important when considering the operation of multiple medical devices from different manufacturers, each with different QoS requirements.<br />\n
          An overall effort to promote plug-and-play (PnP) operability between commercially available medical devices and wireless systems (i.e., IEEE, ISO, ANSI, ITU-R, ITU-T), is supported in this guidance document, as well as in follow-on IEEE 11073 profile standards. As private homes are increasingly outfitted with wireless networks, and home- and mobile- management of healthcare and chronic conditions becomes increasingly common, additional issues may emerge.<br />\n
          Recommendations provided in this document are not prescriptive, but instead offer general guidance aimed at the different stakeholders to facilitate design and management of wireless medical data transport to support the necessary QoS and performance requirements as well as co-exist in a complex environment with other wireless traffic. Likewise, exercises and comparisons included in this document are not intended to endorse any particular medical device, wireless technology, or data exchange format, but to offer examples for reference and comparison. Ultimate solutions will vary greatly depend greatly on healthcare needs, resources, sizes, and environments.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Health informatics--PoC medical device communication Part 00101: Guide--Guidelines for the use of RF wireless technology"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95521 …}
    #channels: Doctrine\ORM\PersistentCollection {#95527 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95523 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95525 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95513 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95508
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#95509
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1230246000 {#95510
      date: 2008-12-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#95511
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-00101"
    -bookCollection: ""
    -pageCount: 125
    -documents: Doctrine\ORM\PersistentCollection {#95515 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95517 …}
  }
  +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 {#95512
    #id: 10344
    #code: "IEEE00004206"
    #attributes: Doctrine\ORM\PersistentCollection {#95529 …}
    #variants: Doctrine\ORM\PersistentCollection {#95531 …}
    #options: Doctrine\ORM\PersistentCollection {#95535 …}
    #associations: Doctrine\ORM\PersistentCollection {#95533 …}
    #createdAt: DateTime @1751039003 {#95506
      date: 2025-06-27 17:43:23.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95507
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95519 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96440
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95512}
        #id: 36385
        #name: "IEEE 11073-00101:2008"
        #slug: "ieee-11073-00101-2008-ieee00004206-241996"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          &quot;The following Guidance document addresses the use of radio frequency 1 (RF) wireless technology for the transport of medical data both to and from point-of-care (PoC) medical devices. The context of such wireless medical data transport can range from home- or mobile-based healthcare to in hospital ambulatory and stationary situations. The intent of the guidance document is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the US. At the time of this Guidance document several applicable RF wireless technologies exist with a range of capabilities and characteristics, and in different stages of maturity, standardization, and adoption in healthcare. It is recognized that RF technologies are rapidly evolving, and new options may become available (or sufficiently established) after the publication of this Guidance document. The recommendations, therefore, avoid being overly prescriptive and instead attempt to assist medical device manufacturers, wireless equipment manufacturers, healthcare providers, government agencies and any other end-user of this document to make reasonable judgments regarding performance and practical implementation of wireless solutions. The Guidance document defines specific use cases to estimate, compare, and contrast performance of known technologies operating on wireless personal area (WPAN), wireless local area (WLAN), wireless metropolitan area (WMAN), and wireless wide area (WWAN) networks. Major considerations are 1) the quality-of-service (QoS) requirements (reliability, latency, priority, bandwidth) associated with the data being transported, 2) the expected performance (power, link range, throughput, link establishment and maintenance) of the wireless technology, and 3) the specific needs and resources of the end user. Related issues include network architecture, EMI/EMC, coexistence with other data streams, security, cost, power consumption, and technology configurability. Performance summaries for specific wireless technologies that support defined use cases are not intended as an endorsement of optimal solution because different needs, resources, sizes, and environments cannot be comprehensively addressed. This overview document is meant to be a foundation and reference for several follow-on IEEE 11073.3.5.x standards that will profile specific classes of off-the-shelf RF wireless technologies for medical data transport. Importantly, this guidance document is not envisioned to be periodically updated, but instead will act as a source of information for the follow-on IEEE 11073-0305.x standards that will supplant it. Periodic updates will be performed on the IEEE 11073- 0305.x standards only.&quot;<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for using radio frequency (RF) wireless communication technologies for ISO/IEEE 11073 point-of-care (PoC) medical devices that exchange vital signs and other medical device information using shared information technology (IT) infrastructure. Use cases specific to these technologies are evaluated, and key functional and performance criteria are identified, including quality of service (QoS) management, privacy and security, coexistence with other RF wireless technologies, environmental requirements such as electromagnetic interference and compatibility (EMI/EMC), and power management. Guidelines are provided for each of these areas. Technologies include, but are not limited to, the IEEE 802.11 and IEEE 802.15™ technologies. Use case environments include traditional clinical settings as well as personal (home and mobile) healthcare. The intent of guide is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the United States. Importantly, this guide will not be periodically updated, but instead will act as a source of information for follow-on ISO/IEEE 11073 RF wireless transport standards that will supersede it. These ISO/IEEE 11073 RF wireless transport standards will detail the use of specific wireless networked technology for the purpose of transporting medical data. Periodic updates will be performed on the ISO/IEEE 11073 standards only.<br />\n
          In recent years there has been rapid growth of RF technology to support wireless communication and data transport, as evidenced by the growing use of personal communication devices (e.g., mobile phones, WiFi enabled laptop computers). The incorporation of RF technology into PoC medical devices for wireless data transport has the potential to offer significant benefits to healthcare, although there are many issues that need to be understood and managed in order to ensure data transfer to computer servers, healthcare professionals, terminal data collection units, or other medical devices is accurate, efficient and reliable. Specific recommendations are aimed at different stakeholder groups that make up the audience for this guidance document including healthcare providers, medical device manufacturers / vendors, wireless equipment manufacturers / vendors, and relevant agency groups. The different functionality and operating environment of medical devices is addressed, ranging from core hospital equipment providing complex waveform and other physiological data to single parameter, low data rate sensors worn in a mobile health scenario. Further, patients, healthcare workers, medical equipment, and medical data move across different areas of the healthcare topology and necessitate that data track in a seamless and managed manner. Quality of Service (QoS) requirements (e.g., priority, throughput, latency) can vary significantly across different medical data types (e.g., alarms, real time wave forms, chart data, asset tracking, e-prescriptions), and simultaneous transport of different data types on a shared IT infrastructure are considered for the design of appropriate solutions. Other issues associated with operation on standardized &quot;open&quot; networks are security and privacy.<br />\n
          Coexistence becomes a significant issue as a growing number of medical devices from multiple manufacturers, perhaps using multiple technologies (e.g., IEEE 802.15.1(tm) with IEEE 802.11b(tm)), start to crowd the RF spectrum and compete for bandwidth and channel access. Other issues considered include EMI/EMC, cost, power consumption, and technology configurability. Several factors influence the performance of the wireless system itself, including whether it operates on a shared IT network (e.g., WLAN, WWAN) or simply maintains a point-to-point connection. The former example is especially important when considering the operation of multiple medical devices from different manufacturers, each with different QoS requirements.<br />\n
          An overall effort to promote plug-and-play (PnP) operability between commercially available medical devices and wireless systems (i.e., IEEE, ISO, ANSI, ITU-R, ITU-T), is supported in this guidance document, as well as in follow-on IEEE 11073 profile standards. As private homes are increasingly outfitted with wireless networks, and home- and mobile- management of healthcare and chronic conditions becomes increasingly common, additional issues may emerge.<br />\n
          Recommendations provided in this document are not prescriptive, but instead offer general guidance aimed at the different stakeholders to facilitate design and management of wireless medical data transport to support the necessary QoS and performance requirements as well as co-exist in a complex environment with other wireless traffic. Likewise, exercises and comparisons included in this document are not intended to endorse any particular medical device, wireless technology, or data exchange format, but to offer examples for reference and comparison. Ultimate solutions will vary greatly depend greatly on healthcare needs, resources, sizes, and environments.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Health informatics--PoC medical device communication Part 00101: Guide--Guidelines for the use of RF wireless technology"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95521 …}
    #channels: Doctrine\ORM\PersistentCollection {#95527 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95523 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95525 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95513 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95508
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#95509
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1230246000 {#95510
      date: 2008-12-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#95511
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-00101"
    -bookCollection: ""
    -pageCount: 125
    -documents: Doctrine\ORM\PersistentCollection {#95515 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95517 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96454
  +product: App\Entity\Product\Product {#95512
    #id: 10344
    #code: "IEEE00004206"
    #attributes: Doctrine\ORM\PersistentCollection {#95529 …}
    #variants: Doctrine\ORM\PersistentCollection {#95531 …}
    #options: Doctrine\ORM\PersistentCollection {#95535 …}
    #associations: Doctrine\ORM\PersistentCollection {#95533 …}
    #createdAt: DateTime @1751039003 {#95506
      date: 2025-06-27 17:43:23.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95507
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95519 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96440
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95512}
        #id: 36385
        #name: "IEEE 11073-00101:2008"
        #slug: "ieee-11073-00101-2008-ieee00004206-241996"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          &quot;The following Guidance document addresses the use of radio frequency 1 (RF) wireless technology for the transport of medical data both to and from point-of-care (PoC) medical devices. The context of such wireless medical data transport can range from home- or mobile-based healthcare to in hospital ambulatory and stationary situations. The intent of the guidance document is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the US. At the time of this Guidance document several applicable RF wireless technologies exist with a range of capabilities and characteristics, and in different stages of maturity, standardization, and adoption in healthcare. It is recognized that RF technologies are rapidly evolving, and new options may become available (or sufficiently established) after the publication of this Guidance document. The recommendations, therefore, avoid being overly prescriptive and instead attempt to assist medical device manufacturers, wireless equipment manufacturers, healthcare providers, government agencies and any other end-user of this document to make reasonable judgments regarding performance and practical implementation of wireless solutions. The Guidance document defines specific use cases to estimate, compare, and contrast performance of known technologies operating on wireless personal area (WPAN), wireless local area (WLAN), wireless metropolitan area (WMAN), and wireless wide area (WWAN) networks. Major considerations are 1) the quality-of-service (QoS) requirements (reliability, latency, priority, bandwidth) associated with the data being transported, 2) the expected performance (power, link range, throughput, link establishment and maintenance) of the wireless technology, and 3) the specific needs and resources of the end user. Related issues include network architecture, EMI/EMC, coexistence with other data streams, security, cost, power consumption, and technology configurability. Performance summaries for specific wireless technologies that support defined use cases are not intended as an endorsement of optimal solution because different needs, resources, sizes, and environments cannot be comprehensively addressed. This overview document is meant to be a foundation and reference for several follow-on IEEE 11073.3.5.x standards that will profile specific classes of off-the-shelf RF wireless technologies for medical data transport. Importantly, this guidance document is not envisioned to be periodically updated, but instead will act as a source of information for the follow-on IEEE 11073-0305.x standards that will supplant it. Periodic updates will be performed on the IEEE 11073- 0305.x standards only.&quot;<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for using radio frequency (RF) wireless communication technologies for ISO/IEEE 11073 point-of-care (PoC) medical devices that exchange vital signs and other medical device information using shared information technology (IT) infrastructure. Use cases specific to these technologies are evaluated, and key functional and performance criteria are identified, including quality of service (QoS) management, privacy and security, coexistence with other RF wireless technologies, environmental requirements such as electromagnetic interference and compatibility (EMI/EMC), and power management. Guidelines are provided for each of these areas. Technologies include, but are not limited to, the IEEE 802.11 and IEEE 802.15™ technologies. Use case environments include traditional clinical settings as well as personal (home and mobile) healthcare. The intent of guide is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the United States. Importantly, this guide will not be periodically updated, but instead will act as a source of information for follow-on ISO/IEEE 11073 RF wireless transport standards that will supersede it. These ISO/IEEE 11073 RF wireless transport standards will detail the use of specific wireless networked technology for the purpose of transporting medical data. Periodic updates will be performed on the ISO/IEEE 11073 standards only.<br />\n
          In recent years there has been rapid growth of RF technology to support wireless communication and data transport, as evidenced by the growing use of personal communication devices (e.g., mobile phones, WiFi enabled laptop computers). The incorporation of RF technology into PoC medical devices for wireless data transport has the potential to offer significant benefits to healthcare, although there are many issues that need to be understood and managed in order to ensure data transfer to computer servers, healthcare professionals, terminal data collection units, or other medical devices is accurate, efficient and reliable. Specific recommendations are aimed at different stakeholder groups that make up the audience for this guidance document including healthcare providers, medical device manufacturers / vendors, wireless equipment manufacturers / vendors, and relevant agency groups. The different functionality and operating environment of medical devices is addressed, ranging from core hospital equipment providing complex waveform and other physiological data to single parameter, low data rate sensors worn in a mobile health scenario. Further, patients, healthcare workers, medical equipment, and medical data move across different areas of the healthcare topology and necessitate that data track in a seamless and managed manner. Quality of Service (QoS) requirements (e.g., priority, throughput, latency) can vary significantly across different medical data types (e.g., alarms, real time wave forms, chart data, asset tracking, e-prescriptions), and simultaneous transport of different data types on a shared IT infrastructure are considered for the design of appropriate solutions. Other issues associated with operation on standardized &quot;open&quot; networks are security and privacy.<br />\n
          Coexistence becomes a significant issue as a growing number of medical devices from multiple manufacturers, perhaps using multiple technologies (e.g., IEEE 802.15.1(tm) with IEEE 802.11b(tm)), start to crowd the RF spectrum and compete for bandwidth and channel access. Other issues considered include EMI/EMC, cost, power consumption, and technology configurability. Several factors influence the performance of the wireless system itself, including whether it operates on a shared IT network (e.g., WLAN, WWAN) or simply maintains a point-to-point connection. The former example is especially important when considering the operation of multiple medical devices from different manufacturers, each with different QoS requirements.<br />\n
          An overall effort to promote plug-and-play (PnP) operability between commercially available medical devices and wireless systems (i.e., IEEE, ISO, ANSI, ITU-R, ITU-T), is supported in this guidance document, as well as in follow-on IEEE 11073 profile standards. As private homes are increasingly outfitted with wireless networks, and home- and mobile- management of healthcare and chronic conditions becomes increasingly common, additional issues may emerge.<br />\n
          Recommendations provided in this document are not prescriptive, but instead offer general guidance aimed at the different stakeholders to facilitate design and management of wireless medical data transport to support the necessary QoS and performance requirements as well as co-exist in a complex environment with other wireless traffic. Likewise, exercises and comparisons included in this document are not intended to endorse any particular medical device, wireless technology, or data exchange format, but to offer examples for reference and comparison. Ultimate solutions will vary greatly depend greatly on healthcare needs, resources, sizes, and environments.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Health informatics--PoC medical device communication Part 00101: Guide--Guidelines for the use of RF wireless technology"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95521 …}
    #channels: Doctrine\ORM\PersistentCollection {#95527 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95523 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95525 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95513 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95508
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#95509
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1230246000 {#95510
      date: 2008-12-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#95511
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-00101"
    -bookCollection: ""
    -pageCount: 125
    -documents: Doctrine\ORM\PersistentCollection {#95515 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95517 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95512
    #id: 10344
    #code: "IEEE00004206"
    #attributes: Doctrine\ORM\PersistentCollection {#95529 …}
    #variants: Doctrine\ORM\PersistentCollection {#95531 …}
    #options: Doctrine\ORM\PersistentCollection {#95535 …}
    #associations: Doctrine\ORM\PersistentCollection {#95533 …}
    #createdAt: DateTime @1751039003 {#95506
      date: 2025-06-27 17:43:23.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95507
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95519 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96440
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95512}
        #id: 36385
        #name: "IEEE 11073-00101:2008"
        #slug: "ieee-11073-00101-2008-ieee00004206-241996"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          &quot;The following Guidance document addresses the use of radio frequency 1 (RF) wireless technology for the transport of medical data both to and from point-of-care (PoC) medical devices. The context of such wireless medical data transport can range from home- or mobile-based healthcare to in hospital ambulatory and stationary situations. The intent of the guidance document is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the US. At the time of this Guidance document several applicable RF wireless technologies exist with a range of capabilities and characteristics, and in different stages of maturity, standardization, and adoption in healthcare. It is recognized that RF technologies are rapidly evolving, and new options may become available (or sufficiently established) after the publication of this Guidance document. The recommendations, therefore, avoid being overly prescriptive and instead attempt to assist medical device manufacturers, wireless equipment manufacturers, healthcare providers, government agencies and any other end-user of this document to make reasonable judgments regarding performance and practical implementation of wireless solutions. The Guidance document defines specific use cases to estimate, compare, and contrast performance of known technologies operating on wireless personal area (WPAN), wireless local area (WLAN), wireless metropolitan area (WMAN), and wireless wide area (WWAN) networks. Major considerations are 1) the quality-of-service (QoS) requirements (reliability, latency, priority, bandwidth) associated with the data being transported, 2) the expected performance (power, link range, throughput, link establishment and maintenance) of the wireless technology, and 3) the specific needs and resources of the end user. Related issues include network architecture, EMI/EMC, coexistence with other data streams, security, cost, power consumption, and technology configurability. Performance summaries for specific wireless technologies that support defined use cases are not intended as an endorsement of optimal solution because different needs, resources, sizes, and environments cannot be comprehensively addressed. This overview document is meant to be a foundation and reference for several follow-on IEEE 11073.3.5.x standards that will profile specific classes of off-the-shelf RF wireless technologies for medical data transport. Importantly, this guidance document is not envisioned to be periodically updated, but instead will act as a source of information for the follow-on IEEE 11073-0305.x standards that will supplant it. Periodic updates will be performed on the IEEE 11073- 0305.x standards only.&quot;<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for using radio frequency (RF) wireless communication technologies for ISO/IEEE 11073 point-of-care (PoC) medical devices that exchange vital signs and other medical device information using shared information technology (IT) infrastructure. Use cases specific to these technologies are evaluated, and key functional and performance criteria are identified, including quality of service (QoS) management, privacy and security, coexistence with other RF wireless technologies, environmental requirements such as electromagnetic interference and compatibility (EMI/EMC), and power management. Guidelines are provided for each of these areas. Technologies include, but are not limited to, the IEEE 802.11 and IEEE 802.15™ technologies. Use case environments include traditional clinical settings as well as personal (home and mobile) healthcare. The intent of guide is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the United States. Importantly, this guide will not be periodically updated, but instead will act as a source of information for follow-on ISO/IEEE 11073 RF wireless transport standards that will supersede it. These ISO/IEEE 11073 RF wireless transport standards will detail the use of specific wireless networked technology for the purpose of transporting medical data. Periodic updates will be performed on the ISO/IEEE 11073 standards only.<br />\n
          In recent years there has been rapid growth of RF technology to support wireless communication and data transport, as evidenced by the growing use of personal communication devices (e.g., mobile phones, WiFi enabled laptop computers). The incorporation of RF technology into PoC medical devices for wireless data transport has the potential to offer significant benefits to healthcare, although there are many issues that need to be understood and managed in order to ensure data transfer to computer servers, healthcare professionals, terminal data collection units, or other medical devices is accurate, efficient and reliable. Specific recommendations are aimed at different stakeholder groups that make up the audience for this guidance document including healthcare providers, medical device manufacturers / vendors, wireless equipment manufacturers / vendors, and relevant agency groups. The different functionality and operating environment of medical devices is addressed, ranging from core hospital equipment providing complex waveform and other physiological data to single parameter, low data rate sensors worn in a mobile health scenario. Further, patients, healthcare workers, medical equipment, and medical data move across different areas of the healthcare topology and necessitate that data track in a seamless and managed manner. Quality of Service (QoS) requirements (e.g., priority, throughput, latency) can vary significantly across different medical data types (e.g., alarms, real time wave forms, chart data, asset tracking, e-prescriptions), and simultaneous transport of different data types on a shared IT infrastructure are considered for the design of appropriate solutions. Other issues associated with operation on standardized &quot;open&quot; networks are security and privacy.<br />\n
          Coexistence becomes a significant issue as a growing number of medical devices from multiple manufacturers, perhaps using multiple technologies (e.g., IEEE 802.15.1(tm) with IEEE 802.11b(tm)), start to crowd the RF spectrum and compete for bandwidth and channel access. Other issues considered include EMI/EMC, cost, power consumption, and technology configurability. Several factors influence the performance of the wireless system itself, including whether it operates on a shared IT network (e.g., WLAN, WWAN) or simply maintains a point-to-point connection. The former example is especially important when considering the operation of multiple medical devices from different manufacturers, each with different QoS requirements.<br />\n
          An overall effort to promote plug-and-play (PnP) operability between commercially available medical devices and wireless systems (i.e., IEEE, ISO, ANSI, ITU-R, ITU-T), is supported in this guidance document, as well as in follow-on IEEE 11073 profile standards. As private homes are increasingly outfitted with wireless networks, and home- and mobile- management of healthcare and chronic conditions becomes increasingly common, additional issues may emerge.<br />\n
          Recommendations provided in this document are not prescriptive, but instead offer general guidance aimed at the different stakeholders to facilitate design and management of wireless medical data transport to support the necessary QoS and performance requirements as well as co-exist in a complex environment with other wireless traffic. Likewise, exercises and comparisons included in this document are not intended to endorse any particular medical device, wireless technology, or data exchange format, but to offer examples for reference and comparison. Ultimate solutions will vary greatly depend greatly on healthcare needs, resources, sizes, and environments.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Health informatics--PoC medical device communication Part 00101: Guide--Guidelines for the use of RF wireless technology"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95521 …}
    #channels: Doctrine\ORM\PersistentCollection {#95527 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95523 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95525 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95513 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95508
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#95509
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1230246000 {#95510
      date: 2008-12-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#95511
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-00101"
    -bookCollection: ""
    -pageCount: 125
    -documents: Doctrine\ORM\PersistentCollection {#95515 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95517 …}
  }
]

App\Twig\Components\ProductMostRecent {#96528
  +product: App\Entity\Product\Product {#95512
    #id: 10344
    #code: "IEEE00004206"
    #attributes: Doctrine\ORM\PersistentCollection {#95529 …}
    #variants: Doctrine\ORM\PersistentCollection {#95531 …}
    #options: Doctrine\ORM\PersistentCollection {#95535 …}
    #associations: Doctrine\ORM\PersistentCollection {#95533 …}
    #createdAt: DateTime @1751039003 {#95506
      date: 2025-06-27 17:43:23.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95507
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95519 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96440
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95512}
        #id: 36385
        #name: "IEEE 11073-00101:2008"
        #slug: "ieee-11073-00101-2008-ieee00004206-241996"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          &quot;The following Guidance document addresses the use of radio frequency 1 (RF) wireless technology for the transport of medical data both to and from point-of-care (PoC) medical devices. The context of such wireless medical data transport can range from home- or mobile-based healthcare to in hospital ambulatory and stationary situations. The intent of the guidance document is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the US. At the time of this Guidance document several applicable RF wireless technologies exist with a range of capabilities and characteristics, and in different stages of maturity, standardization, and adoption in healthcare. It is recognized that RF technologies are rapidly evolving, and new options may become available (or sufficiently established) after the publication of this Guidance document. The recommendations, therefore, avoid being overly prescriptive and instead attempt to assist medical device manufacturers, wireless equipment manufacturers, healthcare providers, government agencies and any other end-user of this document to make reasonable judgments regarding performance and practical implementation of wireless solutions. The Guidance document defines specific use cases to estimate, compare, and contrast performance of known technologies operating on wireless personal area (WPAN), wireless local area (WLAN), wireless metropolitan area (WMAN), and wireless wide area (WWAN) networks. Major considerations are 1) the quality-of-service (QoS) requirements (reliability, latency, priority, bandwidth) associated with the data being transported, 2) the expected performance (power, link range, throughput, link establishment and maintenance) of the wireless technology, and 3) the specific needs and resources of the end user. Related issues include network architecture, EMI/EMC, coexistence with other data streams, security, cost, power consumption, and technology configurability. Performance summaries for specific wireless technologies that support defined use cases are not intended as an endorsement of optimal solution because different needs, resources, sizes, and environments cannot be comprehensively addressed. This overview document is meant to be a foundation and reference for several follow-on IEEE 11073.3.5.x standards that will profile specific classes of off-the-shelf RF wireless technologies for medical data transport. Importantly, this guidance document is not envisioned to be periodically updated, but instead will act as a source of information for the follow-on IEEE 11073-0305.x standards that will supplant it. Periodic updates will be performed on the IEEE 11073- 0305.x standards only.&quot;<br />\n
          \t\t\t\t<br />\n
          This guide provides guidance for using radio frequency (RF) wireless communication technologies for ISO/IEEE 11073 point-of-care (PoC) medical devices that exchange vital signs and other medical device information using shared information technology (IT) infrastructure. Use cases specific to these technologies are evaluated, and key functional and performance criteria are identified, including quality of service (QoS) management, privacy and security, coexistence with other RF wireless technologies, environmental requirements such as electromagnetic interference and compatibility (EMI/EMC), and power management. Guidelines are provided for each of these areas. Technologies include, but are not limited to, the IEEE 802.11 and IEEE 802.15™ technologies. Use case environments include traditional clinical settings as well as personal (home and mobile) healthcare. The intent of guide is to be global with respect to wireless spectrum and equipment, although working group participation and expertise have favored detail of scenarios from the United States. Importantly, this guide will not be periodically updated, but instead will act as a source of information for follow-on ISO/IEEE 11073 RF wireless transport standards that will supersede it. These ISO/IEEE 11073 RF wireless transport standards will detail the use of specific wireless networked technology for the purpose of transporting medical data. Periodic updates will be performed on the ISO/IEEE 11073 standards only.<br />\n
          In recent years there has been rapid growth of RF technology to support wireless communication and data transport, as evidenced by the growing use of personal communication devices (e.g., mobile phones, WiFi enabled laptop computers). The incorporation of RF technology into PoC medical devices for wireless data transport has the potential to offer significant benefits to healthcare, although there are many issues that need to be understood and managed in order to ensure data transfer to computer servers, healthcare professionals, terminal data collection units, or other medical devices is accurate, efficient and reliable. Specific recommendations are aimed at different stakeholder groups that make up the audience for this guidance document including healthcare providers, medical device manufacturers / vendors, wireless equipment manufacturers / vendors, and relevant agency groups. The different functionality and operating environment of medical devices is addressed, ranging from core hospital equipment providing complex waveform and other physiological data to single parameter, low data rate sensors worn in a mobile health scenario. Further, patients, healthcare workers, medical equipment, and medical data move across different areas of the healthcare topology and necessitate that data track in a seamless and managed manner. Quality of Service (QoS) requirements (e.g., priority, throughput, latency) can vary significantly across different medical data types (e.g., alarms, real time wave forms, chart data, asset tracking, e-prescriptions), and simultaneous transport of different data types on a shared IT infrastructure are considered for the design of appropriate solutions. Other issues associated with operation on standardized &quot;open&quot; networks are security and privacy.<br />\n
          Coexistence becomes a significant issue as a growing number of medical devices from multiple manufacturers, perhaps using multiple technologies (e.g., IEEE 802.15.1(tm) with IEEE 802.11b(tm)), start to crowd the RF spectrum and compete for bandwidth and channel access. Other issues considered include EMI/EMC, cost, power consumption, and technology configurability. Several factors influence the performance of the wireless system itself, including whether it operates on a shared IT network (e.g., WLAN, WWAN) or simply maintains a point-to-point connection. The former example is especially important when considering the operation of multiple medical devices from different manufacturers, each with different QoS requirements.<br />\n
          An overall effort to promote plug-and-play (PnP) operability between commercially available medical devices and wireless systems (i.e., IEEE, ISO, ANSI, ITU-R, ITU-T), is supported in this guidance document, as well as in follow-on IEEE 11073 profile standards. As private homes are increasingly outfitted with wireless networks, and home- and mobile- management of healthcare and chronic conditions becomes increasingly common, additional issues may emerge.<br />\n
          Recommendations provided in this document are not prescriptive, but instead offer general guidance aimed at the different stakeholders to facilitate design and management of wireless medical data transport to support the necessary QoS and performance requirements as well as co-exist in a complex environment with other wireless traffic. Likewise, exercises and comparisons included in this document are not intended to endorse any particular medical device, wireless technology, or data exchange format, but to offer examples for reference and comparison. Ultimate solutions will vary greatly depend greatly on healthcare needs, resources, sizes, and environments.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Health informatics--PoC medical device communication Part 00101: Guide--Guidelines for the use of RF wireless technology"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95521 …}
    #channels: Doctrine\ORM\PersistentCollection {#95527 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95523 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95525 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95513 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95508
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1579820400 {#95509
      date: 2020-01-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1230246000 {#95510
      date: 2008-12-26 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#95511
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-00101"
    -bookCollection: ""
    -pageCount: 125
    -documents: Doctrine\ORM\PersistentCollection {#95515 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95517 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95543
    #id: 11035
    #code: "IEEE00005468"
    #attributes: Doctrine\ORM\PersistentCollection {#95560 …}
    #variants: Doctrine\ORM\PersistentCollection {#95562 …}
    #options: Doctrine\ORM\PersistentCollection {#95566 …}
    #associations: Doctrine\ORM\PersistentCollection {#95564 …}
    #createdAt: DateTime @1751039438 {#95537
      date: 2025-06-27 17:50:38.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95538
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95550 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96670
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95543}
        #id: 39149
        #name: "IEEE 11073-10424:2014"
        #slug: "ieee-11073-10424-2014-ieee00005468-242687"
        #description: """
          New IEEE Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between sleep apnoea breathing therapy equipment (SABTE) devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes), in a manner that enables plug-and-play interoperability, is established in this standard. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for SABTE. In this context, SABTE is defined as a device that is intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. SABTE is primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between sleep apnoea breathing therapy equipment and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for sleep apnoea breathing therapy equipment. In this context, sleep apnoea breathing therapy equipment are defined as devices that are intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. Sleep apnoea breathing therapy equipment are primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, and set top boxes). Interoperability is key to growing the potential market for these devices and to enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Health informatics--Personal health device communication - Part 10424: Device Specialization--Sleep Apnoea Breathing Therapy Equipment (SABTE)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95552 …}
    #channels: Doctrine\ORM\PersistentCollection {#95558 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95554 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95556 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95544 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95539
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95540
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1411941600 {#95541
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1411941600 {#95542
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "11073-10424"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#95546 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95548 …}
  }
  "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 {#96650
  +product: App\Entity\Product\Product {#95543
    #id: 11035
    #code: "IEEE00005468"
    #attributes: Doctrine\ORM\PersistentCollection {#95560 …}
    #variants: Doctrine\ORM\PersistentCollection {#95562 …}
    #options: Doctrine\ORM\PersistentCollection {#95566 …}
    #associations: Doctrine\ORM\PersistentCollection {#95564 …}
    #createdAt: DateTime @1751039438 {#95537
      date: 2025-06-27 17:50:38.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95538
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95550 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96670
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95543}
        #id: 39149
        #name: "IEEE 11073-10424:2014"
        #slug: "ieee-11073-10424-2014-ieee00005468-242687"
        #description: """
          New IEEE Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between sleep apnoea breathing therapy equipment (SABTE) devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes), in a manner that enables plug-and-play interoperability, is established in this standard. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for SABTE. In this context, SABTE is defined as a device that is intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. SABTE is primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between sleep apnoea breathing therapy equipment and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for sleep apnoea breathing therapy equipment. In this context, sleep apnoea breathing therapy equipment are defined as devices that are intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. Sleep apnoea breathing therapy equipment are primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, and set top boxes). Interoperability is key to growing the potential market for these devices and to enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Health informatics--Personal health device communication - Part 10424: Device Specialization--Sleep Apnoea Breathing Therapy Equipment (SABTE)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95552 …}
    #channels: Doctrine\ORM\PersistentCollection {#95558 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95554 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95556 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95544 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95539
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95540
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1411941600 {#95541
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1411941600 {#95542
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "11073-10424"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#95546 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95548 …}
  }
  +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 {#95543
    #id: 11035
    #code: "IEEE00005468"
    #attributes: Doctrine\ORM\PersistentCollection {#95560 …}
    #variants: Doctrine\ORM\PersistentCollection {#95562 …}
    #options: Doctrine\ORM\PersistentCollection {#95566 …}
    #associations: Doctrine\ORM\PersistentCollection {#95564 …}
    #createdAt: DateTime @1751039438 {#95537
      date: 2025-06-27 17:50:38.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95538
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95550 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96670
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95543}
        #id: 39149
        #name: "IEEE 11073-10424:2014"
        #slug: "ieee-11073-10424-2014-ieee00005468-242687"
        #description: """
          New IEEE Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between sleep apnoea breathing therapy equipment (SABTE) devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes), in a manner that enables plug-and-play interoperability, is established in this standard. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for SABTE. In this context, SABTE is defined as a device that is intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. SABTE is primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between sleep apnoea breathing therapy equipment and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for sleep apnoea breathing therapy equipment. In this context, sleep apnoea breathing therapy equipment are defined as devices that are intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. Sleep apnoea breathing therapy equipment are primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, and set top boxes). Interoperability is key to growing the potential market for these devices and to enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Health informatics--Personal health device communication - Part 10424: Device Specialization--Sleep Apnoea Breathing Therapy Equipment (SABTE)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95552 …}
    #channels: Doctrine\ORM\PersistentCollection {#95558 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95554 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95556 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95544 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95539
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95540
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1411941600 {#95541
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1411941600 {#95542
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "11073-10424"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#95546 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95548 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96684
  +product: App\Entity\Product\Product {#95543
    #id: 11035
    #code: "IEEE00005468"
    #attributes: Doctrine\ORM\PersistentCollection {#95560 …}
    #variants: Doctrine\ORM\PersistentCollection {#95562 …}
    #options: Doctrine\ORM\PersistentCollection {#95566 …}
    #associations: Doctrine\ORM\PersistentCollection {#95564 …}
    #createdAt: DateTime @1751039438 {#95537
      date: 2025-06-27 17:50:38.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95538
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95550 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96670
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95543}
        #id: 39149
        #name: "IEEE 11073-10424:2014"
        #slug: "ieee-11073-10424-2014-ieee00005468-242687"
        #description: """
          New IEEE Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between sleep apnoea breathing therapy equipment (SABTE) devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes), in a manner that enables plug-and-play interoperability, is established in this standard. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for SABTE. In this context, SABTE is defined as a device that is intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. SABTE is primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between sleep apnoea breathing therapy equipment and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for sleep apnoea breathing therapy equipment. In this context, sleep apnoea breathing therapy equipment are defined as devices that are intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. Sleep apnoea breathing therapy equipment are primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, and set top boxes). Interoperability is key to growing the potential market for these devices and to enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Health informatics--Personal health device communication - Part 10424: Device Specialization--Sleep Apnoea Breathing Therapy Equipment (SABTE)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95552 …}
    #channels: Doctrine\ORM\PersistentCollection {#95558 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95554 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95556 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95544 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95539
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95540
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1411941600 {#95541
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1411941600 {#95542
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "11073-10424"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#95546 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95548 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95543
    #id: 11035
    #code: "IEEE00005468"
    #attributes: Doctrine\ORM\PersistentCollection {#95560 …}
    #variants: Doctrine\ORM\PersistentCollection {#95562 …}
    #options: Doctrine\ORM\PersistentCollection {#95566 …}
    #associations: Doctrine\ORM\PersistentCollection {#95564 …}
    #createdAt: DateTime @1751039438 {#95537
      date: 2025-06-27 17:50:38.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95538
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95550 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96670
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95543}
        #id: 39149
        #name: "IEEE 11073-10424:2014"
        #slug: "ieee-11073-10424-2014-ieee00005468-242687"
        #description: """
          New IEEE Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between sleep apnoea breathing therapy equipment (SABTE) devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes), in a manner that enables plug-and-play interoperability, is established in this standard. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for SABTE. In this context, SABTE is defined as a device that is intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. SABTE is primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between sleep apnoea breathing therapy equipment and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for sleep apnoea breathing therapy equipment. In this context, sleep apnoea breathing therapy equipment are defined as devices that are intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. Sleep apnoea breathing therapy equipment are primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, and set top boxes). Interoperability is key to growing the potential market for these devices and to enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Health informatics--Personal health device communication - Part 10424: Device Specialization--Sleep Apnoea Breathing Therapy Equipment (SABTE)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95552 …}
    #channels: Doctrine\ORM\PersistentCollection {#95558 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95554 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95556 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95544 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95539
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95540
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1411941600 {#95541
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1411941600 {#95542
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "11073-10424"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#95546 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95548 …}
  }
]

App\Twig\Components\ProductMostRecent {#96758
  +product: App\Entity\Product\Product {#95543
    #id: 11035
    #code: "IEEE00005468"
    #attributes: Doctrine\ORM\PersistentCollection {#95560 …}
    #variants: Doctrine\ORM\PersistentCollection {#95562 …}
    #options: Doctrine\ORM\PersistentCollection {#95566 …}
    #associations: Doctrine\ORM\PersistentCollection {#95564 …}
    #createdAt: DateTime @1751039438 {#95537
      date: 2025-06-27 17:50:38.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#95538
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95550 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96670
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95543}
        #id: 39149
        #name: "IEEE 11073-10424:2014"
        #slug: "ieee-11073-10424-2014-ieee00005468-242687"
        #description: """
          New IEEE Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between sleep apnoea breathing therapy equipment (SABTE) devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes), in a manner that enables plug-and-play interoperability, is established in this standard. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for SABTE. In this context, SABTE is defined as a device that is intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. SABTE is primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between sleep apnoea breathing therapy equipment and managers (e.g., cell phones, personal computers, personal health appliances, set top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments restricting optionality in base frameworks in favor of interoperability. This standard defines a common core of communication functionality for sleep apnoea breathing therapy equipment. In this context, sleep apnoea breathing therapy equipment are defined as devices that are intended to alleviate the symptoms of a patient who suffers from sleep apnoea by delivering a therapeutic breathing pressure to the patient. Sleep apnoea breathing therapy equipment are primarily used in the home health-care environment by a lay operator without direct professional supervision.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices (agents) and managers (e.g., cell phones, personal computers, personal health appliances, and set top boxes). Interoperability is key to growing the potential market for these devices and to enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Health informatics--Personal health device communication - Part 10424: Device Specialization--Sleep Apnoea Breathing Therapy Equipment (SABTE)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95552 …}
    #channels: Doctrine\ORM\PersistentCollection {#95558 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95554 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95556 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95544 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95539
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95540
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1411941600 {#95541
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1411941600 {#95542
      date: 2014-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "11073-10424"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#95546 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95548 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95574
    #id: 11494
    #code: "IEEE00006220"
    #attributes: Doctrine\ORM\PersistentCollection {#95591 …}
    #variants: Doctrine\ORM\PersistentCollection {#95593 …}
    #options: Doctrine\ORM\PersistentCollection {#95597 …}
    #associations: Doctrine\ORM\PersistentCollection {#95595 …}
    #createdAt: DateTime @1751039742 {#95568
      date: 2025-06-27 17:55:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95569
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95581 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96908
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95574}
        #id: 40985
        #name: "IEEE 11073-10420:2020"
        #slug: "ieee-11073-10420-2020-ieee00006220-243146"
        #description: """
          Revision Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) is established by this standard in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a<br />\n
          common core of communication functionality for personal telehealth body composition analyzers.In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a common core of<br />\n
          communication functionality for personal telehealth body composition analyzers. In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes). Interoperability is key to growing the potential market for these devices and enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standards for Health informatics--Device interoperability - Part 10420: Personal health device communication--Device specialization--Body composition analyzer"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95583 …}
    #channels: Doctrine\ORM\PersistentCollection {#95589 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95585 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95587 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95575 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95570
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1612825200 {#95571
      date: 2021-02-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605567600 {#95572
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605567600 {#95573
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-10420"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#95577 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95579 …}
  }
  "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 {#96888
  +product: App\Entity\Product\Product {#95574
    #id: 11494
    #code: "IEEE00006220"
    #attributes: Doctrine\ORM\PersistentCollection {#95591 …}
    #variants: Doctrine\ORM\PersistentCollection {#95593 …}
    #options: Doctrine\ORM\PersistentCollection {#95597 …}
    #associations: Doctrine\ORM\PersistentCollection {#95595 …}
    #createdAt: DateTime @1751039742 {#95568
      date: 2025-06-27 17:55:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95569
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95581 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96908
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95574}
        #id: 40985
        #name: "IEEE 11073-10420:2020"
        #slug: "ieee-11073-10420-2020-ieee00006220-243146"
        #description: """
          Revision Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) is established by this standard in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a<br />\n
          common core of communication functionality for personal telehealth body composition analyzers.In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a common core of<br />\n
          communication functionality for personal telehealth body composition analyzers. In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes). Interoperability is key to growing the potential market for these devices and enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standards for Health informatics--Device interoperability - Part 10420: Personal health device communication--Device specialization--Body composition analyzer"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95583 …}
    #channels: Doctrine\ORM\PersistentCollection {#95589 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95585 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95587 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95575 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95570
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1612825200 {#95571
      date: 2021-02-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605567600 {#95572
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605567600 {#95573
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-10420"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#95577 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95579 …}
  }
  +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 {#95574
    #id: 11494
    #code: "IEEE00006220"
    #attributes: Doctrine\ORM\PersistentCollection {#95591 …}
    #variants: Doctrine\ORM\PersistentCollection {#95593 …}
    #options: Doctrine\ORM\PersistentCollection {#95597 …}
    #associations: Doctrine\ORM\PersistentCollection {#95595 …}
    #createdAt: DateTime @1751039742 {#95568
      date: 2025-06-27 17:55:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95569
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95581 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96908
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95574}
        #id: 40985
        #name: "IEEE 11073-10420:2020"
        #slug: "ieee-11073-10420-2020-ieee00006220-243146"
        #description: """
          Revision Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) is established by this standard in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a<br />\n
          common core of communication functionality for personal telehealth body composition analyzers.In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a common core of<br />\n
          communication functionality for personal telehealth body composition analyzers. In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes). Interoperability is key to growing the potential market for these devices and enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standards for Health informatics--Device interoperability - Part 10420: Personal health device communication--Device specialization--Body composition analyzer"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95583 …}
    #channels: Doctrine\ORM\PersistentCollection {#95589 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95585 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95587 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95575 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95570
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1612825200 {#95571
      date: 2021-02-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605567600 {#95572
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605567600 {#95573
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-10420"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#95577 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95579 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#96926
  +product: App\Entity\Product\Product {#95574
    #id: 11494
    #code: "IEEE00006220"
    #attributes: Doctrine\ORM\PersistentCollection {#95591 …}
    #variants: Doctrine\ORM\PersistentCollection {#95593 …}
    #options: Doctrine\ORM\PersistentCollection {#95597 …}
    #associations: Doctrine\ORM\PersistentCollection {#95595 …}
    #createdAt: DateTime @1751039742 {#95568
      date: 2025-06-27 17:55:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95569
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95581 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96908
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95574}
        #id: 40985
        #name: "IEEE 11073-10420:2020"
        #slug: "ieee-11073-10420-2020-ieee00006220-243146"
        #description: """
          Revision Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) is established by this standard in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a<br />\n
          common core of communication functionality for personal telehealth body composition analyzers.In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a common core of<br />\n
          communication functionality for personal telehealth body composition analyzers. In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes). Interoperability is key to growing the potential market for these devices and enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standards for Health informatics--Device interoperability - Part 10420: Personal health device communication--Device specialization--Body composition analyzer"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95583 …}
    #channels: Doctrine\ORM\PersistentCollection {#95589 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95585 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95587 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95575 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95570
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1612825200 {#95571
      date: 2021-02-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605567600 {#95572
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605567600 {#95573
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-10420"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#95577 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95579 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95574
    #id: 11494
    #code: "IEEE00006220"
    #attributes: Doctrine\ORM\PersistentCollection {#95591 …}
    #variants: Doctrine\ORM\PersistentCollection {#95593 …}
    #options: Doctrine\ORM\PersistentCollection {#95597 …}
    #associations: Doctrine\ORM\PersistentCollection {#95595 …}
    #createdAt: DateTime @1751039742 {#95568
      date: 2025-06-27 17:55:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95569
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95581 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96908
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95574}
        #id: 40985
        #name: "IEEE 11073-10420:2020"
        #slug: "ieee-11073-10420-2020-ieee00006220-243146"
        #description: """
          Revision Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) is established by this standard in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a<br />\n
          common core of communication functionality for personal telehealth body composition analyzers.In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a common core of<br />\n
          communication functionality for personal telehealth body composition analyzers. In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes). Interoperability is key to growing the potential market for these devices and enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standards for Health informatics--Device interoperability - Part 10420: Personal health device communication--Device specialization--Body composition analyzer"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95583 …}
    #channels: Doctrine\ORM\PersistentCollection {#95589 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95585 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95587 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95575 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95570
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1612825200 {#95571
      date: 2021-02-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605567600 {#95572
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605567600 {#95573
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-10420"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#95577 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95579 …}
  }
]

App\Twig\Components\ProductMostRecent {#97000
  +product: App\Entity\Product\Product {#95574
    #id: 11494
    #code: "IEEE00006220"
    #attributes: Doctrine\ORM\PersistentCollection {#95591 …}
    #variants: Doctrine\ORM\PersistentCollection {#95593 …}
    #options: Doctrine\ORM\PersistentCollection {#95597 …}
    #associations: Doctrine\ORM\PersistentCollection {#95595 …}
    #createdAt: DateTime @1751039742 {#95568
      date: 2025-06-27 17:55:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95569
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95581 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#96908
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95574}
        #id: 40985
        #name: "IEEE 11073-10420:2020"
        #slug: "ieee-11073-10420-2020-ieee00006220-243146"
        #description: """
          Revision Standard - Active.<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) is established by this standard in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a<br />\n
          common core of communication functionality for personal telehealth body composition analyzers.In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          \t\t\t\t<br />\n
          Within the context of the ISO/IEEE 11073 family of standards for device communication, this standard establishes a normative definition of the communication between personal body composition analyzer agents and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes) in a manner that enables plug-and-play interoperability. It leverages appropriate portions of existing standards including ISO/IEEE 11073 terminology, information models, application profile standards, and transport standards. It specifies the use of specific term codes, formats, and behaviors in telehealth environments to restrict optionality in base frameworks in favor of interoperability. This standard defines a common core of<br />\n
          communication functionality for personal telehealth body composition analyzers. In this context, the phrase “body composition analyzer” is used broadly to cover analyzing devices that measure body impedances and compute the various body components including body fat from the impedance.<br />\n
          This standard addresses a need for an openly defined, independent standard for controlling information exchange to and from personal health devices and managers (e.g., cell phones, personal computers, personal health appliances, set-top boxes). Interoperability is key to growing the potential market for these devices and enabling people to be better informed participants in the management of their health.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standards for Health informatics--Device interoperability - Part 10420: Personal health device communication--Device specialization--Body composition analyzer"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95583 …}
    #channels: Doctrine\ORM\PersistentCollection {#95589 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95585 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95587 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95575 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95570
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1612825200 {#95571
      date: 2021-02-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1605567600 {#95572
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1605567600 {#95573
      date: 2020-11-17 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "11073-10420"
    -bookCollection: ""
    -pageCount: 78
    -documents: Doctrine\ORM\PersistentCollection {#95577 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95579 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1831 …}
}

[
  "product" => App\Entity\Product\Product {#95604
    #id: 11688
    #code: "IEEE00006448"
    #attributes: Doctrine\ORM\PersistentCollection {#95621 …}
    #variants: Doctrine\ORM\PersistentCollection {#95623 …}
    #options: Doctrine\ORM\PersistentCollection {#95627 …}
    #associations: Doctrine\ORM\PersistentCollection {#95625 …}
    #createdAt: DateTime @1751039898 {#95599
      date: 2025-06-27 17:58:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95600
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95611 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97159
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95604}
        #id: 41761
        #name: "ANSI/IEEE 450:1980"
        #slug: "ansi-ieee-450-1980-ieee00006448-243340"
        #description: """
          Revision Standard - Superseded.<br />\n
          Large stationary lead storage batteries play an ever increasing role in substation and generating<br />\n
          station control and power systems and in providing the back-up energy for emergencies. This recommended practice fulfillls the need within the industry to provide common or standard practices of maintenance, testing, and replacement. The methods described are applicable to all installations and battery sizes. The installations considered herein are designed for full-float operation with a battery charger serving to maintain the battery in a charged condition as well as to supply the normal dc load.<br />\n
          \t\t\t\t<br />\n
          This recommended practice is limited to providing recommended practices of maintenance, test schedules, and testing procedures that can be used to optimize the life and performance of large lead storage batteries. It also provides guidance to determine when batteries should be replaced. There are other test procedures and replacement techniques used within the industry (especially for smaller substation batteries) which are equally as effective but are beyond the scope of this recommended practice. Sizing, installation, qualification, other battery types, and application are also beyond the scope of this recommended practice. This recommended practice does not include any other component of the dc system nor surveillance and testing of the dc system, even though the battery is part of that system. Pre-operational and periodic dc system tests of chargers and other dc components may require that the battery be connected to the system. Details for these tests will depend on the requirements of the dc system and are not within the scope of this recommended practice
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Maintenance, Testing , and Replacement of Large Lead Storage Batteries for Generating Stations and Substations"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95613 …}
    #channels: Doctrine\ORM\PersistentCollection {#95619 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95615 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95617 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95605 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95601
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95602
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @341190000 {#95603
      date: 1980-10-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "450"
    -bookCollection: ""
    -pageCount: 14
    -documents: Doctrine\ORM\PersistentCollection {#95607 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95609 …}
  }
  "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 {#97139
  +product: App\Entity\Product\Product {#95604
    #id: 11688
    #code: "IEEE00006448"
    #attributes: Doctrine\ORM\PersistentCollection {#95621 …}
    #variants: Doctrine\ORM\PersistentCollection {#95623 …}
    #options: Doctrine\ORM\PersistentCollection {#95627 …}
    #associations: Doctrine\ORM\PersistentCollection {#95625 …}
    #createdAt: DateTime @1751039898 {#95599
      date: 2025-06-27 17:58:18.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#95600
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#95611 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#97159
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#95604}
        #id: 41761
        #name: "ANSI/IEEE 450:1980"
        #slug: "ansi-ieee-450-1980-ieee00006448-243340"
        #description: """
          Revision Standard - Superseded.<br />\n
          Large stationary lead storage batteries play an ever increasing role in substation and generating<br />\n
          station control and power systems and in providing the back-up energy for emergencies. This recommended practice fulfillls the need within the industry to provide common or standard practices of maintenance, testing, and replacement. The methods described are applicable to all installations and battery sizes. The installations considered herein are designed for full-float operation with a battery charger serving to maintain the battery in a charged condition as well as to supply the normal dc load.<br />\n
          \t\t\t\t<br />\n
          This recommended practice is limited to providing recommended practices of maintenance, test schedules, and testing procedures that can be used to optimize the life and performance of large lead storage batteries. It also provides guidance to determine when batteries should be replaced. There are other test procedures and replacement techniques used within the industry (especially for smaller substation batteries) which are equally as effective but are beyond the scope of this recommended practice. Sizing, installation, qualification, other battery types, and application are also beyond the scope of this recommended practice. This recommended practice does not include any other component of the dc system nor surveillance and testing of the dc system, even though the battery is part of that system. Pre-operational and periodic dc system tests of chargers and other dc components may require that the battery be connected to the system. Details for these tests will depend on the requirements of the dc system and are not within the scope of this recommended practice
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Maintenance, Testing , and Replacement of Large Lead Storage Batteries for Generating Stations and Substations"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#95613 …}
    #channels: Doctrine\ORM\PersistentCollection {#95619 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8776 …}
    #reviews: Doctrine\ORM\PersistentCollection {#95615 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#95617 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#95342 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95605 …}
    -apiLastModifiedAt: DateTime @1754517600 {#95601
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#95602
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @341190000 {#95603
      date: 1980-10-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "450"
    -bookCollection: ""
    -pageCount: 14
    -documents: Doctrine\ORM\PersistentCollection {#95607 …}
    -favorites: Doctrine\ORM\PersistentCollection {#95609 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}