Components

4 Twig Components
8 Render Count
10 ms Render Time
1,066.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState
"App\Twig\Components\ProductState"
components/ProductState.html.twig
3 0.75ms
ProductMostRecent
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig
3 2.00ms
ProductType
"App\Twig\Components\ProductType"
components/ProductType.html.twig
1 0.20ms
ProductCard
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig
1 7.78ms

Render calls

ProductState App\Twig\Components\ProductState 1,066.0 MiB 0.42 ms
Input props
[
  "product" => App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]
Attributes
[
  "showFullLabel" => "true"
]
Component
App\Twig\Components\ProductState {#95062
  +product: App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 1,066.0 MiB 0.20 ms
Input props
[
  "product" => App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductType {#95242
  +product: App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 1,066.0 MiB 0.72 ms
Input props
[
  "product" => App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductMostRecent {#95317
  +product: App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 1,066.0 MiB 0.17 ms
Input props
[
  "product" => App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]
Attributes
[
  "showFullLabel" => "true"
]
Component
App\Twig\Components\ProductState {#102274
  +product: App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 1,066.0 MiB 0.64 ms
Input props
[
  "product" => App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductMostRecent {#102358
  +product: App\Entity\Product\Product {#7519
    #id: 12206
    #code: "IEEE00007260"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751040271 {#7536
      date: 2025-06-27 18:04:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7535
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 43833
        #name: "IEEE 2745.1:2019"
        #slug: "ieee-2745-1-2019-ieee00007260-243859"
        #description: """
          New IEEE Standard - Active.<br />\n
          An approach to preparing a functional specification for a unified power flow controller (UPFC) using modular multilevel converter (MMC) is documented by this guide. This guide provides the functional requirements for UPFC project application, including UPFC system composition, function and performance requirements, primary equipment requirements, control and protection requirements, characteristic description, spares, engineering studies, testing, documentation, as well as training of UPFC projects. The intention of this document is to serve as a base specification with an informative annex provided to guide utilities, manufacturers, integrators, and other interested entities to apply a particular UPFC project.<br />\n
          \t\t\t\t<br />\n
          This guide provides the functional requirements for unified power flow controller (UPFC) deployment, including application conditions, system architecture, function requirements, performance requirements, primary equipment requirements, control and protection requirements, auxiliary system requirements, testing, spares, and training of UPFC projects, which are suitable for UPFC in transmission power grids.<br />\n
          The purpose of this guide is to specify the functional requirements for UPFC project application, allowing utilities, integrators, and other interested entities to specify the application conditions and system architecture of UPFC, and define the requirements for function, performance, primary equipment, control and protection, commissioning, and testing of UPFC projects. This guide aims to provide the knowledge base, experience, and opportunities for greater utilization of UPFC.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Guide for Technology of Unified Power Flow Controller Using Modular Multilevel Converter - Part 1: Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7496
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1574809200 {#7531
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1574809200 {#7521
      date: 2019-11-27 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2745.1"
    -bookCollection: ""
    -pageCount: 87
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 1,066.0 MiB 7.78 ms
Input props
[
  "product" => App\Entity\Product\Product {#123633
    #id: 8341
    #code: "IEEE00000308"
    #attributes: Doctrine\ORM\PersistentCollection {#123613 …}
    #variants: Doctrine\ORM\PersistentCollection {#123611 …}
    #options: Doctrine\ORM\PersistentCollection {#123606 …}
    #associations: Doctrine\ORM\PersistentCollection {#123608 …}
    #createdAt: DateTime @1751037336 {#123604
      date: 2025-06-27 17:15:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123639
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123633}
        #id: 28373
        #name: "IEEE 139:1988 (R2012)"
        #slug: "ieee-139-1988-r2012-ieee00000308-239993"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist:1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. Etc.<br />\n
          \t\t\t\t<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist: 1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. 6) There is a question about the safety to nearby personnel because of the emissions from the equipment. Measurements should be made under the direction of an engineer skilled in making and interpreting rf field-strength measurements. These measurements are made after the equipment is installed and ready for use at its place of use, and after it has been inspected as described in 2.2. The measurement report should generally be kept on file for at least three years after new measurements are made or after the equipment is no longer in use. There are significant differences between the &quot;open field&quot; or anechoic chamber measurements common in electromagnetic compatibility (EMC) and electromagnetic interference (EMI) work and the on-site measurements of installed ISM equipment. Some of these differences are described below. 1) The measurement conditions are usually more difficult because of crowded measurement locations, reflections from surrounding walls and equipment, and signals from other sources. 2 2) It is reasonable to take advantage of the shielding provided by walls and other equipment located between the ISM Equipment Under Test (EUT) and the location at which field-strength information is required. While the effect of a single wall may be small, the total effect of other equipment and building structures may be significant. In any case, it is not necessary to make measurements in a way which eliminates the benefits of this shielding. Some equipment is designed to be operated in a shielded enclosure, either because of its own sensitivity to outside interference, or because of its emission characteristics. When measuring the emission from this equipment, take advantage of the attenuation of the enclosure by making the measurements outside the enclosure, with the equipment in its normal operating position. 3) Since the measurement equipment is disconnected, moved, and reconnected many times during a set of measurements, its calibration should be checked frequently. 4) ISM equipment may often be grouped for field-strength measurements, taking one set of measurements for the entire group. 5) Electromagnetic-emission measurements of installed ISM equipment are usually significantly less accurate than laboratory (open field or test chamber) measurements because of lack of control of the measurement environment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for the Measurement of Radio Frequency Emission from Industrial, Scientific, and Medical (ISM) Equipment Installed on User's Premises"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123621 …}
    #channels: Doctrine\ORM\PersistentCollection {#123615 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123619 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123617 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123630 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123590
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704927600 {#123638
      date: 2024-01-11 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @597884400 {#123597
      date: 1988-12-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1339106400 {#123610
      date: 2012-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#123631
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "139"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#123628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123626 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]
Attributes
[]
Component
App\Twig\Components\ProductCard {#123670
  +product: App\Entity\Product\Product {#123633
    #id: 8341
    #code: "IEEE00000308"
    #attributes: Doctrine\ORM\PersistentCollection {#123613 …}
    #variants: Doctrine\ORM\PersistentCollection {#123611 …}
    #options: Doctrine\ORM\PersistentCollection {#123606 …}
    #associations: Doctrine\ORM\PersistentCollection {#123608 …}
    #createdAt: DateTime @1751037336 {#123604
      date: 2025-06-27 17:15:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123639
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123633}
        #id: 28373
        #name: "IEEE 139:1988 (R2012)"
        #slug: "ieee-139-1988-r2012-ieee00000308-239993"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist:1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. Etc.<br />\n
          \t\t\t\t<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist: 1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. 6) There is a question about the safety to nearby personnel because of the emissions from the equipment. Measurements should be made under the direction of an engineer skilled in making and interpreting rf field-strength measurements. These measurements are made after the equipment is installed and ready for use at its place of use, and after it has been inspected as described in 2.2. The measurement report should generally be kept on file for at least three years after new measurements are made or after the equipment is no longer in use. There are significant differences between the &quot;open field&quot; or anechoic chamber measurements common in electromagnetic compatibility (EMC) and electromagnetic interference (EMI) work and the on-site measurements of installed ISM equipment. Some of these differences are described below. 1) The measurement conditions are usually more difficult because of crowded measurement locations, reflections from surrounding walls and equipment, and signals from other sources. 2 2) It is reasonable to take advantage of the shielding provided by walls and other equipment located between the ISM Equipment Under Test (EUT) and the location at which field-strength information is required. While the effect of a single wall may be small, the total effect of other equipment and building structures may be significant. In any case, it is not necessary to make measurements in a way which eliminates the benefits of this shielding. Some equipment is designed to be operated in a shielded enclosure, either because of its own sensitivity to outside interference, or because of its emission characteristics. When measuring the emission from this equipment, take advantage of the attenuation of the enclosure by making the measurements outside the enclosure, with the equipment in its normal operating position. 3) Since the measurement equipment is disconnected, moved, and reconnected many times during a set of measurements, its calibration should be checked frequently. 4) ISM equipment may often be grouped for field-strength measurements, taking one set of measurements for the entire group. 5) Electromagnetic-emission measurements of installed ISM equipment are usually significantly less accurate than laboratory (open field or test chamber) measurements because of lack of control of the measurement environment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for the Measurement of Radio Frequency Emission from Industrial, Scientific, and Medical (ISM) Equipment Installed on User's Premises"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123621 …}
    #channels: Doctrine\ORM\PersistentCollection {#123615 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123619 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123617 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123630 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123590
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704927600 {#123638
      date: 2024-01-11 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @597884400 {#123597
      date: 1988-12-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1339106400 {#123610
      date: 2012-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#123631
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "139"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#123628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123626 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}
ProductState App\Twig\Components\ProductState 1,066.0 MiB 0.16 ms
Input props
[
  "product" => App\Entity\Product\Product {#123633
    #id: 8341
    #code: "IEEE00000308"
    #attributes: Doctrine\ORM\PersistentCollection {#123613 …}
    #variants: Doctrine\ORM\PersistentCollection {#123611 …}
    #options: Doctrine\ORM\PersistentCollection {#123606 …}
    #associations: Doctrine\ORM\PersistentCollection {#123608 …}
    #createdAt: DateTime @1751037336 {#123604
      date: 2025-06-27 17:15:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123639
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123633}
        #id: 28373
        #name: "IEEE 139:1988 (R2012)"
        #slug: "ieee-139-1988-r2012-ieee00000308-239993"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist:1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. Etc.<br />\n
          \t\t\t\t<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist: 1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. 6) There is a question about the safety to nearby personnel because of the emissions from the equipment. Measurements should be made under the direction of an engineer skilled in making and interpreting rf field-strength measurements. These measurements are made after the equipment is installed and ready for use at its place of use, and after it has been inspected as described in 2.2. The measurement report should generally be kept on file for at least three years after new measurements are made or after the equipment is no longer in use. There are significant differences between the &quot;open field&quot; or anechoic chamber measurements common in electromagnetic compatibility (EMC) and electromagnetic interference (EMI) work and the on-site measurements of installed ISM equipment. Some of these differences are described below. 1) The measurement conditions are usually more difficult because of crowded measurement locations, reflections from surrounding walls and equipment, and signals from other sources. 2 2) It is reasonable to take advantage of the shielding provided by walls and other equipment located between the ISM Equipment Under Test (EUT) and the location at which field-strength information is required. While the effect of a single wall may be small, the total effect of other equipment and building structures may be significant. In any case, it is not necessary to make measurements in a way which eliminates the benefits of this shielding. Some equipment is designed to be operated in a shielded enclosure, either because of its own sensitivity to outside interference, or because of its emission characteristics. When measuring the emission from this equipment, take advantage of the attenuation of the enclosure by making the measurements outside the enclosure, with the equipment in its normal operating position. 3) Since the measurement equipment is disconnected, moved, and reconnected many times during a set of measurements, its calibration should be checked frequently. 4) ISM equipment may often be grouped for field-strength measurements, taking one set of measurements for the entire group. 5) Electromagnetic-emission measurements of installed ISM equipment are usually significantly less accurate than laboratory (open field or test chamber) measurements because of lack of control of the measurement environment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for the Measurement of Radio Frequency Emission from Industrial, Scientific, and Medical (ISM) Equipment Installed on User's Premises"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123621 …}
    #channels: Doctrine\ORM\PersistentCollection {#123615 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123619 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123617 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123630 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123590
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704927600 {#123638
      date: 2024-01-11 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @597884400 {#123597
      date: 1988-12-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1339106400 {#123610
      date: 2012-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#123631
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "139"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#123628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123626 …}
  }
]
Attributes
[
  "showFullLabel" => false
]
Component
App\Twig\Components\ProductState {#123728
  +product: App\Entity\Product\Product {#123633
    #id: 8341
    #code: "IEEE00000308"
    #attributes: Doctrine\ORM\PersistentCollection {#123613 …}
    #variants: Doctrine\ORM\PersistentCollection {#123611 …}
    #options: Doctrine\ORM\PersistentCollection {#123606 …}
    #associations: Doctrine\ORM\PersistentCollection {#123608 …}
    #createdAt: DateTime @1751037336 {#123604
      date: 2025-06-27 17:15:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123639
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123633}
        #id: 28373
        #name: "IEEE 139:1988 (R2012)"
        #slug: "ieee-139-1988-r2012-ieee00000308-239993"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist:1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. Etc.<br />\n
          \t\t\t\t<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist: 1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. 6) There is a question about the safety to nearby personnel because of the emissions from the equipment. Measurements should be made under the direction of an engineer skilled in making and interpreting rf field-strength measurements. These measurements are made after the equipment is installed and ready for use at its place of use, and after it has been inspected as described in 2.2. The measurement report should generally be kept on file for at least three years after new measurements are made or after the equipment is no longer in use. There are significant differences between the &quot;open field&quot; or anechoic chamber measurements common in electromagnetic compatibility (EMC) and electromagnetic interference (EMI) work and the on-site measurements of installed ISM equipment. Some of these differences are described below. 1) The measurement conditions are usually more difficult because of crowded measurement locations, reflections from surrounding walls and equipment, and signals from other sources. 2 2) It is reasonable to take advantage of the shielding provided by walls and other equipment located between the ISM Equipment Under Test (EUT) and the location at which field-strength information is required. While the effect of a single wall may be small, the total effect of other equipment and building structures may be significant. In any case, it is not necessary to make measurements in a way which eliminates the benefits of this shielding. Some equipment is designed to be operated in a shielded enclosure, either because of its own sensitivity to outside interference, or because of its emission characteristics. When measuring the emission from this equipment, take advantage of the attenuation of the enclosure by making the measurements outside the enclosure, with the equipment in its normal operating position. 3) Since the measurement equipment is disconnected, moved, and reconnected many times during a set of measurements, its calibration should be checked frequently. 4) ISM equipment may often be grouped for field-strength measurements, taking one set of measurements for the entire group. 5) Electromagnetic-emission measurements of installed ISM equipment are usually significantly less accurate than laboratory (open field or test chamber) measurements because of lack of control of the measurement environment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for the Measurement of Radio Frequency Emission from Industrial, Scientific, and Medical (ISM) Equipment Installed on User's Premises"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123621 …}
    #channels: Doctrine\ORM\PersistentCollection {#123615 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123619 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123617 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123630 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123590
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704927600 {#123638
      date: 2024-01-11 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @597884400 {#123597
      date: 1988-12-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1339106400 {#123610
      date: 2012-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#123631
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "139"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#123628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123626 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 1,066.0 MiB 0.63 ms
Input props
[
  "product" => App\Entity\Product\Product {#123633
    #id: 8341
    #code: "IEEE00000308"
    #attributes: Doctrine\ORM\PersistentCollection {#123613 …}
    #variants: Doctrine\ORM\PersistentCollection {#123611 …}
    #options: Doctrine\ORM\PersistentCollection {#123606 …}
    #associations: Doctrine\ORM\PersistentCollection {#123608 …}
    #createdAt: DateTime @1751037336 {#123604
      date: 2025-06-27 17:15:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123639
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123633}
        #id: 28373
        #name: "IEEE 139:1988 (R2012)"
        #slug: "ieee-139-1988-r2012-ieee00000308-239993"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist:1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. Etc.<br />\n
          \t\t\t\t<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist: 1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. 6) There is a question about the safety to nearby personnel because of the emissions from the equipment. Measurements should be made under the direction of an engineer skilled in making and interpreting rf field-strength measurements. These measurements are made after the equipment is installed and ready for use at its place of use, and after it has been inspected as described in 2.2. The measurement report should generally be kept on file for at least three years after new measurements are made or after the equipment is no longer in use. There are significant differences between the &quot;open field&quot; or anechoic chamber measurements common in electromagnetic compatibility (EMC) and electromagnetic interference (EMI) work and the on-site measurements of installed ISM equipment. Some of these differences are described below. 1) The measurement conditions are usually more difficult because of crowded measurement locations, reflections from surrounding walls and equipment, and signals from other sources. 2 2) It is reasonable to take advantage of the shielding provided by walls and other equipment located between the ISM Equipment Under Test (EUT) and the location at which field-strength information is required. While the effect of a single wall may be small, the total effect of other equipment and building structures may be significant. In any case, it is not necessary to make measurements in a way which eliminates the benefits of this shielding. Some equipment is designed to be operated in a shielded enclosure, either because of its own sensitivity to outside interference, or because of its emission characteristics. When measuring the emission from this equipment, take advantage of the attenuation of the enclosure by making the measurements outside the enclosure, with the equipment in its normal operating position. 3) Since the measurement equipment is disconnected, moved, and reconnected many times during a set of measurements, its calibration should be checked frequently. 4) ISM equipment may often be grouped for field-strength measurements, taking one set of measurements for the entire group. 5) Electromagnetic-emission measurements of installed ISM equipment are usually significantly less accurate than laboratory (open field or test chamber) measurements because of lack of control of the measurement environment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for the Measurement of Radio Frequency Emission from Industrial, Scientific, and Medical (ISM) Equipment Installed on User's Premises"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123621 …}
    #channels: Doctrine\ORM\PersistentCollection {#123615 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123619 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123617 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123630 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123590
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704927600 {#123638
      date: 2024-01-11 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @597884400 {#123597
      date: 1988-12-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1339106400 {#123610
      date: 2012-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#123631
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "139"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#123628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123626 …}
  }
]
Attributes
[]
Component
App\Twig\Components\ProductMostRecent {#123805
  +product: App\Entity\Product\Product {#123633
    #id: 8341
    #code: "IEEE00000308"
    #attributes: Doctrine\ORM\PersistentCollection {#123613 …}
    #variants: Doctrine\ORM\PersistentCollection {#123611 …}
    #options: Doctrine\ORM\PersistentCollection {#123606 …}
    #associations: Doctrine\ORM\PersistentCollection {#123608 …}
    #createdAt: DateTime @1751037336 {#123604
      date: 2025-06-27 17:15:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754606304 {#123639
      date: 2025-08-08 00:38:24.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123726
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123633}
        #id: 28373
        #name: "IEEE 139:1988 (R2012)"
        #slug: "ieee-139-1988-r2012-ieee00000308-239993"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist:1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. Etc.<br />\n
          \t\t\t\t<br />\n
          This document describes equipment inspection and radio frequency (rf) electromagnetic field measurement procedures for evaluation of rf industrial, scientific, and medical (ISM) equipment installed in the user's facility. The term, ISM equipment, as used here, includes equipment that generates rf energy for purposes other than radio communications, to cause physical, chemical, or biological changes; for example, industrial heaters (dielectric and induction), medical diathermy, ultrasonic equipment, rf plasma devices, and rf stabilized welders. These procedures are designed to help ensure that the equipment does not interfere with radio communications, navigation, and other essential radio services. The engineer responsible for the measurements should take all reasonable precautions to ensure that the maximum emission from the ISM equipment under test (EUT) has been measured. Radio frequency field-strength measurements of installed ISM equipment may be required if any of the following conditions exist: 1) The emission from the EUT was not measured by the manufacturer. 2) Because of its size or special operating conditions, the EUT could not be tested before installation. 3) Installed ISM equipment is suspected of causing interference. 4) ISM equipment has been modified in a way that could affect its rf emissions. 5) As the equipment ages, there is a question about its continued compliance. 6) There is a question about the safety to nearby personnel because of the emissions from the equipment. Measurements should be made under the direction of an engineer skilled in making and interpreting rf field-strength measurements. These measurements are made after the equipment is installed and ready for use at its place of use, and after it has been inspected as described in 2.2. The measurement report should generally be kept on file for at least three years after new measurements are made or after the equipment is no longer in use. There are significant differences between the &quot;open field&quot; or anechoic chamber measurements common in electromagnetic compatibility (EMC) and electromagnetic interference (EMI) work and the on-site measurements of installed ISM equipment. Some of these differences are described below. 1) The measurement conditions are usually more difficult because of crowded measurement locations, reflections from surrounding walls and equipment, and signals from other sources. 2 2) It is reasonable to take advantage of the shielding provided by walls and other equipment located between the ISM Equipment Under Test (EUT) and the location at which field-strength information is required. While the effect of a single wall may be small, the total effect of other equipment and building structures may be significant. In any case, it is not necessary to make measurements in a way which eliminates the benefits of this shielding. Some equipment is designed to be operated in a shielded enclosure, either because of its own sensitivity to outside interference, or because of its emission characteristics. When measuring the emission from this equipment, take advantage of the attenuation of the enclosure by making the measurements outside the enclosure, with the equipment in its normal operating position. 3) Since the measurement equipment is disconnected, moved, and reconnected many times during a set of measurements, its calibration should be checked frequently. 4) ISM equipment may often be grouped for field-strength measurements, taking one set of measurements for the entire group. 5) Electromagnetic-emission measurements of installed ISM equipment are usually significantly less accurate than laboratory (open field or test chamber) measurements because of lack of control of the measurement environment.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for the Measurement of Radio Frequency Emission from Industrial, Scientific, and Medical (ISM) Equipment Installed on User's Premises"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123621 …}
    #channels: Doctrine\ORM\PersistentCollection {#123615 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123619 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123617 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123630 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123590
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1704927600 {#123638
      date: 2024-01-11 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @597884400 {#123597
      date: 1988-12-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1339106400 {#123610
      date: 2012-06-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#123631
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "139"
    -bookCollection: ""
    -pageCount: 20
    -documents: Doctrine\ORM\PersistentCollection {#123628 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123626 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}