Symfony Profiler

Components

3 Twig Components

7 Render Count

3 ms Render Time

80.0 MiB Memory Usage

Components

Name	Metadata	Render Count	Render Time
ProductState	"App\Twig\Components\ProductState" components/ProductState.html.twig	3	0.56ms
ProductMostRecent	"App\Twig\Components\ProductMostRecent" components/ProductMostRecent.html.twig	3	1.89ms
ProductType	"App\Twig\Components\ProductType" components/ProductType.html.twig	1	0.17ms

Render calls

ProductState	App\Twig\Components\ProductState	66.0 MiB	0.26 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#93007+product: App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

66.0 MiB

0.26 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#93007
  +product: App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductType	App\Twig\Components\ProductType	66.0 MiB	0.17 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} }]
Attributes	[]
Component	App\Twig\Components\ProductType {#93187+product: App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Standard" -typeAttributeCode: "type" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductType

App\Twig\Components\ProductType

66.0 MiB

0.17 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductType {#93187
  +product: App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	66.0 MiB	0.60 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#93262+product: App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

66.0 MiB

0.60 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#93262
  +product: App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductState	App\Twig\Components\ProductState	80.0 MiB	0.16 ms
Input props	["product" => App\Entity\Product\Product {#93672 #id: 10835 #code: "IEEE00005089" #attributes: Doctrine\ORM\PersistentCollection {#93652 …} #variants: Doctrine\ORM\PersistentCollection {#93649 …} #options: Doctrine\ORM\PersistentCollection {#93645 …} #associations: Doctrine\ORM\PersistentCollection {#93641 …} #createdAt: DateTime @1751039312 {#93679 date: 2025-06-27 17:48:32.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#93658 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93663 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93704 #locale: "en_US" #translatable: App\Entity\Product\Product {#93672} #id: 38349 #name: "IEEE C37.232:2011" #slug: "ieee-c37-232-2011-ieee00005089-242487" #description: """ Revision Standard - Inactive-Reserved.<br />\n A standard procedure for naming time sequence data (TSD) files, such as files produced by digital fault recorders, power swing recorders, power quality monitors, and so on, is specified. The sources of TSD files are described, and a survey of current naming techniques is provided. The advantages of using a common naming procedure are highlighted, and the limitations and applications are identified. Issues of compatibility across operating systems and various vintages, and adaptability to other types of files, are also discussed. The required and optional portions of the naming procedure are described in detail, and many examples are provided.<br />\n \t\t\t\t<br />\n This standard defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence.<br />\n The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving<br />\n large numbers of files. There is no other defined standard for naming such files at this time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME)" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93661 …} #channels: Doctrine\ORM\PersistentCollection {#93654 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93659 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93656 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93669 …} -apiLastModifiedAt: DateTime @1754517600 {#93642 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1649109600 {#93678 date: 2022-04-05 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1320793200 {#93677 date: 2011-11-09 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1648076400 {#93671 date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "C37.232" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#93667 …} -favorites: Doctrine\ORM\PersistentCollection {#93665 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#106834+product: App\Entity\Product\Product {#93672 #id: 10835 #code: "IEEE00005089" #attributes: Doctrine\ORM\PersistentCollection {#93652 …} #variants: Doctrine\ORM\PersistentCollection {#93649 …} #options: Doctrine\ORM\PersistentCollection {#93645 …} #associations: Doctrine\ORM\PersistentCollection {#93641 …} #createdAt: DateTime @1751039312 {#93679 date: 2025-06-27 17:48:32.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#93658 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93663 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93704 #locale: "en_US" #translatable: App\Entity\Product\Product {#93672} #id: 38349 #name: "IEEE C37.232:2011" #slug: "ieee-c37-232-2011-ieee00005089-242487" #description: """ Revision Standard - Inactive-Reserved.<br />\n A standard procedure for naming time sequence data (TSD) files, such as files produced by digital fault recorders, power swing recorders, power quality monitors, and so on, is specified. The sources of TSD files are described, and a survey of current naming techniques is provided. The advantages of using a common naming procedure are highlighted, and the limitations and applications are identified. Issues of compatibility across operating systems and various vintages, and adaptability to other types of files, are also discussed. The required and optional portions of the naming procedure are described in detail, and many examples are provided.<br />\n \t\t\t\t<br />\n This standard defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence.<br />\n The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving<br />\n large numbers of files. There is no other defined standard for naming such files at this time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME)" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93661 …} #channels: Doctrine\ORM\PersistentCollection {#93654 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93659 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93656 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93669 …} -apiLastModifiedAt: DateTime @1754517600 {#93642 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1649109600 {#93678 date: 2022-04-05 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1320793200 {#93677 date: 2011-11-09 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1648076400 {#93671 date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "C37.232" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#93667 …} -favorites: Doctrine\ORM\PersistentCollection {#93665 …} } +appearance: "state-withdrawn" +labels: [ "Withdrawn" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

80.0 MiB

0.16 ms

Input props

[
  "product" => App\Entity\Product\Product {#93672
    #id: 10835
    #code: "IEEE00005089"
    #attributes: Doctrine\ORM\PersistentCollection {#93652 …}
    #variants: Doctrine\ORM\PersistentCollection {#93649 …}
    #options: Doctrine\ORM\PersistentCollection {#93645 …}
    #associations: Doctrine\ORM\PersistentCollection {#93641 …}
    #createdAt: DateTime @1751039312 {#93679
      date: 2025-06-27 17:48:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93658
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93663 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93704
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93672}
        #id: 38349
        #name: "IEEE C37.232:2011"
        #slug: "ieee-c37-232-2011-ieee00005089-242487"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          A standard procedure for naming time sequence data (TSD) files, such as files produced by digital fault recorders, power swing recorders, power quality monitors, and so on, is specified. The sources of TSD files are described, and a survey of current naming techniques is provided. The advantages of using a common naming procedure are highlighted, and the limitations and applications are identified. Issues of compatibility across operating systems and various vintages, and adaptability to other types of files, are also discussed. The required and optional portions of the naming procedure are described in detail, and many examples are provided.<br />\n
          \t\t\t\t<br />\n
          This standard defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence.<br />\n
          The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving<br />\n
          large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93661 …}
    #channels: Doctrine\ORM\PersistentCollection {#93654 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93659 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93656 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93669 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93642
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1649109600 {#93678
      date: 2022-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1320793200 {#93677
      date: 2011-11-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#93671
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#93667 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93665 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#106834
  +product: App\Entity\Product\Product {#93672
    #id: 10835
    #code: "IEEE00005089"
    #attributes: Doctrine\ORM\PersistentCollection {#93652 …}
    #variants: Doctrine\ORM\PersistentCollection {#93649 …}
    #options: Doctrine\ORM\PersistentCollection {#93645 …}
    #associations: Doctrine\ORM\PersistentCollection {#93641 …}
    #createdAt: DateTime @1751039312 {#93679
      date: 2025-06-27 17:48:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93658
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93663 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93704
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93672}
        #id: 38349
        #name: "IEEE C37.232:2011"
        #slug: "ieee-c37-232-2011-ieee00005089-242487"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          A standard procedure for naming time sequence data (TSD) files, such as files produced by digital fault recorders, power swing recorders, power quality monitors, and so on, is specified. The sources of TSD files are described, and a survey of current naming techniques is provided. The advantages of using a common naming procedure are highlighted, and the limitations and applications are identified. Issues of compatibility across operating systems and various vintages, and adaptability to other types of files, are also discussed. The required and optional portions of the naming procedure are described in detail, and many examples are provided.<br />\n
          \t\t\t\t<br />\n
          This standard defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence.<br />\n
          The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving<br />\n
          large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93661 …}
    #channels: Doctrine\ORM\PersistentCollection {#93654 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93659 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93656 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93669 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93642
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1649109600 {#93678
      date: 2022-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1320793200 {#93677
      date: 2011-11-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#93671
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#93667 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93665 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	80.0 MiB	0.71 ms
Input props	["product" => App\Entity\Product\Product {#93672 #id: 10835 #code: "IEEE00005089" #attributes: Doctrine\ORM\PersistentCollection {#93652 …} #variants: Doctrine\ORM\PersistentCollection {#93649 …} #options: Doctrine\ORM\PersistentCollection {#93645 …} #associations: Doctrine\ORM\PersistentCollection {#93641 …} #createdAt: DateTime @1751039312 {#93679 date: 2025-06-27 17:48:32.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#93658 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93663 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93704 #locale: "en_US" #translatable: App\Entity\Product\Product {#93672} #id: 38349 #name: "IEEE C37.232:2011" #slug: "ieee-c37-232-2011-ieee00005089-242487" #description: """ Revision Standard - Inactive-Reserved.<br />\n A standard procedure for naming time sequence data (TSD) files, such as files produced by digital fault recorders, power swing recorders, power quality monitors, and so on, is specified. The sources of TSD files are described, and a survey of current naming techniques is provided. The advantages of using a common naming procedure are highlighted, and the limitations and applications are identified. Issues of compatibility across operating systems and various vintages, and adaptability to other types of files, are also discussed. The required and optional portions of the naming procedure are described in detail, and many examples are provided.<br />\n \t\t\t\t<br />\n This standard defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence.<br />\n The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving<br />\n large numbers of files. There is no other defined standard for naming such files at this time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME)" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93661 …} #channels: Doctrine\ORM\PersistentCollection {#93654 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93659 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93656 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93669 …} -apiLastModifiedAt: DateTime @1754517600 {#93642 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1649109600 {#93678 date: 2022-04-05 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1320793200 {#93677 date: 2011-11-09 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1648076400 {#93671 date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "C37.232" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#93667 …} -favorites: Doctrine\ORM\PersistentCollection {#93665 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#106899+product: App\Entity\Product\Product {#93672 #id: 10835 #code: "IEEE00005089" #attributes: Doctrine\ORM\PersistentCollection {#93652 …} #variants: Doctrine\ORM\PersistentCollection {#93649 …} #options: Doctrine\ORM\PersistentCollection {#93645 …} #associations: Doctrine\ORM\PersistentCollection {#93641 …} #createdAt: DateTime @1751039312 {#93679 date: 2025-06-27 17:48:32.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#93658 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93663 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93704 #locale: "en_US" #translatable: App\Entity\Product\Product {#93672} #id: 38349 #name: "IEEE C37.232:2011" #slug: "ieee-c37-232-2011-ieee00005089-242487" #description: """ Revision Standard - Inactive-Reserved.<br />\n A standard procedure for naming time sequence data (TSD) files, such as files produced by digital fault recorders, power swing recorders, power quality monitors, and so on, is specified. The sources of TSD files are described, and a survey of current naming techniques is provided. The advantages of using a common naming procedure are highlighted, and the limitations and applications are identified. Issues of compatibility across operating systems and various vintages, and adaptability to other types of files, are also discussed. The required and optional portions of the naming procedure are described in detail, and many examples are provided.<br />\n \t\t\t\t<br />\n This standard defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence.<br />\n The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving<br />\n large numbers of files. There is no other defined standard for naming such files at this time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME)" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93661 …} #channels: Doctrine\ORM\PersistentCollection {#93654 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#93659 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93656 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93669 …} -apiLastModifiedAt: DateTime @1754517600 {#93642 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1649109600 {#93678 date: 2022-04-05 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1320793200 {#93677 date: 2011-11-09 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1648076400 {#93671 date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "C37.232" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#93667 …} -favorites: Doctrine\ORM\PersistentCollection {#93665 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

80.0 MiB

0.71 ms

Input props

[
  "product" => App\Entity\Product\Product {#93672
    #id: 10835
    #code: "IEEE00005089"
    #attributes: Doctrine\ORM\PersistentCollection {#93652 …}
    #variants: Doctrine\ORM\PersistentCollection {#93649 …}
    #options: Doctrine\ORM\PersistentCollection {#93645 …}
    #associations: Doctrine\ORM\PersistentCollection {#93641 …}
    #createdAt: DateTime @1751039312 {#93679
      date: 2025-06-27 17:48:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93658
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93663 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93704
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93672}
        #id: 38349
        #name: "IEEE C37.232:2011"
        #slug: "ieee-c37-232-2011-ieee00005089-242487"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          A standard procedure for naming time sequence data (TSD) files, such as files produced by digital fault recorders, power swing recorders, power quality monitors, and so on, is specified. The sources of TSD files are described, and a survey of current naming techniques is provided. The advantages of using a common naming procedure are highlighted, and the limitations and applications are identified. Issues of compatibility across operating systems and various vintages, and adaptability to other types of files, are also discussed. The required and optional portions of the naming procedure are described in detail, and many examples are provided.<br />\n
          \t\t\t\t<br />\n
          This standard defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence.<br />\n
          The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving<br />\n
          large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93661 …}
    #channels: Doctrine\ORM\PersistentCollection {#93654 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93659 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93656 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93669 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93642
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1649109600 {#93678
      date: 2022-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1320793200 {#93677
      date: 2011-11-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#93671
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#93667 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93665 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#106899
  +product: App\Entity\Product\Product {#93672
    #id: 10835
    #code: "IEEE00005089"
    #attributes: Doctrine\ORM\PersistentCollection {#93652 …}
    #variants: Doctrine\ORM\PersistentCollection {#93649 …}
    #options: Doctrine\ORM\PersistentCollection {#93645 …}
    #associations: Doctrine\ORM\PersistentCollection {#93641 …}
    #createdAt: DateTime @1751039312 {#93679
      date: 2025-06-27 17:48:32.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#93658
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93663 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93704
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93672}
        #id: 38349
        #name: "IEEE C37.232:2011"
        #slug: "ieee-c37-232-2011-ieee00005089-242487"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          A standard procedure for naming time sequence data (TSD) files, such as files produced by digital fault recorders, power swing recorders, power quality monitors, and so on, is specified. The sources of TSD files are described, and a survey of current naming techniques is provided. The advantages of using a common naming procedure are highlighted, and the limitations and applications are identified. Issues of compatibility across operating systems and various vintages, and adaptability to other types of files, are also discussed. The required and optional portions of the naming procedure are described in detail, and many examples are provided.<br />\n
          \t\t\t\t<br />\n
          This standard defines a procedure for naming time sequence data (TSD) files that originate from digital protection and measurement devices, such as transient data records, event sequences, and periodic data logs. The filename includes, among other features, key portions of the information contained in the file, including, but not limited to, the names of the circuit, substation, and recording device, and the date and time of event occurrence.<br />\n
          The purpose of this standard is to define a procedure for naming TSD files, a procedure that is needed to resolve many problems that are associated with reporting, saving, exchanging, archiving, and retrieving<br />\n
          large numbers of files. There is no other defined standard for naming such files at this time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Format for Naming Time Sequence Data Files (COMNAME)"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93661 …}
    #channels: Doctrine\ORM\PersistentCollection {#93654 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93659 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93656 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93669 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93642
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1649109600 {#93678
      date: 2022-04-05 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1320793200 {#93677
      date: 2011-11-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1648076400 {#93671
      date: 2022-03-24 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "C37.232"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#93667 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93665 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductState	App\Twig\Components\ProductState	80.0 MiB	0.14 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#106964+product: App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

80.0 MiB

0.14 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#106964
  +product: App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	80.0 MiB	0.58 ms
Input props	["product" => App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#106991+product: App\Entity\Product\Product {#7310 #id: 10073 #code: "IEEE00003579" #attributes: Doctrine\ORM\PersistentCollection {#7700 …} #variants: Doctrine\ORM\PersistentCollection {#7743 …} #options: Doctrine\ORM\PersistentCollection {#7915 …} #associations: Doctrine\ORM\PersistentCollection {#7899 …} #createdAt: DateTime @1751038794 {#7274 date: 2025-06-27 17:39:54.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 {#7921 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7920 #locale: "en_US" #translatable: App\Entity\Product\Product {#7310} #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 {#7533 …} #channels: Doctrine\ORM\PersistentCollection {#7627 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …} #reviews: Doctrine\ORM\PersistentCollection {#7612 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7644 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#7292 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1187733600 {#7318 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 {#7464 …} -favorites: Doctrine\ORM\PersistentCollection {#7499 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

80.0 MiB

0.58 ms

Input props

[
  "product" => App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#106991
  +product: App\Entity\Product\Product {#7310
    #id: 10073
    #code: "IEEE00003579"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751038794 {#7274
      date: 2025-06-27 17:39:54.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 {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #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 {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1187733600 {#7318
      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 {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

Symfony Profiler

GET https://dev.normadoc.fr/_partial/products/10073/associations/10220/sort?fieldSort=%7B%22publishedAt%22%3A%22DESC%22%7D&isSubscriberDashboard=0&template=%40Syliu…

Configuration Settings

Theme

Page Width

Components

Components

Render calls