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

Response
200 OK
IP
216.73.216.116
Profiled on
Token
9a04fa

Components

4 Twig Components
15 Render Count
23 ms Render Time
324.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		6 2.89ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		6 4.52ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		2 16.37ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.49ms

Render calls

ProductState App\Twig\Components\ProductState 324.0 MiB 1.92 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#92951
  +product: App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 324.0 MiB 0.49 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93122
  +product: App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 324.0 MiB 1.07 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93197
  +product: App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -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 324.0 MiB 0.21 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100191
    #id: 9396
    #code: "IEEE00002250"
    #attributes: Doctrine\ORM\PersistentCollection {#100174 …}
    #variants: Doctrine\ORM\PersistentCollection {#100171 …}
    #options: Doctrine\ORM\PersistentCollection {#100167 …}
    #associations: Doctrine\ORM\PersistentCollection {#100169 …}
    #createdAt: DateTime @1751038230 {#100199
      date: 2025-06-27 17:30:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100172
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100185 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100209
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 32593
        #name: "IEEE 1512.1:2003"
        #slug: "ieee-1512-1-2003-ieee00002250-241048"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised by IEEE Std 1512.1-2006 The exchange of vital traffic management data and data to support traffic management decisions, between the Traffic Management Center and other agencies involved in transportation-related events, through common incident management message sets, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard will be limited to the development of a comprehensive set of messages specific to Traffic Management. This work will be a functional partition of the Incident Management Base Standard (P1512) and will be developed as a separate project with a separate time schedule.<br />\n
          This standard will produce a standard set of all the message sets required for Incident Management that is unique to Traffic Management communications. These message sets will be 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 times.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Traffic 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 {#100182 …}
    #channels: Doctrine\ORM\PersistentCollection {#100176 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100180 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100178 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100192 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100159
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100198
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1052431200 {#100197
      date: 2003-05-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 132
    -documents: Doctrine\ORM\PersistentCollection {#100189 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100187 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#100245
  +product: App\Entity\Product\Product {#100191
    #id: 9396
    #code: "IEEE00002250"
    #attributes: Doctrine\ORM\PersistentCollection {#100174 …}
    #variants: Doctrine\ORM\PersistentCollection {#100171 …}
    #options: Doctrine\ORM\PersistentCollection {#100167 …}
    #associations: Doctrine\ORM\PersistentCollection {#100169 …}
    #createdAt: DateTime @1751038230 {#100199
      date: 2025-06-27 17:30:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100172
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100185 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100209
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 32593
        #name: "IEEE 1512.1:2003"
        #slug: "ieee-1512-1-2003-ieee00002250-241048"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised by IEEE Std 1512.1-2006 The exchange of vital traffic management data and data to support traffic management decisions, between the Traffic Management Center and other agencies involved in transportation-related events, through common incident management message sets, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard will be limited to the development of a comprehensive set of messages specific to Traffic Management. This work will be a functional partition of the Incident Management Base Standard (P1512) and will be developed as a separate project with a separate time schedule.<br />\n
          This standard will produce a standard set of all the message sets required for Incident Management that is unique to Traffic Management communications. These message sets will be 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 times.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Traffic 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 {#100182 …}
    #channels: Doctrine\ORM\PersistentCollection {#100176 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100180 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100178 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100192 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100159
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100198
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1052431200 {#100197
      date: 2003-05-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 132
    -documents: Doctrine\ORM\PersistentCollection {#100189 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100187 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 324.0 MiB 0.76 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100191
    #id: 9396
    #code: "IEEE00002250"
    #attributes: Doctrine\ORM\PersistentCollection {#100174 …}
    #variants: Doctrine\ORM\PersistentCollection {#100171 …}
    #options: Doctrine\ORM\PersistentCollection {#100167 …}
    #associations: Doctrine\ORM\PersistentCollection {#100169 …}
    #createdAt: DateTime @1751038230 {#100199
      date: 2025-06-27 17:30:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100172
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100185 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100209
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 32593
        #name: "IEEE 1512.1:2003"
        #slug: "ieee-1512-1-2003-ieee00002250-241048"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised by IEEE Std 1512.1-2006 The exchange of vital traffic management data and data to support traffic management decisions, between the Traffic Management Center and other agencies involved in transportation-related events, through common incident management message sets, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard will be limited to the development of a comprehensive set of messages specific to Traffic Management. This work will be a functional partition of the Incident Management Base Standard (P1512) and will be developed as a separate project with a separate time schedule.<br />\n
          This standard will produce a standard set of all the message sets required for Incident Management that is unique to Traffic Management communications. These message sets will be 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 times.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Traffic 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 {#100182 …}
    #channels: Doctrine\ORM\PersistentCollection {#100176 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100180 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100178 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100192 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100159
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100198
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1052431200 {#100197
      date: 2003-05-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 132
    -documents: Doctrine\ORM\PersistentCollection {#100189 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100187 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#100312
  +product: App\Entity\Product\Product {#100191
    #id: 9396
    #code: "IEEE00002250"
    #attributes: Doctrine\ORM\PersistentCollection {#100174 …}
    #variants: Doctrine\ORM\PersistentCollection {#100171 …}
    #options: Doctrine\ORM\PersistentCollection {#100167 …}
    #associations: Doctrine\ORM\PersistentCollection {#100169 …}
    #createdAt: DateTime @1751038230 {#100199
      date: 2025-06-27 17:30:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100172
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100185 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100209
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 32593
        #name: "IEEE 1512.1:2003"
        #slug: "ieee-1512-1-2003-ieee00002250-241048"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised by IEEE Std 1512.1-2006 The exchange of vital traffic management data and data to support traffic management decisions, between the Traffic Management Center and other agencies involved in transportation-related events, through common incident management message sets, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard will be limited to the development of a comprehensive set of messages specific to Traffic Management. This work will be a functional partition of the Incident Management Base Standard (P1512) and will be developed as a separate project with a separate time schedule.<br />\n
          This standard will produce a standard set of all the message sets required for Incident Management that is unique to Traffic Management communications. These message sets will be 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 times.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Traffic 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 {#100182 …}
    #channels: Doctrine\ORM\PersistentCollection {#100176 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100180 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100178 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100192 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100159
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100198
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1052431200 {#100197
      date: 2003-05-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 132
    -documents: Doctrine\ORM\PersistentCollection {#100189 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100187 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 324.0 MiB 0.19 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#106901
  +product: App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 324.0 MiB 0.73 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#106943
  +product: App\Entity\Product\Product {#7270
    #id: 10142
    #code: "IEEE00003715"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038849 {#7306
      date: 2025-06-27 17:40:49.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44: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 {#7270}
        #id: 35577
        #name: "IEEE 1512.1:2006"
        #slug: "ieee-1512-1-2006-ieee00003715-241794"
        #description: """
          Revision Standard - Inactive-Reserved.<br />\n
          Revision of IEEE Std 1512.1-2003. 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 a companion volume for IEEE Std 1512-2006, referred to here as the “Base Standard.” This standard specifies messages, data frames, and data elements for communicating information about traffic and infrastructure management in support of real-time interagency transportation-related incident management. The Base Standard specifies messages, data frames, and data elements to describe an incident and form the message infrastructure for communication involved in real-time interagency transportation related incident management. Refer to the Base Standard for specification of the scope of the combination of the Base Standard and companion volumes such as this one. Together, the Base Standard and companion volumes shall be referred to as the “IEEE 1512 Family of Standards.”<br />\n
          This standard is part of the IEEE 1512 Family of Standards. The purpose of that family of standards as a whole is presented in the Base Standard and will not be repeated here. The purpose of this standard is to take the real-world, available-information situation confronting the incident commander and the several involved agencies, and then support the exchange of that information among agencies, to make further information available to the incident commander and involved agencies, to best support them in managing the event. That calls for messages to communicate whatever information is available, often quite partial, among the several involved agencies, to accomplish four decision-support functions, corresponding to the five kinds of information exchange listed earlier in this clause:<br />\n
          a. Function 1: To disseminate information about current and future traffic flows in the transportation grid, including in particular impacts of an incident and particular route information, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          b. Function 2: To support the management of traffic to assist in the real-time interagency management of a transportation-related incident or event, including establishing reverse links and the use of priority/preemption technologies.<br />\n
          c. Function 3: To support the management of TMC assets and other assets, as necessary to manage traffic, to assist in the real-time interagency management of a transportation-related incident or event.<br />\n
          d. Function 4: To support the cleanup, repair, and replacement of damaged infrastructure, treating that operation as part of another incident, or as a separate incident.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Common Traffic 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 {#7490 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #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 @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#7291
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1162422000 {#7318
      date: 2006-11-02 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#7314
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 104
    -documents: Doctrine\ORM\PersistentCollection {#7535 …}
    -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 324.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100191
    #id: 9396
    #code: "IEEE00002250"
    #attributes: Doctrine\ORM\PersistentCollection {#100174 …}
    #variants: Doctrine\ORM\PersistentCollection {#100171 …}
    #options: Doctrine\ORM\PersistentCollection {#100167 …}
    #associations: Doctrine\ORM\PersistentCollection {#100169 …}
    #createdAt: DateTime @1751038230 {#100199
      date: 2025-06-27 17:30:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100172
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100185 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100209
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 32593
        #name: "IEEE 1512.1:2003"
        #slug: "ieee-1512-1-2003-ieee00002250-241048"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised by IEEE Std 1512.1-2006 The exchange of vital traffic management data and data to support traffic management decisions, between the Traffic Management Center and other agencies involved in transportation-related events, through common incident management message sets, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard will be limited to the development of a comprehensive set of messages specific to Traffic Management. This work will be a functional partition of the Incident Management Base Standard (P1512) and will be developed as a separate project with a separate time schedule.<br />\n
          This standard will produce a standard set of all the message sets required for Incident Management that is unique to Traffic Management communications. These message sets will be 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 times.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Traffic 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 {#100182 …}
    #channels: Doctrine\ORM\PersistentCollection {#100176 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100180 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100178 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100192 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100159
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100198
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1052431200 {#100197
      date: 2003-05-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 132
    -documents: Doctrine\ORM\PersistentCollection {#100189 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100187 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#107008
  +product: App\Entity\Product\Product {#100191
    #id: 9396
    #code: "IEEE00002250"
    #attributes: Doctrine\ORM\PersistentCollection {#100174 …}
    #variants: Doctrine\ORM\PersistentCollection {#100171 …}
    #options: Doctrine\ORM\PersistentCollection {#100167 …}
    #associations: Doctrine\ORM\PersistentCollection {#100169 …}
    #createdAt: DateTime @1751038230 {#100199
      date: 2025-06-27 17:30:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100172
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100185 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100209
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 32593
        #name: "IEEE 1512.1:2003"
        #slug: "ieee-1512-1-2003-ieee00002250-241048"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised by IEEE Std 1512.1-2006 The exchange of vital traffic management data and data to support traffic management decisions, between the Traffic Management Center and other agencies involved in transportation-related events, through common incident management message sets, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard will be limited to the development of a comprehensive set of messages specific to Traffic Management. This work will be a functional partition of the Incident Management Base Standard (P1512) and will be developed as a separate project with a separate time schedule.<br />\n
          This standard will produce a standard set of all the message sets required for Incident Management that is unique to Traffic Management communications. These message sets will be 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 times.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Traffic 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 {#100182 …}
    #channels: Doctrine\ORM\PersistentCollection {#100176 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100180 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100178 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100192 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100159
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100198
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1052431200 {#100197
      date: 2003-05-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 132
    -documents: Doctrine\ORM\PersistentCollection {#100189 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100187 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 324.0 MiB 0.63 ms
Input props 
[
  "product" => App\Entity\Product\Product {#100191
    #id: 9396
    #code: "IEEE00002250"
    #attributes: Doctrine\ORM\PersistentCollection {#100174 …}
    #variants: Doctrine\ORM\PersistentCollection {#100171 …}
    #options: Doctrine\ORM\PersistentCollection {#100167 …}
    #associations: Doctrine\ORM\PersistentCollection {#100169 …}
    #createdAt: DateTime @1751038230 {#100199
      date: 2025-06-27 17:30:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100172
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100185 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100209
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 32593
        #name: "IEEE 1512.1:2003"
        #slug: "ieee-1512-1-2003-ieee00002250-241048"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised by IEEE Std 1512.1-2006 The exchange of vital traffic management data and data to support traffic management decisions, between the Traffic Management Center and other agencies involved in transportation-related events, through common incident management message sets, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard will be limited to the development of a comprehensive set of messages specific to Traffic Management. This work will be a functional partition of the Incident Management Base Standard (P1512) and will be developed as a separate project with a separate time schedule.<br />\n
          This standard will produce a standard set of all the message sets required for Incident Management that is unique to Traffic Management communications. These message sets will be 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 times.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Traffic 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 {#100182 …}
    #channels: Doctrine\ORM\PersistentCollection {#100176 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100180 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100178 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100192 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100159
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100198
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1052431200 {#100197
      date: 2003-05-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 132
    -documents: Doctrine\ORM\PersistentCollection {#100189 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100187 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#107035
  +product: App\Entity\Product\Product {#100191
    #id: 9396
    #code: "IEEE00002250"
    #attributes: Doctrine\ORM\PersistentCollection {#100174 …}
    #variants: Doctrine\ORM\PersistentCollection {#100171 …}
    #options: Doctrine\ORM\PersistentCollection {#100167 …}
    #associations: Doctrine\ORM\PersistentCollection {#100169 …}
    #createdAt: DateTime @1751038230 {#100199
      date: 2025-06-27 17:30:30.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#100172
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#100185 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#100209
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#100191}
        #id: 32593
        #name: "IEEE 1512.1:2003"
        #slug: "ieee-1512-1-2003-ieee00002250-241048"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Revised by IEEE Std 1512.1-2006 The exchange of vital traffic management data and data to support traffic management decisions, between the Traffic Management Center and other agencies involved in transportation-related events, through common incident management message sets, is addressed in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard will be limited to the development of a comprehensive set of messages specific to Traffic Management. This work will be a functional partition of the Incident Management Base Standard (P1512) and will be developed as a separate project with a separate time schedule.<br />\n
          This standard will produce a standard set of all the message sets required for Incident Management that is unique to Traffic Management communications. These message sets will be 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 times.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Traffic 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 {#100182 …}
    #channels: Doctrine\ORM\PersistentCollection {#100176 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#100180 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#100178 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#100192 …}
    -apiLastModifiedAt: DateTime @1754517600 {#100159
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#100198
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1052431200 {#100197
      date: 2003-05-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1512.1"
    -bookCollection: ""
    -pageCount: 132
    -documents: Doctrine\ORM\PersistentCollection {#100189 …}
    -favorites: Doctrine\ORM\PersistentCollection {#100187 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 324.0 MiB 9.19 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128498
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#128481 …}
    #variants: Doctrine\ORM\PersistentCollection {#128479 …}
    #options: Doctrine\ORM\PersistentCollection {#128474 …}
    #associations: Doctrine\ORM\PersistentCollection {#128476 …}
    #createdAt: DateTime @1751038221 {#128471
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#128506
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128492 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128615
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128498}
        #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 {#128490 …}
    #channels: Doctrine\ORM\PersistentCollection {#128483 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128487 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128485 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128500 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128457
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128505
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#128464
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#128477
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#128496 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128494 …}
  }
  "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 {#128532
  +product: App\Entity\Product\Product {#128498
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#128481 …}
    #variants: Doctrine\ORM\PersistentCollection {#128479 …}
    #options: Doctrine\ORM\PersistentCollection {#128474 …}
    #associations: Doctrine\ORM\PersistentCollection {#128476 …}
    #createdAt: DateTime @1751038221 {#128471
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#128506
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128492 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128615
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128498}
        #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 {#128490 …}
    #channels: Doctrine\ORM\PersistentCollection {#128483 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128487 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128485 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128500 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128457
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128505
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#128464
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#128477
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#128496 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128494 …}
  }
  +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 324.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128498
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#128481 …}
    #variants: Doctrine\ORM\PersistentCollection {#128479 …}
    #options: Doctrine\ORM\PersistentCollection {#128474 …}
    #associations: Doctrine\ORM\PersistentCollection {#128476 …}
    #createdAt: DateTime @1751038221 {#128471
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#128506
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128492 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128615
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128498}
        #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 {#128490 …}
    #channels: Doctrine\ORM\PersistentCollection {#128483 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128487 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128485 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128500 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128457
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128505
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#128464
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#128477
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#128496 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128494 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#128619
  +product: App\Entity\Product\Product {#128498
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#128481 …}
    #variants: Doctrine\ORM\PersistentCollection {#128479 …}
    #options: Doctrine\ORM\PersistentCollection {#128474 …}
    #associations: Doctrine\ORM\PersistentCollection {#128476 …}
    #createdAt: DateTime @1751038221 {#128471
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#128506
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128492 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128615
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128498}
        #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 {#128490 …}
    #channels: Doctrine\ORM\PersistentCollection {#128483 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128487 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128485 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128500 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128457
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128505
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#128464
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#128477
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#128496 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128494 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 324.0 MiB 0.72 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128498
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#128481 …}
    #variants: Doctrine\ORM\PersistentCollection {#128479 …}
    #options: Doctrine\ORM\PersistentCollection {#128474 …}
    #associations: Doctrine\ORM\PersistentCollection {#128476 …}
    #createdAt: DateTime @1751038221 {#128471
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#128506
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128492 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128615
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128498}
        #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 {#128490 …}
    #channels: Doctrine\ORM\PersistentCollection {#128483 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128487 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128485 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128500 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128457
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128505
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#128464
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#128477
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#128496 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128494 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#128697
  +product: App\Entity\Product\Product {#128498
    #id: 9385
    #code: "IEEE00002226"
    #attributes: Doctrine\ORM\PersistentCollection {#128481 …}
    #variants: Doctrine\ORM\PersistentCollection {#128479 …}
    #options: Doctrine\ORM\PersistentCollection {#128474 …}
    #associations: Doctrine\ORM\PersistentCollection {#128476 …}
    #createdAt: DateTime @1751038221 {#128471
      date: 2025-06-27 17:30:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#128506
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128492 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128615
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128498}
        #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 {#128490 …}
    #channels: Doctrine\ORM\PersistentCollection {#128483 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128487 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128485 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128500 …}
    -apiLastModifiedAt: DateTime @1743289200 {#128457
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#128505
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @963439200 {#128464
      date: 2000-07-13 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1139180400 {#128477
      date: 2006-02-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1488"
    -bookCollection: ""
    -pageCount: 44
    -documents: Doctrine\ORM\PersistentCollection {#128496 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128494 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 324.0 MiB 7.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128465
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#128549 …}
    #variants: Doctrine\ORM\PersistentCollection {#128548 …}
    #options: Doctrine\ORM\PersistentCollection {#128543 …}
    #associations: Doctrine\ORM\PersistentCollection {#128545 …}
    #createdAt: DateTime @1751038775 {#128472
      date: 2025-06-27 17:39:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128470
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128546 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128814
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128465}
        #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 {#128531 …}
    #channels: Doctrine\ORM\PersistentCollection {#128554 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128509 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128555 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128463 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128469
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#128468
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#128467
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#128466
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#128461 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128454 …}
  }
  "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 {#128772
  +product: App\Entity\Product\Product {#128465
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#128549 …}
    #variants: Doctrine\ORM\PersistentCollection {#128548 …}
    #options: Doctrine\ORM\PersistentCollection {#128543 …}
    #associations: Doctrine\ORM\PersistentCollection {#128545 …}
    #createdAt: DateTime @1751038775 {#128472
      date: 2025-06-27 17:39:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128470
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128546 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128814
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128465}
        #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 {#128531 …}
    #channels: Doctrine\ORM\PersistentCollection {#128554 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128509 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128555 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128463 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128469
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#128468
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#128467
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#128466
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#128461 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128454 …}
  }
  +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 324.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128465
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#128549 …}
    #variants: Doctrine\ORM\PersistentCollection {#128548 …}
    #options: Doctrine\ORM\PersistentCollection {#128543 …}
    #associations: Doctrine\ORM\PersistentCollection {#128545 …}
    #createdAt: DateTime @1751038775 {#128472
      date: 2025-06-27 17:39:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128470
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128546 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128814
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128465}
        #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 {#128531 …}
    #channels: Doctrine\ORM\PersistentCollection {#128554 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128509 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128555 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128463 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128469
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#128468
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#128467
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#128466
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#128461 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128454 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#128828
  +product: App\Entity\Product\Product {#128465
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#128549 …}
    #variants: Doctrine\ORM\PersistentCollection {#128548 …}
    #options: Doctrine\ORM\PersistentCollection {#128543 …}
    #associations: Doctrine\ORM\PersistentCollection {#128545 …}
    #createdAt: DateTime @1751038775 {#128472
      date: 2025-06-27 17:39:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128470
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128546 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128814
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128465}
        #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 {#128531 …}
    #channels: Doctrine\ORM\PersistentCollection {#128554 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128509 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128555 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128463 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128469
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#128468
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#128467
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#128466
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#128461 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128454 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 324.0 MiB 0.62 ms
Input props 
[
  "product" => App\Entity\Product\Product {#128465
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#128549 …}
    #variants: Doctrine\ORM\PersistentCollection {#128548 …}
    #options: Doctrine\ORM\PersistentCollection {#128543 …}
    #associations: Doctrine\ORM\PersistentCollection {#128545 …}
    #createdAt: DateTime @1751038775 {#128472
      date: 2025-06-27 17:39:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128470
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128546 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128814
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128465}
        #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 {#128531 …}
    #channels: Doctrine\ORM\PersistentCollection {#128554 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128509 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128555 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128463 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128469
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#128468
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#128467
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#128466
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#128461 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128454 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#128902
  +product: App\Entity\Product\Product {#128465
    #id: 10049
    #code: "IEEE00003522"
    #attributes: Doctrine\ORM\PersistentCollection {#128549 …}
    #variants: Doctrine\ORM\PersistentCollection {#128548 …}
    #options: Doctrine\ORM\PersistentCollection {#128543 …}
    #associations: Doctrine\ORM\PersistentCollection {#128545 …}
    #createdAt: DateTime @1751038775 {#128472
      date: 2025-06-27 17:39:35.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#128470
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#128546 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#128814
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#128465}
        #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 {#128531 …}
    #channels: Doctrine\ORM\PersistentCollection {#128554 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7274 …}
    #reviews: Doctrine\ORM\PersistentCollection {#128509 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#128555 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#128463 …}
    -apiLastModifiedAt: DateTime @1754517600 {#128469
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1581462000 {#128468
      date: 2020-02-12 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1154988000 {#128467
      date: 2006-08-08 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1573081200 {#128466
      date: 2019-11-07 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1512"
    -bookCollection: ""
    -pageCount: 547
    -documents: Doctrine\ORM\PersistentCollection {#128461 …}
    -favorites: Doctrine\ORM\PersistentCollection {#128454 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}