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

Response
200 OK
IP
216.73.217.119
Profiled on
Token
ea8b40

Components

4 Twig Components
8 Render Count
10 ms Render Time
156.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		3 0.68ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		3 2.25ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.18ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 8.36ms

Render calls

ProductState App\Twig\Components\ProductState 156.0 MiB 0.28 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93009
  +product: App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 156.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93202
  +product: App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 156.0 MiB 0.60 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93277
  +product: App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 156.0 MiB 0.16 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100220
  +product: App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
    "Confirmed"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 156.0 MiB 0.67 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100304
  +product: App\Entity\Product\Product {#7309
    #id: 9963
    #code: "IEEE00003351"
    #attributes: Doctrine\ORM\PersistentCollection {#7702 …}
    #variants: Doctrine\ORM\PersistentCollection {#7745 …}
    #options: Doctrine\ORM\PersistentCollection {#7917 …}
    #associations: Doctrine\ORM\PersistentCollection {#7901 …}
    #createdAt: DateTime @1751038704 {#7274
      date: 2025-06-27 17:38:24.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#7322
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7923 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7922
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7309}
        #id: 34861
        #name: "IEEE C37.231:2006 (R2012)"
        #slug: "ieee-c37-231-2006-r2012-ieee00003351-241615"
        #description: """
          New IEEE Standard - Inactive-Reserved.<br />\n
          Reaffirmed March 2012. This recommended practice deals with the implications surrounding the use and administration of firmware revisions for protection-related equipment. In general, the number of firmware revisions have become prolific since the introduction of microprocessor-based protection related equipment and no standard means of dealing with the issues surrounding this situation has been addressed. This recommended practice attempts to provide guidelines for the effective communication of firmware-related issues with the intent of helping to maximize the security and reliability of the power system.<br />\n
          \t\t\t\t<br />\n
          The scope of this recommended practice is to identify the means for timely and efficient exchange of information between manufacturers and users of protection-related equipment with respect to (1) changes in device firmware and (2) the impact of those changes. It will also include an examination of the technical and operational ramifications resulting from changes in the device firmware. Only hardware changes that impact firmware changes will be included.<br />\n
          The purpose of this recommended practice is to facilitate the exchange of information between manufacturers and users of microprocessor-based protection equipment on the changes in the firmware and the impact those changes will have in the performance of the devices.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Microprocessor-Based Protection Equipment Firmware Control"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7535 …}
    #channels: Doctrine\ORM\PersistentCollection {#7629 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7614 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7646 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7420 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1692223200 {#7292
      date: 2023-08-17 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1181080800 {#7318
      date: 2007-06-06 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: DateTime @1332972000 {#7316
      date: 2012-03-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -canceledAt: DateTime @1680127200 {#7315
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "C37.231"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7466 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7501 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 156.0 MiB 8.36 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121679
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#121697 …}
    #variants: Doctrine\ORM\PersistentCollection {#121695 …}
    #options: Doctrine\ORM\PersistentCollection {#121690 …}
    #associations: Doctrine\ORM\PersistentCollection {#121693 …}
    #createdAt: DateTime @1751038794 {#121686
      date: 2025-06-27 17:39:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121720
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121708 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121806
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121679}
        #id: 35301
        #name: "IEEE C37.232:2007"
        #slug: "ieee-c37-232-2007-ieee00003579-241725"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A procedure for naming time sequence data (TSD) files, such as files produced by<br />\n
          digital fault recorders, power swing recorders, power quality monitors, and so on is<br />\n
          recommended. The sources of TSD files are described, and a survey of current naming<br />\n
          techniques is provided. The advantages of using a common naming procedure are highlighted,<br />\n
          and the limitations and applications are identified. Issues of compatibility across operating<br />\n
          systems and various vintages, and adaptability to other types of files are also discussed. The<br />\n
          required and optional portions of the naming procedure are described in detail, and many<br />\n
          examples are provided.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines a procedure for naming time sequence data (TSD) files that originate<br />\n
          from digital protection and measurement devices, such as transient data records, event sequences, and<br />\n
          periodic data logs. The filename includes, among other features, key portions of the information contained<br />\n
          in the file, including, but not limited to, the names of the circuit, substation and recording device, and the<br />\n
          date and time of event occurrence.<br />\n
          The purpose of this recommended practice is to define a procedure for naming TSD files, a procedure that<br />\n
          is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and<br />\n
          retrieving large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Naming Time Sequence Data Files"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121706 …}
    #channels: Doctrine\ORM\PersistentCollection {#121699 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121703 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121701 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121713 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121672
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121714
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#121721
      date: 2007-08-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#121712 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121710 …}
  }
  "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 {#121765
  +product: App\Entity\Product\Product {#121679
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#121697 …}
    #variants: Doctrine\ORM\PersistentCollection {#121695 …}
    #options: Doctrine\ORM\PersistentCollection {#121690 …}
    #associations: Doctrine\ORM\PersistentCollection {#121693 …}
    #createdAt: DateTime @1751038794 {#121686
      date: 2025-06-27 17:39:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121720
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121708 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121806
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121679}
        #id: 35301
        #name: "IEEE C37.232:2007"
        #slug: "ieee-c37-232-2007-ieee00003579-241725"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A procedure for naming time sequence data (TSD) files, such as files produced by<br />\n
          digital fault recorders, power swing recorders, power quality monitors, and so on is<br />\n
          recommended. The sources of TSD files are described, and a survey of current naming<br />\n
          techniques is provided. The advantages of using a common naming procedure are highlighted,<br />\n
          and the limitations and applications are identified. Issues of compatibility across operating<br />\n
          systems and various vintages, and adaptability to other types of files are also discussed. The<br />\n
          required and optional portions of the naming procedure are described in detail, and many<br />\n
          examples are provided.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines a procedure for naming time sequence data (TSD) files that originate<br />\n
          from digital protection and measurement devices, such as transient data records, event sequences, and<br />\n
          periodic data logs. The filename includes, among other features, key portions of the information contained<br />\n
          in the file, including, but not limited to, the names of the circuit, substation and recording device, and the<br />\n
          date and time of event occurrence.<br />\n
          The purpose of this recommended practice is to define a procedure for naming TSD files, a procedure that<br />\n
          is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and<br />\n
          retrieving large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Naming Time Sequence Data Files"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121706 …}
    #channels: Doctrine\ORM\PersistentCollection {#121699 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121703 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121701 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121713 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121672
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121714
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#121721
      date: 2007-08-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#121712 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121710 …}
  }
  +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 156.0 MiB 0.24 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121679
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#121697 …}
    #variants: Doctrine\ORM\PersistentCollection {#121695 …}
    #options: Doctrine\ORM\PersistentCollection {#121690 …}
    #associations: Doctrine\ORM\PersistentCollection {#121693 …}
    #createdAt: DateTime @1751038794 {#121686
      date: 2025-06-27 17:39:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121720
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121708 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121806
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121679}
        #id: 35301
        #name: "IEEE C37.232:2007"
        #slug: "ieee-c37-232-2007-ieee00003579-241725"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A procedure for naming time sequence data (TSD) files, such as files produced by<br />\n
          digital fault recorders, power swing recorders, power quality monitors, and so on is<br />\n
          recommended. The sources of TSD files are described, and a survey of current naming<br />\n
          techniques is provided. The advantages of using a common naming procedure are highlighted,<br />\n
          and the limitations and applications are identified. Issues of compatibility across operating<br />\n
          systems and various vintages, and adaptability to other types of files are also discussed. The<br />\n
          required and optional portions of the naming procedure are described in detail, and many<br />\n
          examples are provided.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines a procedure for naming time sequence data (TSD) files that originate<br />\n
          from digital protection and measurement devices, such as transient data records, event sequences, and<br />\n
          periodic data logs. The filename includes, among other features, key portions of the information contained<br />\n
          in the file, including, but not limited to, the names of the circuit, substation and recording device, and the<br />\n
          date and time of event occurrence.<br />\n
          The purpose of this recommended practice is to define a procedure for naming TSD files, a procedure that<br />\n
          is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and<br />\n
          retrieving large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Naming Time Sequence Data Files"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121706 …}
    #channels: Doctrine\ORM\PersistentCollection {#121699 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121703 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121701 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121713 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121672
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121714
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#121721
      date: 2007-08-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#121712 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121710 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#121808
  +product: App\Entity\Product\Product {#121679
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#121697 …}
    #variants: Doctrine\ORM\PersistentCollection {#121695 …}
    #options: Doctrine\ORM\PersistentCollection {#121690 …}
    #associations: Doctrine\ORM\PersistentCollection {#121693 …}
    #createdAt: DateTime @1751038794 {#121686
      date: 2025-06-27 17:39:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121720
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121708 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121806
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121679}
        #id: 35301
        #name: "IEEE C37.232:2007"
        #slug: "ieee-c37-232-2007-ieee00003579-241725"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A procedure for naming time sequence data (TSD) files, such as files produced by<br />\n
          digital fault recorders, power swing recorders, power quality monitors, and so on is<br />\n
          recommended. The sources of TSD files are described, and a survey of current naming<br />\n
          techniques is provided. The advantages of using a common naming procedure are highlighted,<br />\n
          and the limitations and applications are identified. Issues of compatibility across operating<br />\n
          systems and various vintages, and adaptability to other types of files are also discussed. The<br />\n
          required and optional portions of the naming procedure are described in detail, and many<br />\n
          examples are provided.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines a procedure for naming time sequence data (TSD) files that originate<br />\n
          from digital protection and measurement devices, such as transient data records, event sequences, and<br />\n
          periodic data logs. The filename includes, among other features, key portions of the information contained<br />\n
          in the file, including, but not limited to, the names of the circuit, substation and recording device, and the<br />\n
          date and time of event occurrence.<br />\n
          The purpose of this recommended practice is to define a procedure for naming TSD files, a procedure that<br />\n
          is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and<br />\n
          retrieving large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Naming Time Sequence Data Files"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121706 …}
    #channels: Doctrine\ORM\PersistentCollection {#121699 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121703 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121701 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121713 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121672
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121714
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#121721
      date: 2007-08-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#121712 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121710 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 156.0 MiB 0.98 ms
Input props 
[
  "product" => App\Entity\Product\Product {#121679
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#121697 …}
    #variants: Doctrine\ORM\PersistentCollection {#121695 …}
    #options: Doctrine\ORM\PersistentCollection {#121690 …}
    #associations: Doctrine\ORM\PersistentCollection {#121693 …}
    #createdAt: DateTime @1751038794 {#121686
      date: 2025-06-27 17:39:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121720
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121708 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121806
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121679}
        #id: 35301
        #name: "IEEE C37.232:2007"
        #slug: "ieee-c37-232-2007-ieee00003579-241725"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A procedure for naming time sequence data (TSD) files, such as files produced by<br />\n
          digital fault recorders, power swing recorders, power quality monitors, and so on is<br />\n
          recommended. The sources of TSD files are described, and a survey of current naming<br />\n
          techniques is provided. The advantages of using a common naming procedure are highlighted,<br />\n
          and the limitations and applications are identified. Issues of compatibility across operating<br />\n
          systems and various vintages, and adaptability to other types of files are also discussed. The<br />\n
          required and optional portions of the naming procedure are described in detail, and many<br />\n
          examples are provided.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines a procedure for naming time sequence data (TSD) files that originate<br />\n
          from digital protection and measurement devices, such as transient data records, event sequences, and<br />\n
          periodic data logs. The filename includes, among other features, key portions of the information contained<br />\n
          in the file, including, but not limited to, the names of the circuit, substation and recording device, and the<br />\n
          date and time of event occurrence.<br />\n
          The purpose of this recommended practice is to define a procedure for naming TSD files, a procedure that<br />\n
          is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and<br />\n
          retrieving large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Naming Time Sequence Data Files"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121706 …}
    #channels: Doctrine\ORM\PersistentCollection {#121699 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121703 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121701 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121713 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121672
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121714
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#121721
      date: 2007-08-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#121712 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121710 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#121885
  +product: App\Entity\Product\Product {#121679
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#121697 …}
    #variants: Doctrine\ORM\PersistentCollection {#121695 …}
    #options: Doctrine\ORM\PersistentCollection {#121690 …}
    #associations: Doctrine\ORM\PersistentCollection {#121693 …}
    #createdAt: DateTime @1751038794 {#121686
      date: 2025-06-27 17:39:54.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121720
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121708 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121806
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121679}
        #id: 35301
        #name: "IEEE C37.232:2007"
        #slug: "ieee-c37-232-2007-ieee00003579-241725"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          A procedure for naming time sequence data (TSD) files, such as files produced by<br />\n
          digital fault recorders, power swing recorders, power quality monitors, and so on is<br />\n
          recommended. The sources of TSD files are described, and a survey of current naming<br />\n
          techniques is provided. The advantages of using a common naming procedure are highlighted,<br />\n
          and the limitations and applications are identified. Issues of compatibility across operating<br />\n
          systems and various vintages, and adaptability to other types of files are also discussed. The<br />\n
          required and optional portions of the naming procedure are described in detail, and many<br />\n
          examples are provided.<br />\n
          \t\t\t\t<br />\n
          This recommended practice defines a procedure for naming time sequence data (TSD) files that originate<br />\n
          from digital protection and measurement devices, such as transient data records, event sequences, and<br />\n
          periodic data logs. The filename includes, among other features, key portions of the information contained<br />\n
          in the file, including, but not limited to, the names of the circuit, substation and recording device, and the<br />\n
          date and time of event occurrence.<br />\n
          The purpose of this recommended practice is to define a procedure for naming TSD files, a procedure that<br />\n
          is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and<br />\n
          retrieving large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Naming Time Sequence Data Files"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121706 …}
    #channels: Doctrine\ORM\PersistentCollection {#121699 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7308 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121703 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121701 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7422 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121713 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121672
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121714
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#121721
      date: 2007-08-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 24
    -documents: Doctrine\ORM\PersistentCollection {#121712 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121710 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}