From 219e55c1f86fd78027f164e1ae3cb895bff57261 Mon Sep 17 00:00:00 2001 From: Matthew Griffin <117279304+mgriffin-scottlogic@users.noreply.github.com> Date: Tue, 10 Sep 2024 15:00:20 +0100 Subject: [PATCH] SFD-207: Ensure links from categories go to the right part of the page (#57) * Make sure internal links go to the correct fragment (limitation of the jekyll-redirect-from plugin is that it doesn't pass this through) * Additional link updates --- _data/carbonStandard.yml | 30 +++++++++++------------ pages/impact_categories/operational.md | 4 +-- pages/technology_categories/cloud/paas.md | 4 +-- pages/technology_categories/estate.md | 8 +++--- 4 files changed, 23 insertions(+), 23 deletions(-) diff --git a/_data/carbonStandard.yml b/_data/carbonStandard.yml index b4aa938..5177a3c 100644 --- a/_data/carbonStandard.yml +++ b/_data/carbonStandard.yml @@ -31,7 +31,7 @@ CatUSoftware: icon: web selected: false description: - link: /categories/upstream#software + link: /impact-categories/upstream#software noLink: false CatUEmployeeHardware: @@ -41,7 +41,7 @@ CatUEmployeeHardware: icon: devices selected: false description: - link: /categories/upstream#employee-hardware + link: /impact-categories/upstream#employee-hardware noLink: false CatUNetworkHardware: @@ -51,7 +51,7 @@ CatUNetworkHardware: icon: router selected: false description: - link: /categories/upstream#networking-hardware + link: /impact-categories/upstream#networking-hardware noLink: false CatUServerHardware: @@ -61,7 +61,7 @@ CatUServerHardware: icon: storage selected: false description: - link: /categories/upstream#data-centre-and-server-hardware + link: /impact-categories/upstream#data-centre-and-server-hardware noLink: false OperationalEmissions: @@ -77,7 +77,7 @@ CatOServers: icon: storage selected: false description: - link: /categories/operational#servers-and-storage + link: /impact-categories/operational#servers-and-storage noLink: false CatONetworkDevices: @@ -87,7 +87,7 @@ CatONetworkDevices: icon: router selected: false description: - link: /categories/operational#networking-devices + link: /impact-categories/operational#networking-devices noLink: false CatOOnsiteEmployeeDevices: @@ -97,7 +97,7 @@ CatOOnsiteEmployeeDevices: icon: devices selected: false description: - link: /categories/operational#onsite-employee-devices + link: /impact-categories/operational#onsite-employee-devices noLink: false CatGGenerators: @@ -107,7 +107,7 @@ CatGGenerators: icon: bolt selected: false description: - link: /categories/operational#generators + link: /impact-categories/operational#generators noLink: false CatC: @@ -120,7 +120,7 @@ CatCCloud: icon: cloud selected: false description: - link: /categories/operational#cloud-services + link: /impact-categories/operational#cloud-services noLink: false CatCSaas: @@ -130,7 +130,7 @@ CatCSaas: icon: web selected: false description: - link: /categories/operational#saas + link: /impact-categories/operational#saas noLink: false CatCManaged: @@ -140,7 +140,7 @@ CatCManaged: icon: storage selected: false description: - link: /categories/operational#managed-services + link: /impact-categories/operational#managed-services noLink: false CatCOffsiteEmployeeDevices: @@ -150,7 +150,7 @@ CatCOffsiteEmployeeDevices: icon: devices selected: false description: - link: /categories/operational#offsite-employee-devices + link: /impact-categories/operational#offsite-employee-devices noLink: false CatD: @@ -163,7 +163,7 @@ CatDEndUserDevices: icon: devices selected: false description: - link: /categories/downstream#end-user-devices + link: /impact-categories/downstream#end-user-devices noLink: false CatDNetworkDataTransfer: @@ -173,7 +173,7 @@ CatDNetworkDataTransfer: icon: cell-tower selected: false description: - link: /categories/downstream#network-data-transfer + link: /impact-categories/downstream#network-data-transfer noLink: false CatDInfrastructure: @@ -183,5 +183,5 @@ CatDInfrastructure: icon: hub selected: false description: - link: /categories/downstream#infrastructure + link: /impact-categories/downstream#infrastructure noLink: false \ No newline at end of file diff --git a/pages/impact_categories/operational.md b/pages/impact_categories/operational.md index 9f83cd6..6a85250 100644 --- a/pages/impact_categories/operational.md +++ b/pages/impact_categories/operational.md @@ -82,9 +82,9 @@ Managed Security Operations, IT support and data backup services. {% include linkedHeading.html heading="Offsite Employee Devices" level=3 %} -The emissions incurred by computers (desktops, laptops), monitors, printers, and other devices used by employees, when used out-of-office. Since these are required by the business, they are accounted for, but as with other indirect groupings, the business does not control them directly. Accordingly, they come under [GHG Protocol Scope 3](/glossary#greenhouse-gas-ghg-protocols), and so are a separate category. +The emissions incurred by computers (desktops, laptops), monitors, printers, and other devices used by employees, when used out-of-office. Since these are required by the business, they are accounted for, but as with other indirect groupings, the business does not control them directly. Accordingly, they come under [GHG Protocol Scope 3](/resources/glossary#greenhouse-gas-ghg-protocols), and so are a separate category. -Offsite employee devices are typically accounted for with an [attribution factor](/glossary#attribution-factor), representing the proportion of time that their use is dedicated to business purposes. +Offsite employee devices are typically accounted for with an [attribution factor](/resources/glossary#attribution-factor), representing the proportion of time that their use is dedicated to business purposes. ## References diff --git a/pages/technology_categories/cloud/paas.md b/pages/technology_categories/cloud/paas.md index 4b6577f..6030a0f 100644 --- a/pages/technology_categories/cloud/paas.md +++ b/pages/technology_categories/cloud/paas.md @@ -24,7 +24,7 @@ Cloud vendor PaaS options often straddle the IaaS divide and allow the mixing an There's also a pattern of CDN providers now offering short-lived compute and sometimes storage services alongside traditional caching use cases. {% include linkedHeading.html heading="Benefits of PaaS for emissions" level=2 %} -The advantages and disadvantages of cloud from an emissions perspective are discussed in Cloud Emissions including the use of green electricity (if offsetting is counted) and having a low PUE. +The advantages and disadvantages of cloud from an emissions perspective are discussed in Cloud Emissions including the use of green electricity (if offsetting is counted) and having a low PUE. Where PaaS can have an advantage over IaaS is in maximising utilisation. Where an organisation has lifted and shifted virtual machines from on-prem those machines may be doing very little work but taking a percentage of a physical machine's resources meaning energy use from CPU and memory usage and also resulting in embodied carbon. e.g. if some large cloud VM instances are required to be continually running in case of high traffic once a day or week. @@ -93,7 +93,7 @@ For AWS, Azure, GCP PaaS services can be measured as described in PUE for each one to capture efficiency. More detail on how to do this is provided in the following sub-sections. Where there's a need to prioritise the analysis, then focus on the largest sources of emissions which will normally be data centres, as indicated by the arrow in the diagram. +To get a complete picture of emissions then all sites, their locations and all hardware within those sites must be identified as well as a PUE for each one to capture efficiency. More detail on how to do this is provided in the following sub-sections. Where there's a need to prioritise the analysis, then focus on the largest sources of emissions which will normally be data centres, as indicated by the arrow in the diagram. {% include linkedHeading.html heading="Device inventory records" level=3 %} @@ -113,7 +113,7 @@ The accuracy of the underlying data will directly impact the precision of emissi Embodied emissions should be based on the asset database described above and ideally the CMDB records will include manufacturer data about each asset's embodied carbon or at least enough information that it can be looked up via data sheets. Where this is not present approximations may be used based on typical values - see Server example for some suggestions around how to do this. -In the earlier diagram the cooling/lighting/other boxes were distinguished in a different shade of green because they are not technology hardware but general purpose equipment that support it. For embodied emissions they are out of the scope of the TCS and therefore not discussed but you should still calculate them for full GHGP Scope 3 emissions. +In the earlier diagram the cooling/lighting/other boxes were distinguished in a different shade of green because they are not technology hardware but general purpose equipment that support it. For embodied emissions they are out of the scope of the TCS and therefore not discussed but you should still calculate them for full GHGP Scope 3 emissions. {% include linkedHeading.html heading="Operational emissions - reporting" level=3 %} @@ -298,7 +298,7 @@ Device power may be specific or if this isn't available for all devices then est {% include linkedHeading.html heading="Reducing emissions" level=3 %} -For servers and cloud the analysis for reducing emissions was more complex than reporting but the opposite is true for devices. Monitors don't have any software running on them to attribute to anyone and although technically laptops do, the wide variety of applications and the fact that the bulk of the carbon will be from their manufacture not the use means there is little value in any analysis. User owned devices (like personal laptops) can also be ignored. +For servers and cloud the analysis for reducing emissions was more complex than reporting but the opposite is true for devices. Monitors don't have any software running on them to attribute to anyone and although technically laptops do, the wide variety of applications and the fact that the bulk of the carbon will be from their manufacture not the use means there is little value in any analysis. User owned devices (like personal laptops) can also be ignored. Therefore, for reducing emissions the focus will be on procurement policy and on changing the default choices of device purchased by the org. If there are 1 or 2 procurement teams then all that matters is how those teams choose devices and manage their longevity and disposal. @@ -310,7 +310,7 @@ There's broadly 3 types of end user device: * IoT devices which may be provided by the organisation selling the software * Servers for service to service communication -The following sections go through each of these. A judgement should be taken as to whether the downstream emissions are worth calculating in any depth. For example, if customer numbers are in the hundreds or less it is likely these emissions will just be noise vs other tech emissions. On the other hand, a video streaming or gaming app with hundreds of thousands of users using the app each day for hours a time shouldn't be ignored. Start with rough approximations based on the information in Downstream and the following sub-sections before deciding whether to go any further. +The following sections go through each of these. A judgement should be taken as to whether the downstream emissions are worth calculating in any depth. For example, if customer numbers are in the hundreds or less it is likely these emissions will just be noise vs other tech emissions. On the other hand, a video streaming or gaming app with hundreds of thousands of users using the app each day for hours a time shouldn't be ignored. Start with rough approximations based on the information in Downstream and the following sub-sections before deciding whether to go any further. {% include linkedHeading.html heading="Consumer devices" level=3 %}