GET https://dev.normadoc.fr/_fragment?_path=_format%3Dhtml%26_locale%3Den_US%26_controller%3DSylius%255CPayPalPlugin%255CController%255CPayPalButtonsController%253A…

Response
200 OK
IP
216.73.216.2
Profiled on
Token
98ca1e

Components

4 Twig Components
8 Render Count
15 ms Render Time
112.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		3 2.47ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		3 2.86ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.50ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 9.92ms

Render calls

ProductState App\Twig\Components\ProductState 94.0 MiB 1.98 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#94943
  +product: App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 94.0 MiB 0.50 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#95114
  +product: App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 94.0 MiB 1.08 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#95189
  +product: App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 94.0 MiB 0.30 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#102146
  +product: App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 94.0 MiB 1.04 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#102230
  +product: App\Entity\Product\Product {#7519
    #id: 11519
    #code: "IEEE00006264"
    #attributes: Doctrine\ORM\PersistentCollection {#8208 …}
    #variants: Doctrine\ORM\PersistentCollection {#8290 …}
    #options: Doctrine\ORM\PersistentCollection {#8629 …}
    #associations: Doctrine\ORM\PersistentCollection {#8586 …}
    #createdAt: DateTime @1751039758 {#7536
      date: 2025-06-27 17:55:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7535
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#8628 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#8613
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7519}
        #id: 41085
        #name: "IEEE 2660.1:2020"
        #slug: "ieee-2660-1-2020-ieee00006264-243171"
        #description: """
          New IEEE Standard - Active.<br />\n
          The recommended practices to solve the interface problem when applying industrial agents, namely, integrating intelligent software agents with low-level automation devices in the context of cyber-physical systems, are described in this recommended practice. In particular, a method to select the best interfacing practice for a given application scenario, defined by the user, from a set of available interfacing templates and technologies, aiming to improve reuse, consistency, and transparency in the integration of industrial agents and low-level control functions, is defined.<br />\n
          \t\t\t\t<br />\n
          This recommended practice describes integrating and deploying the Multi-agent Systems (MAS) technology in industrial environments for use in building the intelligent decision-making layer on top of legacy industrial control platforms. The integration of software agents with the low-level real-time control systems, mainly based on the Programmable Logic Controllers (PLCs) running the IEC 61131-3 control programs (forming in this manner a new component known as industrial agents) are also identified. In addition, the integration of software agents with the control applications based on IEC 61499 standard or executed on embedded controllers is described. This recommended practice supports and helps the engineers leverage the best practices of developing industrial agents for specific automation control problems and given application fields. Therefore, corresponding rules, guidelines and design patterns are provided.<br />\n
          The recommended practice intends to solve the interface problem when applying industrial agents, namely integrating software agents with automation control level in the context of cyber-physical systems (CPS) (Lee [B11]). The idea is to provide a description of a collection of best practices for the integration process according to the automation use cases and automation control level, aiming to standardize the interface process to allow the reuse and transparency
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Recommended Practice for Industrial Agents: Integration of Software Agents and Low-Level Automation Functions"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7944 …}
    #channels: Doctrine\ORM\PersistentCollection {#8105 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#8067 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#8119 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7747 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7530
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1613343600 {#7496
      date: 2021-02-15 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1611874800 {#7531
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1611874800 {#7521
      date: 2021-01-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "2660.1"
    -bookCollection: ""
    -pageCount: 43
    -documents: Doctrine\ORM\PersistentCollection {#7787 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7929 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 112.0 MiB 9.92 ms
Input props 
[
  "product" => App\Entity\Product\Product {#123635
    #id: 11500
    #code: "IEEE00006226"
    #attributes: Doctrine\ORM\PersistentCollection {#123640 …}
    #variants: Doctrine\ORM\PersistentCollection {#123638 …}
    #options: Doctrine\ORM\PersistentCollection {#123633 …}
    #associations: Doctrine\ORM\PersistentCollection {#123636 …}
    #createdAt: DateTime @1751039746 {#123629
      date: 2025-06-27 17:55:46.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#123664
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123651 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123753
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123635}
        #id: 41009
        #name: "IEEE 2413:2019"
        #slug: "ieee-2413-2019-ieee00006226-243152"
        #description: """
          New IEEE Standard - Active.<br />\n
          An architecture framework description for the Internet of Things (IoT) which conforms to the international standard ISO/IEC/IEEE 42010:2011 is defined. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). A conceptual basis for the notion of things in the IoT is provided and the shared concerns as a collection of architecture viewpoints is elaborated to form the body of the framework description.<br />\n
          \t\t\t\t<br />\n
          This standard defines an architecture framework description for the Internet of Things (IoT). The architecture ontology and methodology of the framework architecture conforms to the international standard ISO/IEC/IEEE 42010:2011. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). This standard provides a conceptual basis for the notion of things in the IoT and then elaborates the shared concerns as a collection of architecture viewpoints that form the body of the framework description.<br />\n
          The IoT is predicted to become one of the most significant drivers of growth in many technology markets. The architectural framework defined in this standard will promote cross-domain interaction, aid system interoperability and functional compatibility, and further fuel the growth of the IoT market. The standard will address stakeholder concerns to help them build a connected world that can interoperate while meeting both the needs of enterprises and society for trustworthiness of IoT systems. The adoption of a unified approach to the development of IoT systems will reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world.<br />\n
          The motivation for the standard as informed by stakeholder concerns and desired outcome is to build stakeholder confidence through the following:<br />\n
          a) Provide a framework for vendors to build conformant, interoperable, secure, IoT systems that can span multiple application domains.<br />\n
          b) Provide a framework for buyers to make comparisons and assessments of such systems.<br />\n
          c) Provide a framework for system designers to accelerate design, implementation, and deployment processes of such systems.<br />\n
          Business goals trigger and frame system concerns and thus the system architecture. In fact, the U.S. National Institute of Standards and Technology (NIST) CPS Public Working Group generated a list of concerns for cyber-physical systems (CPS) as listed in the Framework for Cyber-Physical Systems (NIST SP 1500-201). The framework includes a business aspect that defines “concerns about enterprise, time to market, environment, regulation, cost, etc.” The concerns in the present document as derived from the NIST concerns incorporate business elements that acknowledge that systems need to be integrated into business processes to successfully meet the business goals. There is no common approach to addressing the business viewpoint and, therefore, this standard does not include a business architecture viewpoint. The relevance of the business goal of value creation and the desire for differentiable value propositions in the market are implied throughout the standard. Business goals are important for any viable system architecture.<br />\n
          This document provides both a normative part (Clause 6) with the architecture viewpoints intended to be the basis for describing the architecture for an IoT system, and an informative part (Clause 7) with examples of architecture descriptions associated with architecture views that conform to the architecture viewpoints
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for an Architectural Framework for the Internet of Things (IoT)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123649 …}
    #channels: Doctrine\ORM\PersistentCollection {#123642 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123646 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123615
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1585519200 {#123663
      date: 2020-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1583794800 {#123622
      date: 2020-03-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2413"
    -bookCollection: ""
    -pageCount: 269
    -documents: Doctrine\ORM\PersistentCollection {#123655 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123653 …}
  }
  "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 {#123708
  +product: App\Entity\Product\Product {#123635
    #id: 11500
    #code: "IEEE00006226"
    #attributes: Doctrine\ORM\PersistentCollection {#123640 …}
    #variants: Doctrine\ORM\PersistentCollection {#123638 …}
    #options: Doctrine\ORM\PersistentCollection {#123633 …}
    #associations: Doctrine\ORM\PersistentCollection {#123636 …}
    #createdAt: DateTime @1751039746 {#123629
      date: 2025-06-27 17:55:46.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#123664
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123651 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123753
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123635}
        #id: 41009
        #name: "IEEE 2413:2019"
        #slug: "ieee-2413-2019-ieee00006226-243152"
        #description: """
          New IEEE Standard - Active.<br />\n
          An architecture framework description for the Internet of Things (IoT) which conforms to the international standard ISO/IEC/IEEE 42010:2011 is defined. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). A conceptual basis for the notion of things in the IoT is provided and the shared concerns as a collection of architecture viewpoints is elaborated to form the body of the framework description.<br />\n
          \t\t\t\t<br />\n
          This standard defines an architecture framework description for the Internet of Things (IoT). The architecture ontology and methodology of the framework architecture conforms to the international standard ISO/IEC/IEEE 42010:2011. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). This standard provides a conceptual basis for the notion of things in the IoT and then elaborates the shared concerns as a collection of architecture viewpoints that form the body of the framework description.<br />\n
          The IoT is predicted to become one of the most significant drivers of growth in many technology markets. The architectural framework defined in this standard will promote cross-domain interaction, aid system interoperability and functional compatibility, and further fuel the growth of the IoT market. The standard will address stakeholder concerns to help them build a connected world that can interoperate while meeting both the needs of enterprises and society for trustworthiness of IoT systems. The adoption of a unified approach to the development of IoT systems will reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world.<br />\n
          The motivation for the standard as informed by stakeholder concerns and desired outcome is to build stakeholder confidence through the following:<br />\n
          a) Provide a framework for vendors to build conformant, interoperable, secure, IoT systems that can span multiple application domains.<br />\n
          b) Provide a framework for buyers to make comparisons and assessments of such systems.<br />\n
          c) Provide a framework for system designers to accelerate design, implementation, and deployment processes of such systems.<br />\n
          Business goals trigger and frame system concerns and thus the system architecture. In fact, the U.S. National Institute of Standards and Technology (NIST) CPS Public Working Group generated a list of concerns for cyber-physical systems (CPS) as listed in the Framework for Cyber-Physical Systems (NIST SP 1500-201). The framework includes a business aspect that defines “concerns about enterprise, time to market, environment, regulation, cost, etc.” The concerns in the present document as derived from the NIST concerns incorporate business elements that acknowledge that systems need to be integrated into business processes to successfully meet the business goals. There is no common approach to addressing the business viewpoint and, therefore, this standard does not include a business architecture viewpoint. The relevance of the business goal of value creation and the desire for differentiable value propositions in the market are implied throughout the standard. Business goals are important for any viable system architecture.<br />\n
          This document provides both a normative part (Clause 6) with the architecture viewpoints intended to be the basis for describing the architecture for an IoT system, and an informative part (Clause 7) with examples of architecture descriptions associated with architecture views that conform to the architecture viewpoints
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for an Architectural Framework for the Internet of Things (IoT)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123649 …}
    #channels: Doctrine\ORM\PersistentCollection {#123642 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123646 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123615
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1585519200 {#123663
      date: 2020-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1583794800 {#123622
      date: 2020-03-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2413"
    -bookCollection: ""
    -pageCount: 269
    -documents: Doctrine\ORM\PersistentCollection {#123655 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123653 …}
  }
  +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 112.0 MiB 0.19 ms
Input props 
[
  "product" => App\Entity\Product\Product {#123635
    #id: 11500
    #code: "IEEE00006226"
    #attributes: Doctrine\ORM\PersistentCollection {#123640 …}
    #variants: Doctrine\ORM\PersistentCollection {#123638 …}
    #options: Doctrine\ORM\PersistentCollection {#123633 …}
    #associations: Doctrine\ORM\PersistentCollection {#123636 …}
    #createdAt: DateTime @1751039746 {#123629
      date: 2025-06-27 17:55:46.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#123664
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123651 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123753
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123635}
        #id: 41009
        #name: "IEEE 2413:2019"
        #slug: "ieee-2413-2019-ieee00006226-243152"
        #description: """
          New IEEE Standard - Active.<br />\n
          An architecture framework description for the Internet of Things (IoT) which conforms to the international standard ISO/IEC/IEEE 42010:2011 is defined. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). A conceptual basis for the notion of things in the IoT is provided and the shared concerns as a collection of architecture viewpoints is elaborated to form the body of the framework description.<br />\n
          \t\t\t\t<br />\n
          This standard defines an architecture framework description for the Internet of Things (IoT). The architecture ontology and methodology of the framework architecture conforms to the international standard ISO/IEC/IEEE 42010:2011. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). This standard provides a conceptual basis for the notion of things in the IoT and then elaborates the shared concerns as a collection of architecture viewpoints that form the body of the framework description.<br />\n
          The IoT is predicted to become one of the most significant drivers of growth in many technology markets. The architectural framework defined in this standard will promote cross-domain interaction, aid system interoperability and functional compatibility, and further fuel the growth of the IoT market. The standard will address stakeholder concerns to help them build a connected world that can interoperate while meeting both the needs of enterprises and society for trustworthiness of IoT systems. The adoption of a unified approach to the development of IoT systems will reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world.<br />\n
          The motivation for the standard as informed by stakeholder concerns and desired outcome is to build stakeholder confidence through the following:<br />\n
          a) Provide a framework for vendors to build conformant, interoperable, secure, IoT systems that can span multiple application domains.<br />\n
          b) Provide a framework for buyers to make comparisons and assessments of such systems.<br />\n
          c) Provide a framework for system designers to accelerate design, implementation, and deployment processes of such systems.<br />\n
          Business goals trigger and frame system concerns and thus the system architecture. In fact, the U.S. National Institute of Standards and Technology (NIST) CPS Public Working Group generated a list of concerns for cyber-physical systems (CPS) as listed in the Framework for Cyber-Physical Systems (NIST SP 1500-201). The framework includes a business aspect that defines “concerns about enterprise, time to market, environment, regulation, cost, etc.” The concerns in the present document as derived from the NIST concerns incorporate business elements that acknowledge that systems need to be integrated into business processes to successfully meet the business goals. There is no common approach to addressing the business viewpoint and, therefore, this standard does not include a business architecture viewpoint. The relevance of the business goal of value creation and the desire for differentiable value propositions in the market are implied throughout the standard. Business goals are important for any viable system architecture.<br />\n
          This document provides both a normative part (Clause 6) with the architecture viewpoints intended to be the basis for describing the architecture for an IoT system, and an informative part (Clause 7) with examples of architecture descriptions associated with architecture views that conform to the architecture viewpoints
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for an Architectural Framework for the Internet of Things (IoT)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123649 …}
    #channels: Doctrine\ORM\PersistentCollection {#123642 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123646 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123615
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1585519200 {#123663
      date: 2020-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1583794800 {#123622
      date: 2020-03-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2413"
    -bookCollection: ""
    -pageCount: 269
    -documents: Doctrine\ORM\PersistentCollection {#123655 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123653 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#123755
  +product: App\Entity\Product\Product {#123635
    #id: 11500
    #code: "IEEE00006226"
    #attributes: Doctrine\ORM\PersistentCollection {#123640 …}
    #variants: Doctrine\ORM\PersistentCollection {#123638 …}
    #options: Doctrine\ORM\PersistentCollection {#123633 …}
    #associations: Doctrine\ORM\PersistentCollection {#123636 …}
    #createdAt: DateTime @1751039746 {#123629
      date: 2025-06-27 17:55:46.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#123664
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123651 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123753
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123635}
        #id: 41009
        #name: "IEEE 2413:2019"
        #slug: "ieee-2413-2019-ieee00006226-243152"
        #description: """
          New IEEE Standard - Active.<br />\n
          An architecture framework description for the Internet of Things (IoT) which conforms to the international standard ISO/IEC/IEEE 42010:2011 is defined. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). A conceptual basis for the notion of things in the IoT is provided and the shared concerns as a collection of architecture viewpoints is elaborated to form the body of the framework description.<br />\n
          \t\t\t\t<br />\n
          This standard defines an architecture framework description for the Internet of Things (IoT). The architecture ontology and methodology of the framework architecture conforms to the international standard ISO/IEC/IEEE 42010:2011. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). This standard provides a conceptual basis for the notion of things in the IoT and then elaborates the shared concerns as a collection of architecture viewpoints that form the body of the framework description.<br />\n
          The IoT is predicted to become one of the most significant drivers of growth in many technology markets. The architectural framework defined in this standard will promote cross-domain interaction, aid system interoperability and functional compatibility, and further fuel the growth of the IoT market. The standard will address stakeholder concerns to help them build a connected world that can interoperate while meeting both the needs of enterprises and society for trustworthiness of IoT systems. The adoption of a unified approach to the development of IoT systems will reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world.<br />\n
          The motivation for the standard as informed by stakeholder concerns and desired outcome is to build stakeholder confidence through the following:<br />\n
          a) Provide a framework for vendors to build conformant, interoperable, secure, IoT systems that can span multiple application domains.<br />\n
          b) Provide a framework for buyers to make comparisons and assessments of such systems.<br />\n
          c) Provide a framework for system designers to accelerate design, implementation, and deployment processes of such systems.<br />\n
          Business goals trigger and frame system concerns and thus the system architecture. In fact, the U.S. National Institute of Standards and Technology (NIST) CPS Public Working Group generated a list of concerns for cyber-physical systems (CPS) as listed in the Framework for Cyber-Physical Systems (NIST SP 1500-201). The framework includes a business aspect that defines “concerns about enterprise, time to market, environment, regulation, cost, etc.” The concerns in the present document as derived from the NIST concerns incorporate business elements that acknowledge that systems need to be integrated into business processes to successfully meet the business goals. There is no common approach to addressing the business viewpoint and, therefore, this standard does not include a business architecture viewpoint. The relevance of the business goal of value creation and the desire for differentiable value propositions in the market are implied throughout the standard. Business goals are important for any viable system architecture.<br />\n
          This document provides both a normative part (Clause 6) with the architecture viewpoints intended to be the basis for describing the architecture for an IoT system, and an informative part (Clause 7) with examples of architecture descriptions associated with architecture views that conform to the architecture viewpoints
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for an Architectural Framework for the Internet of Things (IoT)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123649 …}
    #channels: Doctrine\ORM\PersistentCollection {#123642 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123646 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123615
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1585519200 {#123663
      date: 2020-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1583794800 {#123622
      date: 2020-03-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2413"
    -bookCollection: ""
    -pageCount: 269
    -documents: Doctrine\ORM\PersistentCollection {#123655 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123653 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 112.0 MiB 0.74 ms
Input props 
[
  "product" => App\Entity\Product\Product {#123635
    #id: 11500
    #code: "IEEE00006226"
    #attributes: Doctrine\ORM\PersistentCollection {#123640 …}
    #variants: Doctrine\ORM\PersistentCollection {#123638 …}
    #options: Doctrine\ORM\PersistentCollection {#123633 …}
    #associations: Doctrine\ORM\PersistentCollection {#123636 …}
    #createdAt: DateTime @1751039746 {#123629
      date: 2025-06-27 17:55:46.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#123664
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123651 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123753
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123635}
        #id: 41009
        #name: "IEEE 2413:2019"
        #slug: "ieee-2413-2019-ieee00006226-243152"
        #description: """
          New IEEE Standard - Active.<br />\n
          An architecture framework description for the Internet of Things (IoT) which conforms to the international standard ISO/IEC/IEEE 42010:2011 is defined. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). A conceptual basis for the notion of things in the IoT is provided and the shared concerns as a collection of architecture viewpoints is elaborated to form the body of the framework description.<br />\n
          \t\t\t\t<br />\n
          This standard defines an architecture framework description for the Internet of Things (IoT). The architecture ontology and methodology of the framework architecture conforms to the international standard ISO/IEC/IEEE 42010:2011. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). This standard provides a conceptual basis for the notion of things in the IoT and then elaborates the shared concerns as a collection of architecture viewpoints that form the body of the framework description.<br />\n
          The IoT is predicted to become one of the most significant drivers of growth in many technology markets. The architectural framework defined in this standard will promote cross-domain interaction, aid system interoperability and functional compatibility, and further fuel the growth of the IoT market. The standard will address stakeholder concerns to help them build a connected world that can interoperate while meeting both the needs of enterprises and society for trustworthiness of IoT systems. The adoption of a unified approach to the development of IoT systems will reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world.<br />\n
          The motivation for the standard as informed by stakeholder concerns and desired outcome is to build stakeholder confidence through the following:<br />\n
          a) Provide a framework for vendors to build conformant, interoperable, secure, IoT systems that can span multiple application domains.<br />\n
          b) Provide a framework for buyers to make comparisons and assessments of such systems.<br />\n
          c) Provide a framework for system designers to accelerate design, implementation, and deployment processes of such systems.<br />\n
          Business goals trigger and frame system concerns and thus the system architecture. In fact, the U.S. National Institute of Standards and Technology (NIST) CPS Public Working Group generated a list of concerns for cyber-physical systems (CPS) as listed in the Framework for Cyber-Physical Systems (NIST SP 1500-201). The framework includes a business aspect that defines “concerns about enterprise, time to market, environment, regulation, cost, etc.” The concerns in the present document as derived from the NIST concerns incorporate business elements that acknowledge that systems need to be integrated into business processes to successfully meet the business goals. There is no common approach to addressing the business viewpoint and, therefore, this standard does not include a business architecture viewpoint. The relevance of the business goal of value creation and the desire for differentiable value propositions in the market are implied throughout the standard. Business goals are important for any viable system architecture.<br />\n
          This document provides both a normative part (Clause 6) with the architecture viewpoints intended to be the basis for describing the architecture for an IoT system, and an informative part (Clause 7) with examples of architecture descriptions associated with architecture views that conform to the architecture viewpoints
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for an Architectural Framework for the Internet of Things (IoT)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123649 …}
    #channels: Doctrine\ORM\PersistentCollection {#123642 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123646 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123615
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1585519200 {#123663
      date: 2020-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1583794800 {#123622
      date: 2020-03-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2413"
    -bookCollection: ""
    -pageCount: 269
    -documents: Doctrine\ORM\PersistentCollection {#123655 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123653 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#123832
  +product: App\Entity\Product\Product {#123635
    #id: 11500
    #code: "IEEE00006226"
    #attributes: Doctrine\ORM\PersistentCollection {#123640 …}
    #variants: Doctrine\ORM\PersistentCollection {#123638 …}
    #options: Doctrine\ORM\PersistentCollection {#123633 …}
    #associations: Doctrine\ORM\PersistentCollection {#123636 …}
    #createdAt: DateTime @1751039746 {#123629
      date: 2025-06-27 17:55:46.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#123664
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#123651 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#123753
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#123635}
        #id: 41009
        #name: "IEEE 2413:2019"
        #slug: "ieee-2413-2019-ieee00006226-243152"
        #description: """
          New IEEE Standard - Active.<br />\n
          An architecture framework description for the Internet of Things (IoT) which conforms to the international standard ISO/IEC/IEEE 42010:2011 is defined. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). A conceptual basis for the notion of things in the IoT is provided and the shared concerns as a collection of architecture viewpoints is elaborated to form the body of the framework description.<br />\n
          \t\t\t\t<br />\n
          This standard defines an architecture framework description for the Internet of Things (IoT). The architecture ontology and methodology of the framework architecture conforms to the international standard ISO/IEC/IEEE 42010:2011. The architecture framework description is motivated by concerns commonly shared by IoT system stakeholders across multiple domains (transportation, healthcare, Smart Grid, etc.). This standard provides a conceptual basis for the notion of things in the IoT and then elaborates the shared concerns as a collection of architecture viewpoints that form the body of the framework description.<br />\n
          The IoT is predicted to become one of the most significant drivers of growth in many technology markets. The architectural framework defined in this standard will promote cross-domain interaction, aid system interoperability and functional compatibility, and further fuel the growth of the IoT market. The standard will address stakeholder concerns to help them build a connected world that can interoperate while meeting both the needs of enterprises and society for trustworthiness of IoT systems. The adoption of a unified approach to the development of IoT systems will reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world.<br />\n
          The motivation for the standard as informed by stakeholder concerns and desired outcome is to build stakeholder confidence through the following:<br />\n
          a) Provide a framework for vendors to build conformant, interoperable, secure, IoT systems that can span multiple application domains.<br />\n
          b) Provide a framework for buyers to make comparisons and assessments of such systems.<br />\n
          c) Provide a framework for system designers to accelerate design, implementation, and deployment processes of such systems.<br />\n
          Business goals trigger and frame system concerns and thus the system architecture. In fact, the U.S. National Institute of Standards and Technology (NIST) CPS Public Working Group generated a list of concerns for cyber-physical systems (CPS) as listed in the Framework for Cyber-Physical Systems (NIST SP 1500-201). The framework includes a business aspect that defines “concerns about enterprise, time to market, environment, regulation, cost, etc.” The concerns in the present document as derived from the NIST concerns incorporate business elements that acknowledge that systems need to be integrated into business processes to successfully meet the business goals. There is no common approach to addressing the business viewpoint and, therefore, this standard does not include a business architecture viewpoint. The relevance of the business goal of value creation and the desire for differentiable value propositions in the market are implied throughout the standard. Business goals are important for any viable system architecture.<br />\n
          This document provides both a normative part (Clause 6) with the architecture viewpoints intended to be the basis for describing the architecture for an IoT system, and an informative part (Clause 7) with examples of architecture descriptions associated with architecture views that conform to the architecture viewpoints
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for an Architectural Framework for the Internet of Things (IoT)"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#123649 …}
    #channels: Doctrine\ORM\PersistentCollection {#123642 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7518 …}
    #reviews: Doctrine\ORM\PersistentCollection {#123646 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#123644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7682 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#123656 …}
    -apiLastModifiedAt: DateTime @1754517600 {#123615
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1585519200 {#123663
      date: 2020-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1583794800 {#123622
      date: 2020-03-10 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2413"
    -bookCollection: ""
    -pageCount: 269
    -documents: Doctrine\ORM\PersistentCollection {#123655 …}
    -favorites: Doctrine\ORM\PersistentCollection {#123653 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}