Symfony Profiler

Components

4 Twig Components

17 Render Count

23 ms Render Time

126.0 MiB Memory Usage

Components

Name	Metadata	Render Count	Render Time
ProductState	"App\Twig\Components\ProductState" components/ProductState.html.twig	7	3.26ms
ProductMostRecent	"App\Twig\Components\ProductMostRecent" components/ProductMostRecent.html.twig	7	5.64ms
ProductCard	"App\Twig\Components\ProductCard" components/ProductCard.html.twig	2	15.75ms
ProductType	"App\Twig\Components\ProductType" components/ProductType.html.twig	1	0.49ms

Render calls

ProductState	App\Twig\Components\ProductState	92.0 MiB	1.90 ms
Input props	["product" => App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#93068+product: App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } +appearance: "state-withdrawn" +labels: [ "Withdrawn" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

92.0 MiB

1.90 ms

Input props

[
  "product" => App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#93068
  +product: App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductType	App\Twig\Components\ProductType	92.0 MiB	0.49 ms
Input props	["product" => App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} }]
Attributes	[]
Component	App\Twig\Components\ProductType {#93239+product: App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } +label: "Standard" -typeAttributeCode: "type" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductType

App\Twig\Components\ProductType

92.0 MiB

0.49 ms

Input props

[
  "product" => App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductType {#93239
  +product: App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	92.0 MiB	1.03 ms
Input props	["product" => App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#93314+product: App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

92.0 MiB

1.03 ms

Input props

[
  "product" => App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#93314
  +product: App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductState	App\Twig\Components\ProductState	98.0 MiB	0.21 ms
Input props	["product" => App\Entity\Product\Product {#106758 #id: 9395 #code: "IEEE00002249" #attributes: Doctrine\ORM\PersistentCollection {#106741 …} #variants: Doctrine\ORM\PersistentCollection {#106738 …} #options: Doctrine\ORM\PersistentCollection {#106734 …} #associations: Doctrine\ORM\PersistentCollection {#106736 …} #createdAt: DateTime @1751038229 {#106766 date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#106739 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106752 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106791 #locale: "en_US" #translatable: App\Entity\Product\Product {#106758} #id: 32589 #name: "IEEE 1512:2000" #slug: "ieee-1512-2000-ieee00002249-241047" #description: """ New IEEE Standard - Superseded.<br />\n Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n \t\t\t\t<br />\n This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …} #channels: Doctrine\ORM\PersistentCollection {#106743 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#106747 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106745 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …} -apiLastModifiedAt: DateTime @1754517600 {#106726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106765 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @962920800 {#106764 date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 64 -documents: Doctrine\ORM\PersistentCollection {#106756 …} -favorites: Doctrine\ORM\PersistentCollection {#106754 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#106774+product: App\Entity\Product\Product {#106758 #id: 9395 #code: "IEEE00002249" #attributes: Doctrine\ORM\PersistentCollection {#106741 …} #variants: Doctrine\ORM\PersistentCollection {#106738 …} #options: Doctrine\ORM\PersistentCollection {#106734 …} #associations: Doctrine\ORM\PersistentCollection {#106736 …} #createdAt: DateTime @1751038229 {#106766 date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#106739 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106752 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106791 #locale: "en_US" #translatable: App\Entity\Product\Product {#106758} #id: 32589 #name: "IEEE 1512:2000" #slug: "ieee-1512-2000-ieee00002249-241047" #description: """ New IEEE Standard - Superseded.<br />\n Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n \t\t\t\t<br />\n This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …} #channels: Doctrine\ORM\PersistentCollection {#106743 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#106747 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106745 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …} -apiLastModifiedAt: DateTime @1754517600 {#106726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106765 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @962920800 {#106764 date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 64 -documents: Doctrine\ORM\PersistentCollection {#106756 …} -favorites: Doctrine\ORM\PersistentCollection {#106754 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

98.0 MiB

0.21 ms

Input props

[
  "product" => App\Entity\Product\Product {#106758
    #id: 9395
    #code: "IEEE00002249"
    #attributes: Doctrine\ORM\PersistentCollection {#106741 …}
    #variants: Doctrine\ORM\PersistentCollection {#106738 …}
    #options: Doctrine\ORM\PersistentCollection {#106734 …}
    #associations: Doctrine\ORM\PersistentCollection {#106736 …}
    #createdAt: DateTime @1751038229 {#106766
      date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#106739
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106791
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106758}
        #id: 32589
        #name: "IEEE 1512:2000"
        #slug: "ieee-1512-2000-ieee00002249-241047"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          \t\t\t\t<br />\n
          This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …}
    #channels: Doctrine\ORM\PersistentCollection {#106743 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106747 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106745 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106765
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @962920800 {#106764
      date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 64
    -documents: Doctrine\ORM\PersistentCollection {#106756 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106754 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#106774
  +product: App\Entity\Product\Product {#106758
    #id: 9395
    #code: "IEEE00002249"
    #attributes: Doctrine\ORM\PersistentCollection {#106741 …}
    #variants: Doctrine\ORM\PersistentCollection {#106738 …}
    #options: Doctrine\ORM\PersistentCollection {#106734 …}
    #associations: Doctrine\ORM\PersistentCollection {#106736 …}
    #createdAt: DateTime @1751038229 {#106766
      date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#106739
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106791
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106758}
        #id: 32589
        #name: "IEEE 1512:2000"
        #slug: "ieee-1512-2000-ieee00002249-241047"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          \t\t\t\t<br />\n
          This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …}
    #channels: Doctrine\ORM\PersistentCollection {#106743 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106747 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106745 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106765
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @962920800 {#106764
      date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 64
    -documents: Doctrine\ORM\PersistentCollection {#106756 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106754 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	98.0 MiB	0.76 ms
Input props	["product" => App\Entity\Product\Product {#106758 #id: 9395 #code: "IEEE00002249" #attributes: Doctrine\ORM\PersistentCollection {#106741 …} #variants: Doctrine\ORM\PersistentCollection {#106738 …} #options: Doctrine\ORM\PersistentCollection {#106734 …} #associations: Doctrine\ORM\PersistentCollection {#106736 …} #createdAt: DateTime @1751038229 {#106766 date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#106739 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106752 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106791 #locale: "en_US" #translatable: App\Entity\Product\Product {#106758} #id: 32589 #name: "IEEE 1512:2000" #slug: "ieee-1512-2000-ieee00002249-241047" #description: """ New IEEE Standard - Superseded.<br />\n Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n \t\t\t\t<br />\n This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …} #channels: Doctrine\ORM\PersistentCollection {#106743 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#106747 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106745 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …} -apiLastModifiedAt: DateTime @1754517600 {#106726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106765 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @962920800 {#106764 date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 64 -documents: Doctrine\ORM\PersistentCollection {#106756 …} -favorites: Doctrine\ORM\PersistentCollection {#106754 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#106873+product: App\Entity\Product\Product {#106758 #id: 9395 #code: "IEEE00002249" #attributes: Doctrine\ORM\PersistentCollection {#106741 …} #variants: Doctrine\ORM\PersistentCollection {#106738 …} #options: Doctrine\ORM\PersistentCollection {#106734 …} #associations: Doctrine\ORM\PersistentCollection {#106736 …} #createdAt: DateTime @1751038229 {#106766 date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#106739 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106752 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106791 #locale: "en_US" #translatable: App\Entity\Product\Product {#106758} #id: 32589 #name: "IEEE 1512:2000" #slug: "ieee-1512-2000-ieee00002249-241047" #description: """ New IEEE Standard - Superseded.<br />\n Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n \t\t\t\t<br />\n This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …} #channels: Doctrine\ORM\PersistentCollection {#106743 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#106747 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106745 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …} -apiLastModifiedAt: DateTime @1754517600 {#106726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106765 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @962920800 {#106764 date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 64 -documents: Doctrine\ORM\PersistentCollection {#106756 …} -favorites: Doctrine\ORM\PersistentCollection {#106754 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

98.0 MiB

0.76 ms

Input props

[
  "product" => App\Entity\Product\Product {#106758
    #id: 9395
    #code: "IEEE00002249"
    #attributes: Doctrine\ORM\PersistentCollection {#106741 …}
    #variants: Doctrine\ORM\PersistentCollection {#106738 …}
    #options: Doctrine\ORM\PersistentCollection {#106734 …}
    #associations: Doctrine\ORM\PersistentCollection {#106736 …}
    #createdAt: DateTime @1751038229 {#106766
      date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#106739
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106791
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106758}
        #id: 32589
        #name: "IEEE 1512:2000"
        #slug: "ieee-1512-2000-ieee00002249-241047"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          \t\t\t\t<br />\n
          This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …}
    #channels: Doctrine\ORM\PersistentCollection {#106743 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106747 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106745 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106765
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @962920800 {#106764
      date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 64
    -documents: Doctrine\ORM\PersistentCollection {#106756 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106754 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#106873
  +product: App\Entity\Product\Product {#106758
    #id: 9395
    #code: "IEEE00002249"
    #attributes: Doctrine\ORM\PersistentCollection {#106741 …}
    #variants: Doctrine\ORM\PersistentCollection {#106738 …}
    #options: Doctrine\ORM\PersistentCollection {#106734 …}
    #associations: Doctrine\ORM\PersistentCollection {#106736 …}
    #createdAt: DateTime @1751038229 {#106766
      date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#106739
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106791
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106758}
        #id: 32589
        #name: "IEEE 1512:2000"
        #slug: "ieee-1512-2000-ieee00002249-241047"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          \t\t\t\t<br />\n
          This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …}
    #channels: Doctrine\ORM\PersistentCollection {#106743 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106747 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106745 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106765
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @962920800 {#106764
      date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 64
    -documents: Doctrine\ORM\PersistentCollection {#106756 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106754 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductState	App\Twig\Components\ProductState	104.0 MiB	0.29 ms
Input props	["product" => App\Entity\Product\Product {#93755 #id: 10079 #code: "IEEE00003595" #attributes: Doctrine\ORM\PersistentCollection {#93737 …} #variants: Doctrine\ORM\PersistentCollection {#93734 …} #options: Doctrine\ORM\PersistentCollection {#93730 …} #associations: Doctrine\ORM\PersistentCollection {#93732 …} #createdAt: DateTime @1751038799 {#93763 date: 2025-06-27 17:39:59.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#93742 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93748 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93783 #locale: "en_US" #translatable: App\Entity\Product\Product {#93755} #id: 35325 #name: "IEEE 1512" #slug: "ieee-1512-ieee00003595-241731" #description: """ - Inactive-Withdrawn.<br />\n IEEE Std 1512(TM), an Intelligent Transportation Systems (ITS) standard, deals with information exchanges between public safety centers and traffic management centers.<br />\n \t\t\t\t<br />\n The purpose of the IEEE 1512 Implementation Guide is to provide guidelines for and assistance with the implementation process of IEEE Std 1512. This guide presents information and examples on how to facilitate the development of needs, requirements, and design content that can be used during the procurement, implementation, and verification phases of the system life cycle for projects that use IEEE Std 1512. """ #metaKeywords: null #metaDescription: null #shortDescription: "Guide for Implementing IEEE Std 1512(tm) - Using a Systems Engineering Process" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93746 …} #channels: Doctrine\ORM\PersistentCollection {#93739 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#93744 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93741 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93756 …} -apiLastModifiedAt: DateTime @1754517600 {#93726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#93762 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1225753200 {#93761 date: 2008-11-04 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 127 -documents: Doctrine\ORM\PersistentCollection {#93752 …} -favorites: Doctrine\ORM\PersistentCollection {#93750 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#113490+product: App\Entity\Product\Product {#93755 #id: 10079 #code: "IEEE00003595" #attributes: Doctrine\ORM\PersistentCollection {#93737 …} #variants: Doctrine\ORM\PersistentCollection {#93734 …} #options: Doctrine\ORM\PersistentCollection {#93730 …} #associations: Doctrine\ORM\PersistentCollection {#93732 …} #createdAt: DateTime @1751038799 {#93763 date: 2025-06-27 17:39:59.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#93742 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93748 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93783 #locale: "en_US" #translatable: App\Entity\Product\Product {#93755} #id: 35325 #name: "IEEE 1512" #slug: "ieee-1512-ieee00003595-241731" #description: """ - Inactive-Withdrawn.<br />\n IEEE Std 1512(TM), an Intelligent Transportation Systems (ITS) standard, deals with information exchanges between public safety centers and traffic management centers.<br />\n \t\t\t\t<br />\n The purpose of the IEEE 1512 Implementation Guide is to provide guidelines for and assistance with the implementation process of IEEE Std 1512. This guide presents information and examples on how to facilitate the development of needs, requirements, and design content that can be used during the procurement, implementation, and verification phases of the system life cycle for projects that use IEEE Std 1512. """ #metaKeywords: null #metaDescription: null #shortDescription: "Guide for Implementing IEEE Std 1512(tm) - Using a Systems Engineering Process" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93746 …} #channels: Doctrine\ORM\PersistentCollection {#93739 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#93744 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93741 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93756 …} -apiLastModifiedAt: DateTime @1754517600 {#93726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#93762 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1225753200 {#93761 date: 2008-11-04 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 127 -documents: Doctrine\ORM\PersistentCollection {#93752 …} -favorites: Doctrine\ORM\PersistentCollection {#93750 …} } +appearance: "state-withdrawn" +labels: [ "Withdrawn" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

104.0 MiB

0.29 ms

Input props

[
  "product" => App\Entity\Product\Product {#93755
    #id: 10079
    #code: "IEEE00003595"
    #attributes: Doctrine\ORM\PersistentCollection {#93737 …}
    #variants: Doctrine\ORM\PersistentCollection {#93734 …}
    #options: Doctrine\ORM\PersistentCollection {#93730 …}
    #associations: Doctrine\ORM\PersistentCollection {#93732 …}
    #createdAt: DateTime @1751038799 {#93763
      date: 2025-06-27 17:39:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#93742
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93748 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93783
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93755}
        #id: 35325
        #name: "IEEE 1512"
        #slug: "ieee-1512-ieee00003595-241731"
        #description: """
           - Inactive-Withdrawn.<br />\n
          IEEE Std 1512(TM), an Intelligent Transportation Systems (ITS) standard, deals with information exchanges between public safety centers and traffic management centers.<br />\n
          \t\t\t\t<br />\n
          The purpose of the IEEE 1512 Implementation Guide is to provide guidelines for and assistance with the implementation process of IEEE Std 1512. This guide presents information and examples on how to facilitate the development of needs, requirements, and design content that can be used during the procurement, implementation, and verification phases of the system life cycle for projects that use IEEE Std 1512.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Guide for Implementing IEEE Std 1512(tm) - Using a Systems Engineering Process"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93746 …}
    #channels: Doctrine\ORM\PersistentCollection {#93739 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93744 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93741 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93756 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93762
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1225753200 {#93761
      date: 2008-11-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#93752 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93750 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#113490
  +product: App\Entity\Product\Product {#93755
    #id: 10079
    #code: "IEEE00003595"
    #attributes: Doctrine\ORM\PersistentCollection {#93737 …}
    #variants: Doctrine\ORM\PersistentCollection {#93734 …}
    #options: Doctrine\ORM\PersistentCollection {#93730 …}
    #associations: Doctrine\ORM\PersistentCollection {#93732 …}
    #createdAt: DateTime @1751038799 {#93763
      date: 2025-06-27 17:39:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#93742
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93748 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93783
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93755}
        #id: 35325
        #name: "IEEE 1512"
        #slug: "ieee-1512-ieee00003595-241731"
        #description: """
           - Inactive-Withdrawn.<br />\n
          IEEE Std 1512(TM), an Intelligent Transportation Systems (ITS) standard, deals with information exchanges between public safety centers and traffic management centers.<br />\n
          \t\t\t\t<br />\n
          The purpose of the IEEE 1512 Implementation Guide is to provide guidelines for and assistance with the implementation process of IEEE Std 1512. This guide presents information and examples on how to facilitate the development of needs, requirements, and design content that can be used during the procurement, implementation, and verification phases of the system life cycle for projects that use IEEE Std 1512.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Guide for Implementing IEEE Std 1512(tm) - Using a Systems Engineering Process"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93746 …}
    #channels: Doctrine\ORM\PersistentCollection {#93739 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93744 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93741 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93756 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93762
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1225753200 {#93761
      date: 2008-11-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#93752 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93750 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	104.0 MiB	0.88 ms
Input props	["product" => App\Entity\Product\Product {#93755 #id: 10079 #code: "IEEE00003595" #attributes: Doctrine\ORM\PersistentCollection {#93737 …} #variants: Doctrine\ORM\PersistentCollection {#93734 …} #options: Doctrine\ORM\PersistentCollection {#93730 …} #associations: Doctrine\ORM\PersistentCollection {#93732 …} #createdAt: DateTime @1751038799 {#93763 date: 2025-06-27 17:39:59.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#93742 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93748 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93783 #locale: "en_US" #translatable: App\Entity\Product\Product {#93755} #id: 35325 #name: "IEEE 1512" #slug: "ieee-1512-ieee00003595-241731" #description: """ - Inactive-Withdrawn.<br />\n IEEE Std 1512(TM), an Intelligent Transportation Systems (ITS) standard, deals with information exchanges between public safety centers and traffic management centers.<br />\n \t\t\t\t<br />\n The purpose of the IEEE 1512 Implementation Guide is to provide guidelines for and assistance with the implementation process of IEEE Std 1512. This guide presents information and examples on how to facilitate the development of needs, requirements, and design content that can be used during the procurement, implementation, and verification phases of the system life cycle for projects that use IEEE Std 1512. """ #metaKeywords: null #metaDescription: null #shortDescription: "Guide for Implementing IEEE Std 1512(tm) - Using a Systems Engineering Process" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93746 …} #channels: Doctrine\ORM\PersistentCollection {#93739 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#93744 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93741 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93756 …} -apiLastModifiedAt: DateTime @1754517600 {#93726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#93762 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1225753200 {#93761 date: 2008-11-04 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 127 -documents: Doctrine\ORM\PersistentCollection {#93752 …} -favorites: Doctrine\ORM\PersistentCollection {#93750 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#113557+product: App\Entity\Product\Product {#93755 #id: 10079 #code: "IEEE00003595" #attributes: Doctrine\ORM\PersistentCollection {#93737 …} #variants: Doctrine\ORM\PersistentCollection {#93734 …} #options: Doctrine\ORM\PersistentCollection {#93730 …} #associations: Doctrine\ORM\PersistentCollection {#93732 …} #createdAt: DateTime @1751038799 {#93763 date: 2025-06-27 17:39:59.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#93742 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#93748 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#93783 #locale: "en_US" #translatable: App\Entity\Product\Product {#93755} #id: 35325 #name: "IEEE 1512" #slug: "ieee-1512-ieee00003595-241731" #description: """ - Inactive-Withdrawn.<br />\n IEEE Std 1512(TM), an Intelligent Transportation Systems (ITS) standard, deals with information exchanges between public safety centers and traffic management centers.<br />\n \t\t\t\t<br />\n The purpose of the IEEE 1512 Implementation Guide is to provide guidelines for and assistance with the implementation process of IEEE Std 1512. This guide presents information and examples on how to facilitate the development of needs, requirements, and design content that can be used during the procurement, implementation, and verification phases of the system life cycle for projects that use IEEE Std 1512. """ #metaKeywords: null #metaDescription: null #shortDescription: "Guide for Implementing IEEE Std 1512(tm) - Using a Systems Engineering Process" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#93746 …} #channels: Doctrine\ORM\PersistentCollection {#93739 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#93744 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#93741 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93756 …} -apiLastModifiedAt: DateTime @1754517600 {#93726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#93762 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1225753200 {#93761 date: 2008-11-04 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 127 -documents: Doctrine\ORM\PersistentCollection {#93752 …} -favorites: Doctrine\ORM\PersistentCollection {#93750 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

104.0 MiB

0.88 ms

Input props

[
  "product" => App\Entity\Product\Product {#93755
    #id: 10079
    #code: "IEEE00003595"
    #attributes: Doctrine\ORM\PersistentCollection {#93737 …}
    #variants: Doctrine\ORM\PersistentCollection {#93734 …}
    #options: Doctrine\ORM\PersistentCollection {#93730 …}
    #associations: Doctrine\ORM\PersistentCollection {#93732 …}
    #createdAt: DateTime @1751038799 {#93763
      date: 2025-06-27 17:39:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#93742
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93748 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93783
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93755}
        #id: 35325
        #name: "IEEE 1512"
        #slug: "ieee-1512-ieee00003595-241731"
        #description: """
           - Inactive-Withdrawn.<br />\n
          IEEE Std 1512(TM), an Intelligent Transportation Systems (ITS) standard, deals with information exchanges between public safety centers and traffic management centers.<br />\n
          \t\t\t\t<br />\n
          The purpose of the IEEE 1512 Implementation Guide is to provide guidelines for and assistance with the implementation process of IEEE Std 1512. This guide presents information and examples on how to facilitate the development of needs, requirements, and design content that can be used during the procurement, implementation, and verification phases of the system life cycle for projects that use IEEE Std 1512.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Guide for Implementing IEEE Std 1512(tm) - Using a Systems Engineering Process"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93746 …}
    #channels: Doctrine\ORM\PersistentCollection {#93739 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93744 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93741 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93756 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93762
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1225753200 {#93761
      date: 2008-11-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#93752 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93750 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#113557
  +product: App\Entity\Product\Product {#93755
    #id: 10079
    #code: "IEEE00003595"
    #attributes: Doctrine\ORM\PersistentCollection {#93737 …}
    #variants: Doctrine\ORM\PersistentCollection {#93734 …}
    #options: Doctrine\ORM\PersistentCollection {#93730 …}
    #associations: Doctrine\ORM\PersistentCollection {#93732 …}
    #createdAt: DateTime @1751038799 {#93763
      date: 2025-06-27 17:39:59.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#93742
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93748 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93783
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93755}
        #id: 35325
        #name: "IEEE 1512"
        #slug: "ieee-1512-ieee00003595-241731"
        #description: """
           - Inactive-Withdrawn.<br />\n
          IEEE Std 1512(TM), an Intelligent Transportation Systems (ITS) standard, deals with information exchanges between public safety centers and traffic management centers.<br />\n
          \t\t\t\t<br />\n
          The purpose of the IEEE 1512 Implementation Guide is to provide guidelines for and assistance with the implementation process of IEEE Std 1512. This guide presents information and examples on how to facilitate the development of needs, requirements, and design content that can be used during the procurement, implementation, and verification phases of the system life cycle for projects that use IEEE Std 1512.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "Guide for Implementing IEEE Std 1512(tm) - Using a Systems Engineering Process"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93746 …}
    #channels: Doctrine\ORM\PersistentCollection {#93739 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93744 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93741 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93756 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#93762
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1225753200 {#93761
      date: 2008-11-04 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 127
    -documents: Doctrine\ORM\PersistentCollection {#93752 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93750 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductState	App\Twig\Components\ProductState	104.0 MiB	0.27 ms
Input props	["product" => App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#113622+product: App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } +appearance: "state-withdrawn" +labels: [ "Withdrawn" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

104.0 MiB

0.27 ms

Input props

[
  "product" => App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#113622
  +product: App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	104.0 MiB	0.83 ms
Input props	["product" => App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#113649+product: App\Entity\Product\Product {#7311 #id: 10049 #code: "IEEE00003522" #attributes: Doctrine\ORM\PersistentCollection {#7701 …} #variants: Doctrine\ORM\PersistentCollection {#7744 …} #options: Doctrine\ORM\PersistentCollection {#7916 …} #associations: Doctrine\ORM\PersistentCollection {#7900 …} #createdAt: DateTime @1751038775 {#7274 date: 2025-06-27 17:39:35.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 {#7922 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#7921 #locale: "en_US" #translatable: App\Entity\Product\Product {#7311} #id: 35205 #name: "IEEE 1512:2006" #slug: "ieee-1512-2006-ieee00003522-241701" #description: """ Revision Standard - Inactive-Reserved.<br />\n This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n \t\t\t\t<br />\n This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers" -notes: "Inactive-Reserved" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …} #channels: Doctrine\ORM\PersistentCollection {#7628 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#7613 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#7645 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …} -apiLastModifiedAt: DateTime @1754517600 {#7317 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1581462000 {#7292 date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1154988000 {#7318 date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1573081200 {#7316 date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 547 -documents: Doctrine\ORM\PersistentCollection {#7465 …} -favorites: Doctrine\ORM\PersistentCollection {#7500 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

104.0 MiB

0.83 ms

Input props

[
  "product" => App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#113649
  +product: App\Entity\Product\Product {#7311
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038775 {#7274
      date: 2025-06-27 17:39:35.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 {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 35205
        #name: "IEEE 1512:2006"
        #slug: "ieee-1512-2006-ieee00003522-241701"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          This standard addresses the exchange of vital data about public safety and emergency management issues involved in transportation-related events, through common incident management message sets. The message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises the basic volume of the family of incident management standards, a multi-volume set of documents centered around this Base Standard. Other members of that family include three other companion volumes, specifying incident management message sets for transportation-management-related data exchange and hazardous-material- and cargo-related data exchange, etc. Collectively, that family of standards shall be referred to as the 1512 Family of Standards. The goal of that family of standards is to support efficient communication for the real-time, interagency management of transportation-related events. Those events include incidents, emergencies, accidents, planned roadway closures, special events, and disasters caused by humans or natural events. Those events include any such event that impacts transportation systems or that causes a report to be received by an emergency management system, whether or not the event actually affects a transportation system and whether or not a response is required.<br />\n
          \t\t\t\t<br />\n
          This standard is the Base Standard for a family of related standards that address the intercommunication needs of emergency management centers and other types of centers engaged in transportation incident management. Incident in this standard includes information concerning any transportation-related event that is received by the emergency management system, including planned roadway closures and special events, whether or not the incident actually affects traffic flow and whether or not a response is required. This standard specifies common incident management message sets to allow vital data exchange for information and coordination. It provides a common mechanism for this data exchange within the defined National ITS Architecture, with latitude for local agencies to determine what level of cooperation, and hence message exchanges, best meets their requirements. This standard is independent of communication protocols used in any local implementation. It also assumes that the mechanics of communication, such as addressing, are handled by communication management, which is not addressed in this standard. Other companion standards, herein referred to as companion volumes, will provide specific content and usage guidance for other types of centers that could participate in a local incident management system. Companion volumes dealing with the unique needs of transportation management, public safety, and hazardous materials centers have been developed as well. The Base Standard specifies messages, data frames, and data elements (DEs) for the basic underlying communication involved in real-time interagency transportation-related incident management. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.” Clause 6 and Clause 7 present the specified messages, data frames and data elements in ASN.1 format and in XML formats. A complete set of listing in ASN.1 and an XML schema are presented in the annexes.<br />\n
          This standard provides a framework for the exchange of messages used in incident management between emergency management centers and other types of centers, e.g., transportation management centers (TMCs). A minimum set of messages to be accommodated by compliant systems is dictated. Within the framework, there is ample flexibility, in that many messages are in fact composed of lists of optional DEs,<br />\n
          so those lists have the function of “vocabularies” of DEs. That is, the actual DEs specified in a local implementation can be selected from those lists. In addition, within some DEs, where there is a list of possible data values (e.g., possible center types and possible causes for evacuation), there are provisions for local implementers to add their own values. This provision provides for both a standardized lexicon for describing events as well as a local derivative list to be used. Because the dispatching systems of each resources that it wishes to exchange data about, this standard provides a flexible set of descriptive elements that can be implemented to provide differing levels of local, regional, and national interoperation. It remains the responsibility of participating local agencies to determine what level of interoperation is suitable for their own needs. In a local implementation, conformance with this standard may require extant interagency agreements to exchange particular messages using particular DEs selected from this standard. Those messages have been structured so that centers using different legacy systems, and centers with different data needs, can still use a set of common messages to exchange information with other centers. Furthermore, this standard shall be implemented in conjunction with related ITS standards that provide other required portions of the entire architecture. The related ITS standards include detailed message formatting with specific center and domain field of use, center-to-center exchange protocols, and messaging processes, including message delivery, security, and gateway functions. This standard acts as a “wrapper,” incorporating such domain-specific knowledge in its own messages to allow exchange of information in each companion volume for each type of center.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for Use by Emergency Management Centers"
        -notes: "Inactive-Reserved"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7292
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#7318
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7316
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductState	App\Twig\Components\ProductState	104.0 MiB	0.18 ms
Input props	["product" => App\Entity\Product\Product {#106758 #id: 9395 #code: "IEEE00002249" #attributes: Doctrine\ORM\PersistentCollection {#106741 …} #variants: Doctrine\ORM\PersistentCollection {#106738 …} #options: Doctrine\ORM\PersistentCollection {#106734 …} #associations: Doctrine\ORM\PersistentCollection {#106736 …} #createdAt: DateTime @1751038229 {#106766 date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#106739 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106752 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106791 #locale: "en_US" #translatable: App\Entity\Product\Product {#106758} #id: 32589 #name: "IEEE 1512:2000" #slug: "ieee-1512-2000-ieee00002249-241047" #description: """ New IEEE Standard - Superseded.<br />\n Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n \t\t\t\t<br />\n This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …} #channels: Doctrine\ORM\PersistentCollection {#106743 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#106747 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106745 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …} -apiLastModifiedAt: DateTime @1754517600 {#106726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106765 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @962920800 {#106764 date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 64 -documents: Doctrine\ORM\PersistentCollection {#106756 …} -favorites: Doctrine\ORM\PersistentCollection {#106754 …} } "showFullLabel" => "true"]
Attributes	[`"showFullLabel" => "true"`]
Component	App\Twig\Components\ProductState {#113713+product: App\Entity\Product\Product {#106758 #id: 9395 #code: "IEEE00002249" #attributes: Doctrine\ORM\PersistentCollection {#106741 …} #variants: Doctrine\ORM\PersistentCollection {#106738 …} #options: Doctrine\ORM\PersistentCollection {#106734 …} #associations: Doctrine\ORM\PersistentCollection {#106736 …} #createdAt: DateTime @1751038229 {#106766 date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#106739 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106752 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106791 #locale: "en_US" #translatable: App\Entity\Product\Product {#106758} #id: 32589 #name: "IEEE 1512:2000" #slug: "ieee-1512-2000-ieee00002249-241047" #description: """ New IEEE Standard - Superseded.<br />\n Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n \t\t\t\t<br />\n This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …} #channels: Doctrine\ORM\PersistentCollection {#106743 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#106747 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106745 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …} -apiLastModifiedAt: DateTime @1754517600 {#106726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106765 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @962920800 {#106764 date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 64 -documents: Doctrine\ORM\PersistentCollection {#106756 …} -favorites: Doctrine\ORM\PersistentCollection {#106754 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

104.0 MiB

0.18 ms

Input props

[
  "product" => App\Entity\Product\Product {#106758
    #id: 9395
    #code: "IEEE00002249"
    #attributes: Doctrine\ORM\PersistentCollection {#106741 …}
    #variants: Doctrine\ORM\PersistentCollection {#106738 …}
    #options: Doctrine\ORM\PersistentCollection {#106734 …}
    #associations: Doctrine\ORM\PersistentCollection {#106736 …}
    #createdAt: DateTime @1751038229 {#106766
      date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#106739
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106791
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106758}
        #id: 32589
        #name: "IEEE 1512:2000"
        #slug: "ieee-1512-2000-ieee00002249-241047"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          \t\t\t\t<br />\n
          This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …}
    #channels: Doctrine\ORM\PersistentCollection {#106743 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106747 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106745 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106765
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @962920800 {#106764
      date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 64
    -documents: Doctrine\ORM\PersistentCollection {#106756 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106754 …}
  }
  "showFullLabel" => "true"
]

Attributes

[
  "showFullLabel" => "true"
]

Component

App\Twig\Components\ProductState {#113713
  +product: App\Entity\Product\Product {#106758
    #id: 9395
    #code: "IEEE00002249"
    #attributes: Doctrine\ORM\PersistentCollection {#106741 …}
    #variants: Doctrine\ORM\PersistentCollection {#106738 …}
    #options: Doctrine\ORM\PersistentCollection {#106734 …}
    #associations: Doctrine\ORM\PersistentCollection {#106736 …}
    #createdAt: DateTime @1751038229 {#106766
      date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#106739
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106791
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106758}
        #id: 32589
        #name: "IEEE 1512:2000"
        #slug: "ieee-1512-2000-ieee00002249-241047"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          \t\t\t\t<br />\n
          This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …}
    #channels: Doctrine\ORM\PersistentCollection {#106743 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106747 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106745 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106765
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @962920800 {#106764
      date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 64
    -documents: Doctrine\ORM\PersistentCollection {#106756 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106754 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	104.0 MiB	0.85 ms
Input props	["product" => App\Entity\Product\Product {#106758 #id: 9395 #code: "IEEE00002249" #attributes: Doctrine\ORM\PersistentCollection {#106741 …} #variants: Doctrine\ORM\PersistentCollection {#106738 …} #options: Doctrine\ORM\PersistentCollection {#106734 …} #associations: Doctrine\ORM\PersistentCollection {#106736 …} #createdAt: DateTime @1751038229 {#106766 date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#106739 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106752 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106791 #locale: "en_US" #translatable: App\Entity\Product\Product {#106758} #id: 32589 #name: "IEEE 1512:2000" #slug: "ieee-1512-2000-ieee00002249-241047" #description: """ New IEEE Standard - Superseded.<br />\n Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n \t\t\t\t<br />\n This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …} #channels: Doctrine\ORM\PersistentCollection {#106743 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#106747 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106745 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …} -apiLastModifiedAt: DateTime @1754517600 {#106726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106765 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @962920800 {#106764 date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 64 -documents: Doctrine\ORM\PersistentCollection {#106756 …} -favorites: Doctrine\ORM\PersistentCollection {#106754 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#113740+product: App\Entity\Product\Product {#106758 #id: 9395 #code: "IEEE00002249" #attributes: Doctrine\ORM\PersistentCollection {#106741 …} #variants: Doctrine\ORM\PersistentCollection {#106738 …} #options: Doctrine\ORM\PersistentCollection {#106734 …} #associations: Doctrine\ORM\PersistentCollection {#106736 …} #createdAt: DateTime @1751038229 {#106766 date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#106739 date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#106752 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#106791 #locale: "en_US" #translatable: App\Entity\Product\Product {#106758} #id: 32589 #name: "IEEE 1512:2000" #slug: "ieee-1512-2000-ieee00002249-241047" #description: """ New IEEE Standard - Superseded.<br />\n Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n \t\t\t\t<br />\n This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers" -notes: "Superseded" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …} #channels: Doctrine\ORM\PersistentCollection {#106743 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#106747 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#106745 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …} -apiLastModifiedAt: DateTime @1754517600 {#106726 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#106765 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @962920800 {#106764 date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "1512" -bookCollection: "" -pageCount: 64 -documents: Doctrine\ORM\PersistentCollection {#106756 …} -favorites: Doctrine\ORM\PersistentCollection {#106754 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

104.0 MiB

0.85 ms

Input props

[
  "product" => App\Entity\Product\Product {#106758
    #id: 9395
    #code: "IEEE00002249"
    #attributes: Doctrine\ORM\PersistentCollection {#106741 …}
    #variants: Doctrine\ORM\PersistentCollection {#106738 …}
    #options: Doctrine\ORM\PersistentCollection {#106734 …}
    #associations: Doctrine\ORM\PersistentCollection {#106736 …}
    #createdAt: DateTime @1751038229 {#106766
      date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#106739
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106791
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106758}
        #id: 32589
        #name: "IEEE 1512:2000"
        #slug: "ieee-1512-2000-ieee00002249-241047"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          \t\t\t\t<br />\n
          This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …}
    #channels: Doctrine\ORM\PersistentCollection {#106743 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106747 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106745 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106765
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @962920800 {#106764
      date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 64
    -documents: Doctrine\ORM\PersistentCollection {#106756 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106754 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#113740
  +product: App\Entity\Product\Product {#106758
    #id: 9395
    #code: "IEEE00002249"
    #attributes: Doctrine\ORM\PersistentCollection {#106741 …}
    #variants: Doctrine\ORM\PersistentCollection {#106738 …}
    #options: Doctrine\ORM\PersistentCollection {#106734 …}
    #associations: Doctrine\ORM\PersistentCollection {#106736 …}
    #createdAt: DateTime @1751038229 {#106766
      date: 2025-06-27 17:30:29.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#106739
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106752 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106791
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106758}
        #id: 32589
        #name: "IEEE 1512:2000"
        #slug: "ieee-1512-2000-ieee00002249-241047"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Superseded by IEEE Std 1512-2006. This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          \t\t\t\t<br />\n
          This standard will be a base standard for Incident Management message sets which will be used by all response and/or dispatch centers such that the exchange of information will be standard and produce the needed responses(s). This standard will be limited to the common incident management message sets for use by emergency management centers. This project shall include the necessary research and compiling, analyzing, and the consolidation of the results into message sets for Incident Management communications.<br />\n
          This standard will produce a set of common message sets required for Incident Management generated and transmitted between the emergency management subsystem to all the other subsystems and Incident Management providers. The result will be consistent standardized communications among Incident Management centers, fleet and freight management centers, information service providers, Emergency Management centers, planning subsystems, Traffic Management centers and Transit Management centers that will reduce duplication of messages among the various subsystems and increase effective response time.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Incident Management Message Sets for use by Emergency Management Centers"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106749 …}
    #channels: Doctrine\ORM\PersistentCollection {#106743 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106747 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106745 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106759 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106726
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106765
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @962920800 {#106764
      date: 2000-07-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 64
    -documents: Doctrine\ORM\PersistentCollection {#106756 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106754 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductCard	App\Twig\Components\ProductCard	126.0 MiB	9.63 ms
Input props	["product" => App\Entity\Product\Product {#135271 #id: 9385 #code: "IEEE00002226" #attributes: Doctrine\ORM\PersistentCollection {#135254 …} #variants: Doctrine\ORM\PersistentCollection {#135252 …} #options: Doctrine\ORM\PersistentCollection {#135247 …} #associations: Doctrine\ORM\PersistentCollection {#135249 …} #createdAt: DateTime @1751038221 {#135244 date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969444 {#135279 date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135265 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135420 #locale: "en_US" #translatable: App\Entity\Product\Product {#135271} #id: 32549 #name: "IEEE 1488:2000" #slug: "ieee-1488-2000-ieee00002226-241037" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n \t\t\t\t<br />\n Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …} #channels: Doctrine\ORM\PersistentCollection {#135256 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135260 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135258 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …} -apiLastModifiedAt: DateTime @1743289200 {#135230 date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1578006000 {#135278 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @963439200 {#135237 date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1139180400 {#135250 date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1488" -bookCollection: "" -pageCount: 44 -documents: Doctrine\ORM\PersistentCollection {#135269 …} -favorites: Doctrine\ORM\PersistentCollection {#135267 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "additionalClasses" => "product__teaser--with-grey-border" "hasStretchedLink" => true "hoverType" => "shadow" "linkLabel" => "See more"]
Attributes	[]
Component	App\Twig\Components\ProductCard {#135353+product: App\Entity\Product\Product {#135271 #id: 9385 #code: "IEEE00002226" #attributes: Doctrine\ORM\PersistentCollection {#135254 …} #variants: Doctrine\ORM\PersistentCollection {#135252 …} #options: Doctrine\ORM\PersistentCollection {#135247 …} #associations: Doctrine\ORM\PersistentCollection {#135249 …} #createdAt: DateTime @1751038221 {#135244 date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969444 {#135279 date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135265 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135420 #locale: "en_US" #translatable: App\Entity\Product\Product {#135271} #id: 32549 #name: "IEEE 1488:2000" #slug: "ieee-1488-2000-ieee00002226-241037" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n \t\t\t\t<br />\n Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …} #channels: Doctrine\ORM\PersistentCollection {#135256 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135260 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135258 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …} -apiLastModifiedAt: DateTime @1743289200 {#135230 date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1578006000 {#135278 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @963439200 {#135237 date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1139180400 {#135250 date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1488" -bookCollection: "" -pageCount: 44 -documents: Doctrine\ORM\PersistentCollection {#135269 …} -favorites: Doctrine\ORM\PersistentCollection {#135267 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "product__teaser--with-grey-border" +linkLabel: "See more" +imageFilter: "product_thumbnail_teaser" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "shadow"}

ProductCard

App\Twig\Components\ProductCard

126.0 MiB

9.63 ms

Input props

[
  "product" => App\Entity\Product\Product {#135271
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#135254 …}
    #variants: Doctrine\ORM\PersistentCollection {#135252 …}
    #options: Doctrine\ORM\PersistentCollection {#135247 …}
    #associations: Doctrine\ORM\PersistentCollection {#135249 …}
    #createdAt: DateTime @1751038221 {#135244
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#135279
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135265 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135420
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135271}
        #id: 32549
        #name: "IEEE 1488:2000"
        #slug: "ieee-1488-2000-ieee00002226-241037"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n
          The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …}
    #channels: Doctrine\ORM\PersistentCollection {#135256 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135260 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135258 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …}
    -apiLastModifiedAt: DateTime @1743289200 {#135230
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135278
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#135237
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#135250
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#135269 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135267 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

Attributes

[]

Component

App\Twig\Components\ProductCard {#135353
  +product: App\Entity\Product\Product {#135271
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#135254 …}
    #variants: Doctrine\ORM\PersistentCollection {#135252 …}
    #options: Doctrine\ORM\PersistentCollection {#135247 …}
    #associations: Doctrine\ORM\PersistentCollection {#135249 …}
    #createdAt: DateTime @1751038221 {#135244
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#135279
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135265 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135420
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135271}
        #id: 32549
        #name: "IEEE 1488:2000"
        #slug: "ieee-1488-2000-ieee00002226-241037"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n
          The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …}
    #channels: Doctrine\ORM\PersistentCollection {#135256 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135260 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135258 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …}
    -apiLastModifiedAt: DateTime @1743289200 {#135230
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135278
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#135237
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#135250
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#135269 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135267 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}

ProductState	App\Twig\Components\ProductState	126.0 MiB	0.23 ms
Input props	["product" => App\Entity\Product\Product {#135271 #id: 9385 #code: "IEEE00002226" #attributes: Doctrine\ORM\PersistentCollection {#135254 …} #variants: Doctrine\ORM\PersistentCollection {#135252 …} #options: Doctrine\ORM\PersistentCollection {#135247 …} #associations: Doctrine\ORM\PersistentCollection {#135249 …} #createdAt: DateTime @1751038221 {#135244 date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969444 {#135279 date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135265 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135420 #locale: "en_US" #translatable: App\Entity\Product\Product {#135271} #id: 32549 #name: "IEEE 1488:2000" #slug: "ieee-1488-2000-ieee00002226-241037" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n \t\t\t\t<br />\n Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …} #channels: Doctrine\ORM\PersistentCollection {#135256 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135260 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135258 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …} -apiLastModifiedAt: DateTime @1743289200 {#135230 date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1578006000 {#135278 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @963439200 {#135237 date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1139180400 {#135250 date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1488" -bookCollection: "" -pageCount: 44 -documents: Doctrine\ORM\PersistentCollection {#135269 …} -favorites: Doctrine\ORM\PersistentCollection {#135267 …} }]
Attributes	[`"showFullLabel" => false`]
Component	App\Twig\Components\ProductState {#135424+product: App\Entity\Product\Product {#135271 #id: 9385 #code: "IEEE00002226" #attributes: Doctrine\ORM\PersistentCollection {#135254 …} #variants: Doctrine\ORM\PersistentCollection {#135252 …} #options: Doctrine\ORM\PersistentCollection {#135247 …} #associations: Doctrine\ORM\PersistentCollection {#135249 …} #createdAt: DateTime @1751038221 {#135244 date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969444 {#135279 date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135265 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135420 #locale: "en_US" #translatable: App\Entity\Product\Product {#135271} #id: 32549 #name: "IEEE 1488:2000" #slug: "ieee-1488-2000-ieee00002226-241037" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n \t\t\t\t<br />\n Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …} #channels: Doctrine\ORM\PersistentCollection {#135256 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135260 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135258 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …} -apiLastModifiedAt: DateTime @1743289200 {#135230 date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1578006000 {#135278 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @963439200 {#135237 date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1139180400 {#135250 date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1488" -bookCollection: "" -pageCount: 44 -documents: Doctrine\ORM\PersistentCollection {#135269 …} -favorites: Doctrine\ORM\PersistentCollection {#135267 …} } +appearance: "state-withdrawn" +labels: [ "Withdrawn" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

126.0 MiB

0.23 ms

Input props

[
  "product" => App\Entity\Product\Product {#135271
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#135254 …}
    #variants: Doctrine\ORM\PersistentCollection {#135252 …}
    #options: Doctrine\ORM\PersistentCollection {#135247 …}
    #associations: Doctrine\ORM\PersistentCollection {#135249 …}
    #createdAt: DateTime @1751038221 {#135244
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#135279
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135265 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135420
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135271}
        #id: 32549
        #name: "IEEE 1488:2000"
        #slug: "ieee-1488-2000-ieee00002226-241037"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n
          The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …}
    #channels: Doctrine\ORM\PersistentCollection {#135256 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135260 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135258 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …}
    -apiLastModifiedAt: DateTime @1743289200 {#135230
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135278
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#135237
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#135250
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#135269 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135267 …}
  }
]

Attributes

[
  "showFullLabel" => false
]

Component

App\Twig\Components\ProductState {#135424
  +product: App\Entity\Product\Product {#135271
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#135254 …}
    #variants: Doctrine\ORM\PersistentCollection {#135252 …}
    #options: Doctrine\ORM\PersistentCollection {#135247 …}
    #associations: Doctrine\ORM\PersistentCollection {#135249 …}
    #createdAt: DateTime @1751038221 {#135244
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#135279
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135265 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135420
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135271}
        #id: 32549
        #name: "IEEE 1488:2000"
        #slug: "ieee-1488-2000-ieee00002226-241037"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n
          The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …}
    #channels: Doctrine\ORM\PersistentCollection {#135256 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135260 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135258 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …}
    -apiLastModifiedAt: DateTime @1743289200 {#135230
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135278
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#135237
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#135250
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#135269 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135267 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	126.0 MiB	0.68 ms
Input props	["product" => App\Entity\Product\Product {#135271 #id: 9385 #code: "IEEE00002226" #attributes: Doctrine\ORM\PersistentCollection {#135254 …} #variants: Doctrine\ORM\PersistentCollection {#135252 …} #options: Doctrine\ORM\PersistentCollection {#135247 …} #associations: Doctrine\ORM\PersistentCollection {#135249 …} #createdAt: DateTime @1751038221 {#135244 date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969444 {#135279 date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135265 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135420 #locale: "en_US" #translatable: App\Entity\Product\Product {#135271} #id: 32549 #name: "IEEE 1488:2000" #slug: "ieee-1488-2000-ieee00002226-241037" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n \t\t\t\t<br />\n Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …} #channels: Doctrine\ORM\PersistentCollection {#135256 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135260 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135258 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …} -apiLastModifiedAt: DateTime @1743289200 {#135230 date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1578006000 {#135278 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @963439200 {#135237 date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1139180400 {#135250 date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1488" -bookCollection: "" -pageCount: 44 -documents: Doctrine\ORM\PersistentCollection {#135269 …} -favorites: Doctrine\ORM\PersistentCollection {#135267 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#135502+product: App\Entity\Product\Product {#135271 #id: 9385 #code: "IEEE00002226" #attributes: Doctrine\ORM\PersistentCollection {#135254 …} #variants: Doctrine\ORM\PersistentCollection {#135252 …} #options: Doctrine\ORM\PersistentCollection {#135247 …} #associations: Doctrine\ORM\PersistentCollection {#135249 …} #createdAt: DateTime @1751038221 {#135244 date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753969444 {#135279 date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135265 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135420 #locale: "en_US" #translatable: App\Entity\Product\Product {#135271} #id: 32549 #name: "IEEE 1488:2000" #slug: "ieee-1488-2000-ieee00002226-241037" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n \t\t\t\t<br />\n Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …} #channels: Doctrine\ORM\PersistentCollection {#135256 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135260 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135258 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …} -apiLastModifiedAt: DateTime @1743289200 {#135230 date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1578006000 {#135278 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @963439200 {#135237 date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1139180400 {#135250 date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1488" -bookCollection: "" -pageCount: 44 -documents: Doctrine\ORM\PersistentCollection {#135269 …} -favorites: Doctrine\ORM\PersistentCollection {#135267 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

126.0 MiB

0.68 ms

Input props

[
  "product" => App\Entity\Product\Product {#135271
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#135254 …}
    #variants: Doctrine\ORM\PersistentCollection {#135252 …}
    #options: Doctrine\ORM\PersistentCollection {#135247 …}
    #associations: Doctrine\ORM\PersistentCollection {#135249 …}
    #createdAt: DateTime @1751038221 {#135244
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#135279
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135265 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135420
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135271}
        #id: 32549
        #name: "IEEE 1488:2000"
        #slug: "ieee-1488-2000-ieee00002226-241037"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n
          The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …}
    #channels: Doctrine\ORM\PersistentCollection {#135256 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135260 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135258 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …}
    -apiLastModifiedAt: DateTime @1743289200 {#135230
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135278
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#135237
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#135250
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#135269 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135267 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#135502
  +product: App\Entity\Product\Product {#135271
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#135254 …}
    #variants: Doctrine\ORM\PersistentCollection {#135252 …}
    #options: Doctrine\ORM\PersistentCollection {#135247 …}
    #associations: Doctrine\ORM\PersistentCollection {#135249 …}
    #createdAt: DateTime @1751038221 {#135244
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#135279
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135265 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135420
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135271}
        #id: 32549
        #name: "IEEE 1488:2000"
        #slug: "ieee-1488-2000-ieee00002226-241037"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          The expanding use of digital communications among subsystems of the transportation infrastructure has spawned the development of message sets for the communications between these subsystems. A format for Intelligent Transportation System (ITS) message sets, including common terms (e.g., object identifier), as well as attributes necessary to document ITS data messages, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          Research, compile and consolidate information leading to the publication of a standard for a template for message sets for intelligent transportation systems (ITS). The template will provide an overall syntax and structure for ITS message sets.<br />\n
          The global interest in interoperability of communication systems in the transportation infrastructure, e.g. vehicles, management centers, and roadside systems has prompted the ITS user community to seek a standard template for message sets. The users of the standard will be the developers of message sets for intelligent transportation systems. The benefit will be the interoperability of systems developed using these message sets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Message Set Template for Intelligent Transportation Systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135263 …}
    #channels: Doctrine\ORM\PersistentCollection {#135256 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135260 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135258 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135273 …}
    -apiLastModifiedAt: DateTime @1743289200 {#135230
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135278
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#135237
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#135250
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#135269 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135267 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductCard	App\Twig\Components\ProductCard	126.0 MiB	6.12 ms
Input props	["product" => App\Entity\Product\Product {#135238 #id: 9397 #code: "IEEE00002251" #attributes: Doctrine\ORM\PersistentCollection {#135322 …} #variants: Doctrine\ORM\PersistentCollection {#135321 …} #options: Doctrine\ORM\PersistentCollection {#135316 …} #associations: Doctrine\ORM\PersistentCollection {#135318 …} #createdAt: DateTime @1751038231 {#135245 date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#135243 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135319 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135629 #locale: "en_US" #translatable: App\Entity\Product\Product {#135238} #id: 32597 #name: "IEEE 1512.2:2004" #slug: "ieee-1512-2-2004-ieee00002251-241049" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n \t\t\t\t<br />\n Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …} #channels: Doctrine\ORM\PersistentCollection {#135327 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135282 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135328 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …} -apiLastModifiedAt: DateTime @1754517600 {#135242 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135241 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1101769200 {#135240 date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1262991600 {#135239 date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512.2" -bookCollection: "" -pageCount: 183 -documents: Doctrine\ORM\PersistentCollection {#135234 …} -favorites: Doctrine\ORM\PersistentCollection {#135227 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "additionalClasses" => "product__teaser--with-grey-border" "hasStretchedLink" => true "hoverType" => "shadow" "linkLabel" => "See more"]
Attributes	[]
Component	App\Twig\Components\ProductCard {#135590+product: App\Entity\Product\Product {#135238 #id: 9397 #code: "IEEE00002251" #attributes: Doctrine\ORM\PersistentCollection {#135322 …} #variants: Doctrine\ORM\PersistentCollection {#135321 …} #options: Doctrine\ORM\PersistentCollection {#135316 …} #associations: Doctrine\ORM\PersistentCollection {#135318 …} #createdAt: DateTime @1751038231 {#135245 date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#135243 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135319 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135629 #locale: "en_US" #translatable: App\Entity\Product\Product {#135238} #id: 32597 #name: "IEEE 1512.2:2004" #slug: "ieee-1512-2-2004-ieee00002251-241049" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n \t\t\t\t<br />\n Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …} #channels: Doctrine\ORM\PersistentCollection {#135327 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135282 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135328 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …} -apiLastModifiedAt: DateTime @1754517600 {#135242 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135241 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1101769200 {#135240 date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1262991600 {#135239 date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512.2" -bookCollection: "" -pageCount: 183 -documents: Doctrine\ORM\PersistentCollection {#135234 …} -favorites: Doctrine\ORM\PersistentCollection {#135227 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "product__teaser--with-grey-border" +linkLabel: "See more" +imageFilter: "product_thumbnail_teaser" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "shadow"}

ProductCard

App\Twig\Components\ProductCard

126.0 MiB

6.12 ms

Input props

[
  "product" => App\Entity\Product\Product {#135238
    #id: 9397
    #code: "IEEE00002251"
    #attributes: Doctrine\ORM\PersistentCollection {#135322 …}
    #variants: Doctrine\ORM\PersistentCollection {#135321 …}
    #options: Doctrine\ORM\PersistentCollection {#135316 …}
    #associations: Doctrine\ORM\PersistentCollection {#135318 …}
    #createdAt: DateTime @1751038231 {#135245
      date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#135243
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135319 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135629
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135238}
        #id: 32597
        #name: "IEEE 1512.2:2004"
        #slug: "ieee-1512-2-2004-ieee00002251-241049"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n
          \t\t\t\t<br />\n
          Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n
          Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …}
    #channels: Doctrine\ORM\PersistentCollection {#135327 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135282 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135328 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135242
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135241
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1101769200 {#135240
      date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1262991600 {#135239
      date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.2"
    -bookCollection: ""
    -pageCount: 183
    -documents: Doctrine\ORM\PersistentCollection {#135234 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135227 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

Attributes

[]

Component

App\Twig\Components\ProductCard {#135590
  +product: App\Entity\Product\Product {#135238
    #id: 9397
    #code: "IEEE00002251"
    #attributes: Doctrine\ORM\PersistentCollection {#135322 …}
    #variants: Doctrine\ORM\PersistentCollection {#135321 …}
    #options: Doctrine\ORM\PersistentCollection {#135316 …}
    #associations: Doctrine\ORM\PersistentCollection {#135318 …}
    #createdAt: DateTime @1751038231 {#135245
      date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#135243
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135319 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135629
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135238}
        #id: 32597
        #name: "IEEE 1512.2:2004"
        #slug: "ieee-1512-2-2004-ieee00002251-241049"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n
          \t\t\t\t<br />\n
          Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n
          Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …}
    #channels: Doctrine\ORM\PersistentCollection {#135327 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135282 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135328 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135242
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135241
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1101769200 {#135240
      date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1262991600 {#135239
      date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.2"
    -bookCollection: ""
    -pageCount: 183
    -documents: Doctrine\ORM\PersistentCollection {#135234 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135227 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}

ProductState	App\Twig\Components\ProductState	126.0 MiB	0.19 ms
Input props	["product" => App\Entity\Product\Product {#135238 #id: 9397 #code: "IEEE00002251" #attributes: Doctrine\ORM\PersistentCollection {#135322 …} #variants: Doctrine\ORM\PersistentCollection {#135321 …} #options: Doctrine\ORM\PersistentCollection {#135316 …} #associations: Doctrine\ORM\PersistentCollection {#135318 …} #createdAt: DateTime @1751038231 {#135245 date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#135243 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135319 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135629 #locale: "en_US" #translatable: App\Entity\Product\Product {#135238} #id: 32597 #name: "IEEE 1512.2:2004" #slug: "ieee-1512-2-2004-ieee00002251-241049" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n \t\t\t\t<br />\n Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …} #channels: Doctrine\ORM\PersistentCollection {#135327 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135282 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135328 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …} -apiLastModifiedAt: DateTime @1754517600 {#135242 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135241 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1101769200 {#135240 date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1262991600 {#135239 date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512.2" -bookCollection: "" -pageCount: 183 -documents: Doctrine\ORM\PersistentCollection {#135234 …} -favorites: Doctrine\ORM\PersistentCollection {#135227 …} }]
Attributes	[`"showFullLabel" => false`]
Component	App\Twig\Components\ProductState {#135636+product: App\Entity\Product\Product {#135238 #id: 9397 #code: "IEEE00002251" #attributes: Doctrine\ORM\PersistentCollection {#135322 …} #variants: Doctrine\ORM\PersistentCollection {#135321 …} #options: Doctrine\ORM\PersistentCollection {#135316 …} #associations: Doctrine\ORM\PersistentCollection {#135318 …} #createdAt: DateTime @1751038231 {#135245 date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#135243 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135319 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135629 #locale: "en_US" #translatable: App\Entity\Product\Product {#135238} #id: 32597 #name: "IEEE 1512.2:2004" #slug: "ieee-1512-2-2004-ieee00002251-241049" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n \t\t\t\t<br />\n Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …} #channels: Doctrine\ORM\PersistentCollection {#135327 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135282 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135328 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …} -apiLastModifiedAt: DateTime @1754517600 {#135242 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135241 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1101769200 {#135240 date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1262991600 {#135239 date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512.2" -bookCollection: "" -pageCount: 183 -documents: Doctrine\ORM\PersistentCollection {#135234 …} -favorites: Doctrine\ORM\PersistentCollection {#135227 …} } +appearance: "state-withdrawn" +labels: [ "Withdrawn" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductState

App\Twig\Components\ProductState

126.0 MiB

0.19 ms

Input props

[
  "product" => App\Entity\Product\Product {#135238
    #id: 9397
    #code: "IEEE00002251"
    #attributes: Doctrine\ORM\PersistentCollection {#135322 …}
    #variants: Doctrine\ORM\PersistentCollection {#135321 …}
    #options: Doctrine\ORM\PersistentCollection {#135316 …}
    #associations: Doctrine\ORM\PersistentCollection {#135318 …}
    #createdAt: DateTime @1751038231 {#135245
      date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#135243
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135319 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135629
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135238}
        #id: 32597
        #name: "IEEE 1512.2:2004"
        #slug: "ieee-1512-2-2004-ieee00002251-241049"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n
          \t\t\t\t<br />\n
          Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n
          Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …}
    #channels: Doctrine\ORM\PersistentCollection {#135327 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135282 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135328 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135242
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135241
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1101769200 {#135240
      date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1262991600 {#135239
      date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.2"
    -bookCollection: ""
    -pageCount: 183
    -documents: Doctrine\ORM\PersistentCollection {#135234 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135227 …}
  }
]

Attributes

[
  "showFullLabel" => false
]

Component

App\Twig\Components\ProductState {#135636
  +product: App\Entity\Product\Product {#135238
    #id: 9397
    #code: "IEEE00002251"
    #attributes: Doctrine\ORM\PersistentCollection {#135322 …}
    #variants: Doctrine\ORM\PersistentCollection {#135321 …}
    #options: Doctrine\ORM\PersistentCollection {#135316 …}
    #associations: Doctrine\ORM\PersistentCollection {#135318 …}
    #createdAt: DateTime @1751038231 {#135245
      date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#135243
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135319 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135629
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135238}
        #id: 32597
        #name: "IEEE 1512.2:2004"
        #slug: "ieee-1512-2-2004-ieee00002251-241049"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n
          \t\t\t\t<br />\n
          Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n
          Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …}
    #channels: Doctrine\ORM\PersistentCollection {#135327 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135282 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135328 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135242
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135241
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1101769200 {#135240
      date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1262991600 {#135239
      date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.2"
    -bookCollection: ""
    -pageCount: 183
    -documents: Doctrine\ORM\PersistentCollection {#135234 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135227 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

ProductMostRecent	App\Twig\Components\ProductMostRecent	126.0 MiB	0.61 ms
Input props	["product" => App\Entity\Product\Product {#135238 #id: 9397 #code: "IEEE00002251" #attributes: Doctrine\ORM\PersistentCollection {#135322 …} #variants: Doctrine\ORM\PersistentCollection {#135321 …} #options: Doctrine\ORM\PersistentCollection {#135316 …} #associations: Doctrine\ORM\PersistentCollection {#135318 …} #createdAt: DateTime @1751038231 {#135245 date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#135243 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135319 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135629 #locale: "en_US" #translatable: App\Entity\Product\Product {#135238} #id: 32597 #name: "IEEE 1512.2:2004" #slug: "ieee-1512-2-2004-ieee00002251-241049" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n \t\t\t\t<br />\n Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …} #channels: Doctrine\ORM\PersistentCollection {#135327 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135282 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135328 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …} -apiLastModifiedAt: DateTime @1754517600 {#135242 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135241 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1101769200 {#135240 date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1262991600 {#135239 date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512.2" -bookCollection: "" -pageCount: 183 -documents: Doctrine\ORM\PersistentCollection {#135234 …} -favorites: Doctrine\ORM\PersistentCollection {#135227 …} }]
Attributes	[]
Component	App\Twig\Components\ProductMostRecent {#135713+product: App\Entity\Product\Product {#135238 #id: 9397 #code: "IEEE00002251" #attributes: Doctrine\ORM\PersistentCollection {#135322 …} #variants: Doctrine\ORM\PersistentCollection {#135321 …} #options: Doctrine\ORM\PersistentCollection {#135316 …} #associations: Doctrine\ORM\PersistentCollection {#135318 …} #createdAt: DateTime @1751038231 {#135245 date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607004 {#135243 date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#135319 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#135629 #locale: "en_US" #translatable: App\Entity\Product\Product {#135238} #id: 32597 #name: "IEEE 1512.2:2004" #slug: "ieee-1512-2-2004-ieee00002251-241049" #description: """ New IEEE Standard - Inactive-Withdrawn.<br />\n This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n \t\t\t\t<br />\n Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers" -notes: "Inactive-Withdrawn" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …} #channels: Doctrine\ORM\PersistentCollection {#135327 …} #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …} #reviews: Doctrine\ORM\PersistentCollection {#135282 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#135328 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …} -apiLastModifiedAt: DateTime @1754517600 {#135242 date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#135241 date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1101769200 {#135240 date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1262991600 {#135239 date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00) } -edition: null -coreDocument: "1512.2" -bookCollection: "" -pageCount: 183 -documents: Doctrine\ORM\PersistentCollection {#135234 …} -favorites: Doctrine\ORM\PersistentCollection {#135227 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}}

ProductMostRecent

App\Twig\Components\ProductMostRecent

126.0 MiB

0.61 ms

Input props

[
  "product" => App\Entity\Product\Product {#135238
    #id: 9397
    #code: "IEEE00002251"
    #attributes: Doctrine\ORM\PersistentCollection {#135322 …}
    #variants: Doctrine\ORM\PersistentCollection {#135321 …}
    #options: Doctrine\ORM\PersistentCollection {#135316 …}
    #associations: Doctrine\ORM\PersistentCollection {#135318 …}
    #createdAt: DateTime @1751038231 {#135245
      date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#135243
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135319 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135629
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135238}
        #id: 32597
        #name: "IEEE 1512.2:2004"
        #slug: "ieee-1512-2-2004-ieee00002251-241049"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n
          \t\t\t\t<br />\n
          Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n
          Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …}
    #channels: Doctrine\ORM\PersistentCollection {#135327 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135282 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135328 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135242
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135241
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1101769200 {#135240
      date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1262991600 {#135239
      date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.2"
    -bookCollection: ""
    -pageCount: 183
    -documents: Doctrine\ORM\PersistentCollection {#135234 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135227 …}
  }
]

Attributes

[]

Component

App\Twig\Components\ProductMostRecent {#135713
  +product: App\Entity\Product\Product {#135238
    #id: 9397
    #code: "IEEE00002251"
    #attributes: Doctrine\ORM\PersistentCollection {#135322 …}
    #variants: Doctrine\ORM\PersistentCollection {#135321 …}
    #options: Doctrine\ORM\PersistentCollection {#135316 …}
    #associations: Doctrine\ORM\PersistentCollection {#135318 …}
    #createdAt: DateTime @1751038231 {#135245
      date: 2025-06-27 17:30:31.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#135243
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135319 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135629
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135238}
        #id: 32597
        #name: "IEEE 1512.2:2004"
        #slug: "ieee-1512-2-2004-ieee00002251-241049"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          This standard addresses the exchange of vital data about public safety issues involved in transportation-related events, through common incident management message sets. Message sets specified are consistent with the National Intelligent Transportation Systems Architecture and are described using Abstract Syntax Notation One (ASN.1 or ASN) syntax. This standard comprises one companion standard of the family of incident management standards centered around a base standard, IEEE Std 1512®-2000.<br />\n
          \t\t\t\t<br />\n
          Research, compile, analyze and consolidate information leading to the publication of a standards message set for Incident management specifically covering information transfer concerning Public Safety, comprised of Law Enforcement, Fire and Rescue, Emergency Medical Services, and other related functions and services.<br />\n
          Create a standard message set to reduce the duplication of messages among the various subsystems and a common set of message will help providers of services to interact more effectively.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Public Safety Traffic Incident Management Message Sets for Use By Emergency Management Centers"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135304 …}
    #channels: Doctrine\ORM\PersistentCollection {#135327 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135282 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135328 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135236 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135242
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135241
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1101769200 {#135240
      date: 2004-11-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1262991600 {#135239
      date: 2010-01-09 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.2"
    -bookCollection: ""
    -pageCount: 183
    -documents: Doctrine\ORM\PersistentCollection {#135234 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135227 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

Symfony Profiler

GET https://dev.normadoc.fr/products/ieee-1512-2006-ieee00003522-241701

Configuration Settings

Theme

Page Width

Components

Components

Render calls