Symfony Profiler

[
  "backLabel" => "03 : Services. Company organization, management and quality. Administration. Transport. Sociology"
  "backUrl" => "/taxons/main/ics-2277/03-services-company-organization-management-and-quality-administration-transport-sociology-4280"
  "paddingClasses" => "p-2 px-lg-5 py-lg-0"
  "searchPlaceholder" => "sylius.ui.search"
  "showSearch" => "true"
  "title" => "03.080 : Services"
]

App\Twig\Components\PageBanner {#94167
  +supTitle: null
  +title: "03.080 : Services"
  +subTitle: null
  +backUrl: "/taxons/main/ics-2277/03-services-company-organization-management-and-quality-administration-transport-sociology-4280"
  +backLabel: "03 : Services. Company organization, management and quality. Administration. Transport. Sociology"
  +customClasses: null
  +backgroundType: null
  +centered: true
  +showSearch: true
  +searchPlaceholder: "sylius.ui.search"
  +searchValue: null
  +paddingClasses: "p-2 px-lg-5 py-lg-0"
}

[
  "url" => "/taxons/main/ics-2277/03-services-company-organization-management-and-quality-administration-transport-sociology-4280"
  "label" => "03 : Services. Company organization, management and quality. Administration. Transport. Sociology"
]

App\Twig\Components\BackButton {#94258
  +label: "03 : Services. Company organization, management and quality. Administration. Transport. Sociology"
  +url: "/taxons/main/ics-2277/03-services-company-organization-management-and-quality-administration-transport-sociology-4280"
}

[
  "items" => Doctrine\ORM\PersistentCollection {#8719
    #collection: Doctrine\Common\Collections\ArrayCollection {#8665 …}
    #initialized: true
    -snapshot: [ …5]
    -owner: App\Entity\Taxonomy\Taxon {#8648 …}
    -association: [ …16]
    -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
    -backRefFieldName: "parent"
    -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#118181 …}
    -isDirty: false
  }
  "responsiveItemsPerRow" => [
    "mobile" => 2
    "tablet" => 4
    "desktop" => 6
  ]
  "responsiveVisibleRows" => [
    "mobile" => 50
    "tablet" => 25
    "desktop" => 17
  ]
  "containerClass" => "taxon-grid-subcategories-listing mb-4 px-4 px-sm-0"
  "itemTemplate" => "@BitBagSyliusElasticsearchPlugin/Shop/Product/Index/DisplayStyle/_grid_subcategory_item.html.twig"
  "showMoreText" => "app.ui.collapsible_choices.show_more"
  "showLessText" => "app.ui.collapsible_choices.show_less"
]

App\Twig\Components\ResponsiveCollapsibleGrid {#94445
  +items: Doctrine\ORM\PersistentCollection {#8719
    #collection: Doctrine\Common\Collections\ArrayCollection {#8665 …}
    #initialized: true
    -snapshot: [ …5]
    -owner: App\Entity\Taxonomy\Taxon {#8648 …}
    -association: [ …16]
    -em: ContainerHAOxQ06\EntityManagerGhostEbeb667 {#775 …}
    -backRefFieldName: "parent"
    -typeClass: Symfony\Component\VarDumper\Caster\CutStub {#118181 …}
    -isDirty: false
  }
  +responsiveItemsPerRow: [
    "mobile" => 2
    "tablet" => 4
    "desktop" => 6
  ]
  +responsiveVisibleRows: [
    "mobile" => 50
    "tablet" => 25
    "desktop" => 17
  ]
  +containerClass: "taxon-grid-subcategories-listing mb-4 px-4 px-sm-0"
  +buttonClass: ""
  +itemTemplate: "@BitBagSyliusElasticsearchPlugin/Shop/Product/Index/DisplayStyle/_grid_subcategory_item.html.twig"
  +showMoreText: "app.ui.collapsible_choices.show_more"
  +showLessText: "app.ui.collapsible_choices.show_less"
  +gridItemsIdentifierClass: "responsive-collapsible-grid-item-707359"
}

[
  "product" => App\Entity\Product\Product {#94813
    #id: 10874
    #code: "IEEE00005220"
    #attributes: Doctrine\ORM\PersistentCollection {#94876 …}
    #variants: Doctrine\ORM\PersistentCollection {#94874 …}
    #options: Doctrine\ORM\PersistentCollection {#94870 …}
    #associations: Doctrine\ORM\PersistentCollection {#94872 …}
    #createdAt: DateTime @1751039338 {#94807
      date: 2025-06-27 17:48:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94815
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95013
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94813}
        #id: 38505
        #name: "IEEE 20000-1:2013"
        #slug: "ieee-20000-1-2013-ieee00005220-242526"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          ISO/IEC 20000-1:2011, a service management system (SMS) standard, is adopted by the IEEE in this standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include<br />\n
          the design, transition, delivery, and improvement of services to fulfilll agreed service requirements.<br />\n
          This standard can be used by the following:<br />\n
          - An organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled.<br />\n
          - An organization that requires a consistent approach by all its service providers, including those in a supply chain.<br />\n
          - A service provider that intends to demonstrate its capability for the design, transition, delivery, and improvement of services that fulfilll service requirements.<br />\n
          - A service provider to monitor, measure, and review its service management processes and services.<br />\n
          - A service provider to improve the design, transition, delivery, and improvement of services through the effective implementation and operation of the SMS.<br />\n
          - An assessor or auditor as the criteria for a conformity assessment of a service provider’s SMS to the requirements in this standard.<br />\n
          \t\t\t\t<br />\n
          1.1 General<br />\n
          This part of ISO/IEC 20000 is a service management system (SMS) standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include the design, transition, delivery and improvement of services to fulfill service requirements.<br />\n
          This part of ISO/IEC 20000 can be used by:<br />\n
          a) an organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled;<br />\n
          b) an organization that requires a consistent approach by all its service providers, including those in a supply chain;<br />\n
          c) a service provider that intends to demonstrate its capability for the design, transition, delivery and improvement of services that fulfill service requirements;<br />\n
          d) a service provider to monitor, measure and review its service management processes and services;<br />\n
          e) a service provider to improve the design, transition and delivery of services through effective implementation and operation of an SMS;<br />\n
          f) an assessor or auditor as the criteria for a conformity assessment of a service provider's SMS to the requirements in this part of ISO/IEC 20000.<br />\n
          Figure 2 illustrates an SMS, including the service management processes. The service management processes and the relationships between the processes can be implemented in different ways by different service providers. The nature of the relationship between a service provider and the customer will influence how the service management processes are implemented.<br />\n
          1.2 Application<br />\n
          All requirements in this part of ISO/IEC 20000 are generic and are intended to be applicable to all service providers, regardless of type, size and the nature of the services delivered. Exclusion of any of the requirements in Clauses 4 to 9 is not acceptable when a service provider claims conformity to this part of ISO/IEC 20000, irrespective of the nature of the service provider's organization.<br />\n
          Conformity to the requirements in Clause 4 can only be demonstrated by a service provider showing evidence of fulfillling all of the requirements in Clause 4. A service provider cannot rely on evidence of the governance of processes operated by other parties for the requirements in Clause 4.<br />\n
          Conformity to the requirements in Clauses 5 to 9 can be demonstrated by the service provider showing evidence of fulfillling all requirements. Alternatively, the service provider can show evidence of fulfillling the majority of the requirements themselves and evidence of the governance of processes operated by other parties for those processes, or parts of processes, that the service provider does not operate directly.<br />\n
          The scope of this part of ISO/IEC 20000 excludes the specification for a product or tool. However, organizations can use this part of ISO/IEC 20000 to help them develop products or tools that support the operation of an SMS.<br />\n
          NOTE ISO/IEC TR 20000-3 provides guidance on scope definition and applicability of this part of ISO/IEC 20000.<br />\n
          This includes further explanation about the governance of processes operated by other parties.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Adoption of ISO/IEC 20000-1:2011, Information technology -- Service management -- Part 1: Service management system requirements"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94884 …}
    #channels: Doctrine\ORM\PersistentCollection {#94878 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94882 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94880 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94892 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94822
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94827
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94823
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94824
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-1"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#94890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94888 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "white"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#94913
  +product: App\Entity\Product\Product {#94813
    #id: 10874
    #code: "IEEE00005220"
    #attributes: Doctrine\ORM\PersistentCollection {#94876 …}
    #variants: Doctrine\ORM\PersistentCollection {#94874 …}
    #options: Doctrine\ORM\PersistentCollection {#94870 …}
    #associations: Doctrine\ORM\PersistentCollection {#94872 …}
    #createdAt: DateTime @1751039338 {#94807
      date: 2025-06-27 17:48:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94815
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95013
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94813}
        #id: 38505
        #name: "IEEE 20000-1:2013"
        #slug: "ieee-20000-1-2013-ieee00005220-242526"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          ISO/IEC 20000-1:2011, a service management system (SMS) standard, is adopted by the IEEE in this standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include<br />\n
          the design, transition, delivery, and improvement of services to fulfilll agreed service requirements.<br />\n
          This standard can be used by the following:<br />\n
          - An organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled.<br />\n
          - An organization that requires a consistent approach by all its service providers, including those in a supply chain.<br />\n
          - A service provider that intends to demonstrate its capability for the design, transition, delivery, and improvement of services that fulfilll service requirements.<br />\n
          - A service provider to monitor, measure, and review its service management processes and services.<br />\n
          - A service provider to improve the design, transition, delivery, and improvement of services through the effective implementation and operation of the SMS.<br />\n
          - An assessor or auditor as the criteria for a conformity assessment of a service provider’s SMS to the requirements in this standard.<br />\n
          \t\t\t\t<br />\n
          1.1 General<br />\n
          This part of ISO/IEC 20000 is a service management system (SMS) standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include the design, transition, delivery and improvement of services to fulfill service requirements.<br />\n
          This part of ISO/IEC 20000 can be used by:<br />\n
          a) an organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled;<br />\n
          b) an organization that requires a consistent approach by all its service providers, including those in a supply chain;<br />\n
          c) a service provider that intends to demonstrate its capability for the design, transition, delivery and improvement of services that fulfill service requirements;<br />\n
          d) a service provider to monitor, measure and review its service management processes and services;<br />\n
          e) a service provider to improve the design, transition and delivery of services through effective implementation and operation of an SMS;<br />\n
          f) an assessor or auditor as the criteria for a conformity assessment of a service provider's SMS to the requirements in this part of ISO/IEC 20000.<br />\n
          Figure 2 illustrates an SMS, including the service management processes. The service management processes and the relationships between the processes can be implemented in different ways by different service providers. The nature of the relationship between a service provider and the customer will influence how the service management processes are implemented.<br />\n
          1.2 Application<br />\n
          All requirements in this part of ISO/IEC 20000 are generic and are intended to be applicable to all service providers, regardless of type, size and the nature of the services delivered. Exclusion of any of the requirements in Clauses 4 to 9 is not acceptable when a service provider claims conformity to this part of ISO/IEC 20000, irrespective of the nature of the service provider's organization.<br />\n
          Conformity to the requirements in Clause 4 can only be demonstrated by a service provider showing evidence of fulfillling all of the requirements in Clause 4. A service provider cannot rely on evidence of the governance of processes operated by other parties for the requirements in Clause 4.<br />\n
          Conformity to the requirements in Clauses 5 to 9 can be demonstrated by the service provider showing evidence of fulfillling all requirements. Alternatively, the service provider can show evidence of fulfillling the majority of the requirements themselves and evidence of the governance of processes operated by other parties for those processes, or parts of processes, that the service provider does not operate directly.<br />\n
          The scope of this part of ISO/IEC 20000 excludes the specification for a product or tool. However, organizations can use this part of ISO/IEC 20000 to help them develop products or tools that support the operation of an SMS.<br />\n
          NOTE ISO/IEC TR 20000-3 provides guidance on scope definition and applicability of this part of ISO/IEC 20000.<br />\n
          This includes further explanation about the governance of processes operated by other parties.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Adoption of ISO/IEC 20000-1:2011, Information technology -- Service management -- Part 1: Service management system requirements"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94884 …}
    #channels: Doctrine\ORM\PersistentCollection {#94878 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94882 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94880 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94892 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94822
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94827
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94823
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94824
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-1"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#94890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94888 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#94813
    #id: 10874
    #code: "IEEE00005220"
    #attributes: Doctrine\ORM\PersistentCollection {#94876 …}
    #variants: Doctrine\ORM\PersistentCollection {#94874 …}
    #options: Doctrine\ORM\PersistentCollection {#94870 …}
    #associations: Doctrine\ORM\PersistentCollection {#94872 …}
    #createdAt: DateTime @1751039338 {#94807
      date: 2025-06-27 17:48:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94815
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95013
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94813}
        #id: 38505
        #name: "IEEE 20000-1:2013"
        #slug: "ieee-20000-1-2013-ieee00005220-242526"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          ISO/IEC 20000-1:2011, a service management system (SMS) standard, is adopted by the IEEE in this standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include<br />\n
          the design, transition, delivery, and improvement of services to fulfilll agreed service requirements.<br />\n
          This standard can be used by the following:<br />\n
          - An organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled.<br />\n
          - An organization that requires a consistent approach by all its service providers, including those in a supply chain.<br />\n
          - A service provider that intends to demonstrate its capability for the design, transition, delivery, and improvement of services that fulfilll service requirements.<br />\n
          - A service provider to monitor, measure, and review its service management processes and services.<br />\n
          - A service provider to improve the design, transition, delivery, and improvement of services through the effective implementation and operation of the SMS.<br />\n
          - An assessor or auditor as the criteria for a conformity assessment of a service provider’s SMS to the requirements in this standard.<br />\n
          \t\t\t\t<br />\n
          1.1 General<br />\n
          This part of ISO/IEC 20000 is a service management system (SMS) standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include the design, transition, delivery and improvement of services to fulfill service requirements.<br />\n
          This part of ISO/IEC 20000 can be used by:<br />\n
          a) an organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled;<br />\n
          b) an organization that requires a consistent approach by all its service providers, including those in a supply chain;<br />\n
          c) a service provider that intends to demonstrate its capability for the design, transition, delivery and improvement of services that fulfill service requirements;<br />\n
          d) a service provider to monitor, measure and review its service management processes and services;<br />\n
          e) a service provider to improve the design, transition and delivery of services through effective implementation and operation of an SMS;<br />\n
          f) an assessor or auditor as the criteria for a conformity assessment of a service provider's SMS to the requirements in this part of ISO/IEC 20000.<br />\n
          Figure 2 illustrates an SMS, including the service management processes. The service management processes and the relationships between the processes can be implemented in different ways by different service providers. The nature of the relationship between a service provider and the customer will influence how the service management processes are implemented.<br />\n
          1.2 Application<br />\n
          All requirements in this part of ISO/IEC 20000 are generic and are intended to be applicable to all service providers, regardless of type, size and the nature of the services delivered. Exclusion of any of the requirements in Clauses 4 to 9 is not acceptable when a service provider claims conformity to this part of ISO/IEC 20000, irrespective of the nature of the service provider's organization.<br />\n
          Conformity to the requirements in Clause 4 can only be demonstrated by a service provider showing evidence of fulfillling all of the requirements in Clause 4. A service provider cannot rely on evidence of the governance of processes operated by other parties for the requirements in Clause 4.<br />\n
          Conformity to the requirements in Clauses 5 to 9 can be demonstrated by the service provider showing evidence of fulfillling all requirements. Alternatively, the service provider can show evidence of fulfillling the majority of the requirements themselves and evidence of the governance of processes operated by other parties for those processes, or parts of processes, that the service provider does not operate directly.<br />\n
          The scope of this part of ISO/IEC 20000 excludes the specification for a product or tool. However, organizations can use this part of ISO/IEC 20000 to help them develop products or tools that support the operation of an SMS.<br />\n
          NOTE ISO/IEC TR 20000-3 provides guidance on scope definition and applicability of this part of ISO/IEC 20000.<br />\n
          This includes further explanation about the governance of processes operated by other parties.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Adoption of ISO/IEC 20000-1:2011, Information technology -- Service management -- Part 1: Service management system requirements"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94884 …}
    #channels: Doctrine\ORM\PersistentCollection {#94878 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94882 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94880 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94892 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94822
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94827
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94823
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94824
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-1"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#94890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94888 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#95020
  +product: App\Entity\Product\Product {#94813
    #id: 10874
    #code: "IEEE00005220"
    #attributes: Doctrine\ORM\PersistentCollection {#94876 …}
    #variants: Doctrine\ORM\PersistentCollection {#94874 …}
    #options: Doctrine\ORM\PersistentCollection {#94870 …}
    #associations: Doctrine\ORM\PersistentCollection {#94872 …}
    #createdAt: DateTime @1751039338 {#94807
      date: 2025-06-27 17:48:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94815
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95013
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94813}
        #id: 38505
        #name: "IEEE 20000-1:2013"
        #slug: "ieee-20000-1-2013-ieee00005220-242526"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          ISO/IEC 20000-1:2011, a service management system (SMS) standard, is adopted by the IEEE in this standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include<br />\n
          the design, transition, delivery, and improvement of services to fulfilll agreed service requirements.<br />\n
          This standard can be used by the following:<br />\n
          - An organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled.<br />\n
          - An organization that requires a consistent approach by all its service providers, including those in a supply chain.<br />\n
          - A service provider that intends to demonstrate its capability for the design, transition, delivery, and improvement of services that fulfilll service requirements.<br />\n
          - A service provider to monitor, measure, and review its service management processes and services.<br />\n
          - A service provider to improve the design, transition, delivery, and improvement of services through the effective implementation and operation of the SMS.<br />\n
          - An assessor or auditor as the criteria for a conformity assessment of a service provider’s SMS to the requirements in this standard.<br />\n
          \t\t\t\t<br />\n
          1.1 General<br />\n
          This part of ISO/IEC 20000 is a service management system (SMS) standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include the design, transition, delivery and improvement of services to fulfill service requirements.<br />\n
          This part of ISO/IEC 20000 can be used by:<br />\n
          a) an organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled;<br />\n
          b) an organization that requires a consistent approach by all its service providers, including those in a supply chain;<br />\n
          c) a service provider that intends to demonstrate its capability for the design, transition, delivery and improvement of services that fulfill service requirements;<br />\n
          d) a service provider to monitor, measure and review its service management processes and services;<br />\n
          e) a service provider to improve the design, transition and delivery of services through effective implementation and operation of an SMS;<br />\n
          f) an assessor or auditor as the criteria for a conformity assessment of a service provider's SMS to the requirements in this part of ISO/IEC 20000.<br />\n
          Figure 2 illustrates an SMS, including the service management processes. The service management processes and the relationships between the processes can be implemented in different ways by different service providers. The nature of the relationship between a service provider and the customer will influence how the service management processes are implemented.<br />\n
          1.2 Application<br />\n
          All requirements in this part of ISO/IEC 20000 are generic and are intended to be applicable to all service providers, regardless of type, size and the nature of the services delivered. Exclusion of any of the requirements in Clauses 4 to 9 is not acceptable when a service provider claims conformity to this part of ISO/IEC 20000, irrespective of the nature of the service provider's organization.<br />\n
          Conformity to the requirements in Clause 4 can only be demonstrated by a service provider showing evidence of fulfillling all of the requirements in Clause 4. A service provider cannot rely on evidence of the governance of processes operated by other parties for the requirements in Clause 4.<br />\n
          Conformity to the requirements in Clauses 5 to 9 can be demonstrated by the service provider showing evidence of fulfillling all requirements. Alternatively, the service provider can show evidence of fulfillling the majority of the requirements themselves and evidence of the governance of processes operated by other parties for those processes, or parts of processes, that the service provider does not operate directly.<br />\n
          The scope of this part of ISO/IEC 20000 excludes the specification for a product or tool. However, organizations can use this part of ISO/IEC 20000 to help them develop products or tools that support the operation of an SMS.<br />\n
          NOTE ISO/IEC TR 20000-3 provides guidance on scope definition and applicability of this part of ISO/IEC 20000.<br />\n
          This includes further explanation about the governance of processes operated by other parties.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Adoption of ISO/IEC 20000-1:2011, Information technology -- Service management -- Part 1: Service management system requirements"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94884 …}
    #channels: Doctrine\ORM\PersistentCollection {#94878 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94882 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94880 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94892 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94822
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94827
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94823
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94824
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-1"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#94890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94888 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#94813
    #id: 10874
    #code: "IEEE00005220"
    #attributes: Doctrine\ORM\PersistentCollection {#94876 …}
    #variants: Doctrine\ORM\PersistentCollection {#94874 …}
    #options: Doctrine\ORM\PersistentCollection {#94870 …}
    #associations: Doctrine\ORM\PersistentCollection {#94872 …}
    #createdAt: DateTime @1751039338 {#94807
      date: 2025-06-27 17:48:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94815
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95013
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94813}
        #id: 38505
        #name: "IEEE 20000-1:2013"
        #slug: "ieee-20000-1-2013-ieee00005220-242526"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          ISO/IEC 20000-1:2011, a service management system (SMS) standard, is adopted by the IEEE in this standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include<br />\n
          the design, transition, delivery, and improvement of services to fulfilll agreed service requirements.<br />\n
          This standard can be used by the following:<br />\n
          - An organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled.<br />\n
          - An organization that requires a consistent approach by all its service providers, including those in a supply chain.<br />\n
          - A service provider that intends to demonstrate its capability for the design, transition, delivery, and improvement of services that fulfilll service requirements.<br />\n
          - A service provider to monitor, measure, and review its service management processes and services.<br />\n
          - A service provider to improve the design, transition, delivery, and improvement of services through the effective implementation and operation of the SMS.<br />\n
          - An assessor or auditor as the criteria for a conformity assessment of a service provider’s SMS to the requirements in this standard.<br />\n
          \t\t\t\t<br />\n
          1.1 General<br />\n
          This part of ISO/IEC 20000 is a service management system (SMS) standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include the design, transition, delivery and improvement of services to fulfill service requirements.<br />\n
          This part of ISO/IEC 20000 can be used by:<br />\n
          a) an organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled;<br />\n
          b) an organization that requires a consistent approach by all its service providers, including those in a supply chain;<br />\n
          c) a service provider that intends to demonstrate its capability for the design, transition, delivery and improvement of services that fulfill service requirements;<br />\n
          d) a service provider to monitor, measure and review its service management processes and services;<br />\n
          e) a service provider to improve the design, transition and delivery of services through effective implementation and operation of an SMS;<br />\n
          f) an assessor or auditor as the criteria for a conformity assessment of a service provider's SMS to the requirements in this part of ISO/IEC 20000.<br />\n
          Figure 2 illustrates an SMS, including the service management processes. The service management processes and the relationships between the processes can be implemented in different ways by different service providers. The nature of the relationship between a service provider and the customer will influence how the service management processes are implemented.<br />\n
          1.2 Application<br />\n
          All requirements in this part of ISO/IEC 20000 are generic and are intended to be applicable to all service providers, regardless of type, size and the nature of the services delivered. Exclusion of any of the requirements in Clauses 4 to 9 is not acceptable when a service provider claims conformity to this part of ISO/IEC 20000, irrespective of the nature of the service provider's organization.<br />\n
          Conformity to the requirements in Clause 4 can only be demonstrated by a service provider showing evidence of fulfillling all of the requirements in Clause 4. A service provider cannot rely on evidence of the governance of processes operated by other parties for the requirements in Clause 4.<br />\n
          Conformity to the requirements in Clauses 5 to 9 can be demonstrated by the service provider showing evidence of fulfillling all requirements. Alternatively, the service provider can show evidence of fulfillling the majority of the requirements themselves and evidence of the governance of processes operated by other parties for those processes, or parts of processes, that the service provider does not operate directly.<br />\n
          The scope of this part of ISO/IEC 20000 excludes the specification for a product or tool. However, organizations can use this part of ISO/IEC 20000 to help them develop products or tools that support the operation of an SMS.<br />\n
          NOTE ISO/IEC TR 20000-3 provides guidance on scope definition and applicability of this part of ISO/IEC 20000.<br />\n
          This includes further explanation about the governance of processes operated by other parties.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Adoption of ISO/IEC 20000-1:2011, Information technology -- Service management -- Part 1: Service management system requirements"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94884 …}
    #channels: Doctrine\ORM\PersistentCollection {#94878 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94882 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94880 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94892 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94822
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94827
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94823
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94824
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-1"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#94890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94888 …}
  }
]

App\Twig\Components\ProductMostRecent {#95114
  +product: App\Entity\Product\Product {#94813
    #id: 10874
    #code: "IEEE00005220"
    #attributes: Doctrine\ORM\PersistentCollection {#94876 …}
    #variants: Doctrine\ORM\PersistentCollection {#94874 …}
    #options: Doctrine\ORM\PersistentCollection {#94870 …}
    #associations: Doctrine\ORM\PersistentCollection {#94872 …}
    #createdAt: DateTime @1751039338 {#94807
      date: 2025-06-27 17:48:58.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#94815
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94886 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95013
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94813}
        #id: 38505
        #name: "IEEE 20000-1:2013"
        #slug: "ieee-20000-1-2013-ieee00005220-242526"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          ISO/IEC 20000-1:2011, a service management system (SMS) standard, is adopted by the IEEE in this standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include<br />\n
          the design, transition, delivery, and improvement of services to fulfilll agreed service requirements.<br />\n
          This standard can be used by the following:<br />\n
          - An organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled.<br />\n
          - An organization that requires a consistent approach by all its service providers, including those in a supply chain.<br />\n
          - A service provider that intends to demonstrate its capability for the design, transition, delivery, and improvement of services that fulfilll service requirements.<br />\n
          - A service provider to monitor, measure, and review its service management processes and services.<br />\n
          - A service provider to improve the design, transition, delivery, and improvement of services through the effective implementation and operation of the SMS.<br />\n
          - An assessor or auditor as the criteria for a conformity assessment of a service provider’s SMS to the requirements in this standard.<br />\n
          \t\t\t\t<br />\n
          1.1 General<br />\n
          This part of ISO/IEC 20000 is a service management system (SMS) standard. It specifies requirements for the service provider to plan, establish, implement, operate, monitor, review, maintain and improve an SMS. The requirements include the design, transition, delivery and improvement of services to fulfill service requirements.<br />\n
          This part of ISO/IEC 20000 can be used by:<br />\n
          a) an organization seeking services from service providers and requiring assurance that their service requirements will be fulfillled;<br />\n
          b) an organization that requires a consistent approach by all its service providers, including those in a supply chain;<br />\n
          c) a service provider that intends to demonstrate its capability for the design, transition, delivery and improvement of services that fulfill service requirements;<br />\n
          d) a service provider to monitor, measure and review its service management processes and services;<br />\n
          e) a service provider to improve the design, transition and delivery of services through effective implementation and operation of an SMS;<br />\n
          f) an assessor or auditor as the criteria for a conformity assessment of a service provider's SMS to the requirements in this part of ISO/IEC 20000.<br />\n
          Figure 2 illustrates an SMS, including the service management processes. The service management processes and the relationships between the processes can be implemented in different ways by different service providers. The nature of the relationship between a service provider and the customer will influence how the service management processes are implemented.<br />\n
          1.2 Application<br />\n
          All requirements in this part of ISO/IEC 20000 are generic and are intended to be applicable to all service providers, regardless of type, size and the nature of the services delivered. Exclusion of any of the requirements in Clauses 4 to 9 is not acceptable when a service provider claims conformity to this part of ISO/IEC 20000, irrespective of the nature of the service provider's organization.<br />\n
          Conformity to the requirements in Clause 4 can only be demonstrated by a service provider showing evidence of fulfillling all of the requirements in Clause 4. A service provider cannot rely on evidence of the governance of processes operated by other parties for the requirements in Clause 4.<br />\n
          Conformity to the requirements in Clauses 5 to 9 can be demonstrated by the service provider showing evidence of fulfillling all requirements. Alternatively, the service provider can show evidence of fulfillling the majority of the requirements themselves and evidence of the governance of processes operated by other parties for those processes, or parts of processes, that the service provider does not operate directly.<br />\n
          The scope of this part of ISO/IEC 20000 excludes the specification for a product or tool. However, organizations can use this part of ISO/IEC 20000 to help them develop products or tools that support the operation of an SMS.<br />\n
          NOTE ISO/IEC TR 20000-3 provides guidance on scope definition and applicability of this part of ISO/IEC 20000.<br />\n
          This includes further explanation about the governance of processes operated by other parties.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard - Adoption of ISO/IEC 20000-1:2011, Information technology -- Service management -- Part 1: Service management system requirements"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94884 …}
    #channels: Doctrine\ORM\PersistentCollection {#94878 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94882 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94880 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94892 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94822
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94827
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94823
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94824
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-1"
    -bookCollection: ""
    -pageCount: 48
    -documents: Doctrine\ORM\PersistentCollection {#94890 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94888 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#94841
    #id: 11079
    #code: "IEEE00005548"
    #attributes: Doctrine\ORM\PersistentCollection {#94858 …}
    #variants: Doctrine\ORM\PersistentCollection {#94860 …}
    #options: Doctrine\ORM\PersistentCollection {#94895 …}
    #associations: Doctrine\ORM\PersistentCollection {#94862 …}
    #createdAt: DateTime @1751039465 {#94868
      date: 2025-06-27 17:51:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#94867
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94850 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94841}
        #id: 39325
        #name: "IEEE 20000-2:2013"
        #slug: "ieee-20000-2-2013-ieee00005548-242731"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n
          This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n
          This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n
          \t\t\t\t<br />\n
          1.1. General.<br />\n
          This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n
          Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n
          The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n
          1.2 Application<br />\n
          The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n
          Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n
          The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n
          ISO/IEC 20000-1.<br />\n
          The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n
          ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94849 …}
    #channels: Doctrine\ORM\PersistentCollection {#94856 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94854 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94840 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94866
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94865
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94864
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94863
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-2"
    -bookCollection: ""
    -pageCount: 105
    -documents: Doctrine\ORM\PersistentCollection {#94835 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94833 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "imageFilter" => "product_listing_thumbnail"
  "additionalClasses" => "h-100 border-0"
  "hasStretchedLink" => true
  "backgroundColor" => "secondary-lighter"
  "hoverType" => "border-black"
]

App\Twig\Components\ProductCard {#95305
  +product: App\Entity\Product\Product {#94841
    #id: 11079
    #code: "IEEE00005548"
    #attributes: Doctrine\ORM\PersistentCollection {#94858 …}
    #variants: Doctrine\ORM\PersistentCollection {#94860 …}
    #options: Doctrine\ORM\PersistentCollection {#94895 …}
    #associations: Doctrine\ORM\PersistentCollection {#94862 …}
    #createdAt: DateTime @1751039465 {#94868
      date: 2025-06-27 17:51:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#94867
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94850 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94841}
        #id: 39325
        #name: "IEEE 20000-2:2013"
        #slug: "ieee-20000-2-2013-ieee00005548-242731"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n
          This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n
          This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n
          \t\t\t\t<br />\n
          1.1. General.<br />\n
          This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n
          Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n
          The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n
          1.2 Application<br />\n
          The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n
          Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n
          The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n
          ISO/IEC 20000-1.<br />\n
          The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n
          ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94849 …}
    #channels: Doctrine\ORM\PersistentCollection {#94856 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94854 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94840 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94866
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94865
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94864
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94863
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-2"
    -bookCollection: ""
    -pageCount: 105
    -documents: Doctrine\ORM\PersistentCollection {#94835 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94833 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "h-100 border-0"
  +linkLabel: ""
  +imageFilter: "product_listing_thumbnail"
  +hasStretchedLink: true
  +backgroundColor: "secondary-lighter"
  +hoverType: "border-black"
}

[
  "product" => App\Entity\Product\Product {#94841
    #id: 11079
    #code: "IEEE00005548"
    #attributes: Doctrine\ORM\PersistentCollection {#94858 …}
    #variants: Doctrine\ORM\PersistentCollection {#94860 …}
    #options: Doctrine\ORM\PersistentCollection {#94895 …}
    #associations: Doctrine\ORM\PersistentCollection {#94862 …}
    #createdAt: DateTime @1751039465 {#94868
      date: 2025-06-27 17:51:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#94867
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94850 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94841}
        #id: 39325
        #name: "IEEE 20000-2:2013"
        #slug: "ieee-20000-2-2013-ieee00005548-242731"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n
          This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n
          This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n
          \t\t\t\t<br />\n
          1.1. General.<br />\n
          This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n
          Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n
          The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n
          1.2 Application<br />\n
          The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n
          Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n
          The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n
          ISO/IEC 20000-1.<br />\n
          The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n
          ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94849 …}
    #channels: Doctrine\ORM\PersistentCollection {#94856 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94854 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94840 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94866
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94865
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94864
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94863
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-2"
    -bookCollection: ""
    -pageCount: 105
    -documents: Doctrine\ORM\PersistentCollection {#94835 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94833 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#95334
  +product: App\Entity\Product\Product {#94841
    #id: 11079
    #code: "IEEE00005548"
    #attributes: Doctrine\ORM\PersistentCollection {#94858 …}
    #variants: Doctrine\ORM\PersistentCollection {#94860 …}
    #options: Doctrine\ORM\PersistentCollection {#94895 …}
    #associations: Doctrine\ORM\PersistentCollection {#94862 …}
    #createdAt: DateTime @1751039465 {#94868
      date: 2025-06-27 17:51:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#94867
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94850 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94841}
        #id: 39325
        #name: "IEEE 20000-2:2013"
        #slug: "ieee-20000-2-2013-ieee00005548-242731"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n
          This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n
          This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n
          \t\t\t\t<br />\n
          1.1. General.<br />\n
          This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n
          Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n
          The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n
          1.2 Application<br />\n
          The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n
          Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n
          The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n
          ISO/IEC 20000-1.<br />\n
          The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n
          ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94849 …}
    #channels: Doctrine\ORM\PersistentCollection {#94856 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94854 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94840 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94866
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94865
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94864
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94863
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-2"
    -bookCollection: ""
    -pageCount: 105
    -documents: Doctrine\ORM\PersistentCollection {#94835 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94833 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#94841
    #id: 11079
    #code: "IEEE00005548"
    #attributes: Doctrine\ORM\PersistentCollection {#94858 …}
    #variants: Doctrine\ORM\PersistentCollection {#94860 …}
    #options: Doctrine\ORM\PersistentCollection {#94895 …}
    #associations: Doctrine\ORM\PersistentCollection {#94862 …}
    #createdAt: DateTime @1751039465 {#94868
      date: 2025-06-27 17:51:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#94867
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94850 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94841}
        #id: 39325
        #name: "IEEE 20000-2:2013"
        #slug: "ieee-20000-2-2013-ieee00005548-242731"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n
          This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n
          This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n
          \t\t\t\t<br />\n
          1.1. General.<br />\n
          This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n
          Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n
          The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n
          1.2 Application<br />\n
          The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n
          Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n
          The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n
          ISO/IEC 20000-1.<br />\n
          The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n
          ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94849 …}
    #channels: Doctrine\ORM\PersistentCollection {#94856 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94854 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94840 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94866
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94865
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94864
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94863
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-2"
    -bookCollection: ""
    -pageCount: 105
    -documents: Doctrine\ORM\PersistentCollection {#94835 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94833 …}
  }
]

App\Twig\Components\ProductMostRecent {#95411
  +product: App\Entity\Product\Product {#94841
    #id: 11079
    #code: "IEEE00005548"
    #attributes: Doctrine\ORM\PersistentCollection {#94858 …}
    #variants: Doctrine\ORM\PersistentCollection {#94860 …}
    #options: Doctrine\ORM\PersistentCollection {#94895 …}
    #associations: Doctrine\ORM\PersistentCollection {#94862 …}
    #createdAt: DateTime @1751039465 {#94868
      date: 2025-06-27 17:51:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#94867
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#94850 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#95327
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#94841}
        #id: 39325
        #name: "IEEE 20000-2:2013"
        #slug: "ieee-20000-2-2013-ieee00005548-242731"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Guidance on the application of service management systems (SMS) based on the requirements in IEEE Std 20000-2-2013 (ISO/IEC 20000-1) is provided in this adoption of ISO/IEC 20000-2:2012.<br />\n
          This standard enables organizations and individuals to interpret ISO/IEC 20000-1 more accurately and therefore to use it more effectively. The guidance includes examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards.<br />\n
          This includes guidance on the use of an SMS for the planning, design, transition, delivery and improvement of the SMS and services. At a minimum this includes service management policies, objectives, plans, service management processes, process interfaces, documentation, and resources. The SMS provides ongoing control, greater effectiveness, efficiency, and opportunities for continual improvement of service management and of services. It enables an organization to work effectively with a shared vision.<br />\n
          \t\t\t\t<br />\n
          1.1. General.<br />\n
          This part of ISO/IEC 20000 provides guidance on the application of an SMS based on ISO/IEC 20000-1. This part of ISO/IEC 20000 provides examples and suggestions to enable organizations to interpret and apply ISO/IEC 20000-1, including references to other parts of ISO/IEC 20000 and other relevant standards. This part of ISO/IEC 20000 is independent of specific best practice frameworks and the service provider can apply a combination of generally accepted guidance and their own techniques.<br />\n
          Figure 2 shows the processes from Clauses 6 to 9 in the central box. The Clause 5 design and transition of new or changed services process surrounds the Clause 6 to 9 processes. This shows that the new or changed services are operated by the processes in the central box. When there are no new or changed services to which Clause 5 applies, all services can be delivered directly by Clauses 6 to 9.<br />\n
          The interfaces between the service management processes and the relationships between different components of the SMS may be implemented differently by different service providers. The nature of the relationship between the service provider and the customer can also influence how the SMS is implemented to fulfill the requirements of ISO/IEC 20000-1. For these reasons the interfaces between processes are not represented in Figure 2.<br />\n
          1.2 Application<br />\n
          The service provider is accountable for the SMS and therefore cannot ask another party to fulfill the requirements of Clause 4 of ISO/IEC 20000-1:2011. For example, the service provider cannot ask another party to provide the top management and demonstrate top management commitment or to demonstrate the governance of processes operated by other parties.<br />\n
          Some activities in Clause 4 may be performed by another party under the management of the service provider. For example, service providers can engage other parties to conduct internal audits on their behalf. Another example is where a service provider asks another party to create the initial service management plan. The plan, once created and agreed, is the direct responsibility of and is maintained by the service provider. In these examples, the service provider is using other parties for specific short-term activities. The service provider has accountability, authorities and responsibilities for the SMS. The service provider can therefore demonstrate evidence of fulfillling all of the requirements of Clause 4 of ISO/IEC 20000-1:2011.<br />\n
          The service provider can show evidence of fulfillling all requirements directly or can show evidence of fulfillling most of the requirements directly as well as the governance of processes operated by other parties. If the service provider relies on other parties for operation of the majority of the processes in Clauses 5 to 9, the service provider is unlikely to be able to demonstrate governance of the processes. However, if other parties operate only a minority of the processes, the service provider can normally fulfill the requirements specified in<br />\n
          ISO/IEC 20000-1.<br />\n
          The defined, agreed and documented accountability, authorities and responsibilities for the SMS are readily accessible to both the service provider and other relevant parties. To fulfill the requirements of ISO/IEC 20000-1 the service provider can agree changes to the terms of existing contracts or other documented agreements.<br />\n
          ISO/IEC 20000 excludes the specification of, or specific guidance about, any product or tool. However, organizations can use this part of ISO/IEC 20000 to help them use or develop products or tools that support operation of the SMS.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard -- Adoption of ISO/IEC 20000-2:2012, Information technology -- Service management -- Part 2: Guidance on the application of service management systems"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#94849 …}
    #channels: Doctrine\ORM\PersistentCollection {#94856 …}
    #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …}
    #reviews: Doctrine\ORM\PersistentCollection {#94852 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#94854 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94893 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94840 …}
    -apiLastModifiedAt: DateTime @1754517600 {#94866
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#94865
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1370210400 {#94864
      date: 2013-06-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1537999200 {#94863
      date: 2018-09-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "20000-2"
    -bookCollection: ""
    -pageCount: 105
    -documents: Doctrine\ORM\PersistentCollection {#94835 …}
    -favorites: Doctrine\ORM\PersistentCollection {#94833 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}