The ISO Show Podcast Por Blackmores UK arte de portada

The ISO Show

The ISO Show

De: Blackmores UK
Escúchala gratis

Obtén 3 meses por US$0.99 al mes + $20 crédito Audible
Blackmores is a pioneering consultancy firm with a distinctive approach to working with our clients to achieve and sustain high standards in Quality, Risk and Environmental Management. We'll be posting podcasts discussing ISO standards here very soon!All rights reserved Economía Gestión Gestión y Liderazgo
Episodios
  • #236 Taking Data Complexity From Spreadsheets To Supply Chains With Pulsora

    #236 Taking Data Complexity From Spreadsheets To Supply Chains With Pulsora
    Nov 19 2025
    Watch the video interview here One of the common pain points when calculating your carbon emissions is simply gathering the data. When collating data from different departments and suppliers, it can be easy to get overwhelmed. The struggle doesn't stop there, as after obtaining all that data you have to find the best way to capture and display it in a way that's useable for the necessary number crunching. Many will turn to an old favourite, spreadsheets, but these can quickly become very unwieldy and impractical if you've got a lot of data to process. Thankfully, there's a lot of new tech and tools available to help make this task both approachable and integrated within your business. In this episode, Mel Blackmore is joined by Jessica Matthys, Lead Product Manager at Pulsora, to discuss how you can take data complexity from spreadsheets to supply chains, diving into data fragmentation, optimisation and how this can all be balanced for practicality. You'll learn · Who is Jessica Matthys? · Who are Pulsora? · What does data complexity mean in the context of carbon accounting? · What are the requirements for CSRD in California? · What are the biggest pain points relating to data collection? · How can you prevent data fragmentation across your business? · What does 'Comprehensive data' mean in the context of sustainability? · How can Pulsora help a business take their carbon data from spreadsheets to integrated data systems? · How can you make you carbon data more auditable and traceable? · How can new carbon focused technology, such as AI tools, help with seeking investment? · How can you get information from your supply chain to cover scope 3 emissions? Resources · Pulsora · CSRD – California Regulations · SB-253 & SB-261 · Carbonology In this episode, we talk about: [00:25] Episode Summary – Mel Blackmore is joined by Jessica Matthys, Lead Product Manager at Pulsora, to explore how you can take data complexity from spreadsheets to supply chains, diving into data fragmentation, optimisation and how this can all be balanced for practicality. [01:40] Who is Jessica Matthys: Is the Lead Product Manager for carbon solutions at Pulsora. She's been with Pulsora for a year and a half, but has worked within the ESG / carbon / sustainability space for over 8 years in total. Something that people might not know about Jessica is that her passion for sustainability started much earlier than her working career, starting in high school where she opted to live on a farm for one semester. That unique experience of working closely with nature and animals set her on the path that she still walks today. [02:30] Who are Pulsora? Pulsora is an end to end sustainability management AI powered platform. They can manage anything from data collection and carbon accounting all the way towards ESG reporting and audit support. The focus of their platform is auditability and transparency . [04:40] What does data complexity mean in the context of carbon accounting? Jessica breaks this down into three main elements: Disparate nature of data – When compiling data for greenhouse gas accounting, you have to take a lot into consideration including your own production and consumption in addition to all the upstream and downstream relationships across your value chain. The data for all of this will be scattered and will need to be brought together in order to get a full comprehensive view of your emissions data. Missing primary data – Some data may be very difficult to obtain, say from a supplier in a remote region, so in those cases you may need to make estimations to fill those gaps. However, you need to establish a proven and trusted methodology that can be repeated for such instances. Auditability and transparency – Your data needs to be robust enough to hold up to scrutiny in an audit. New and upcoming regulatory requirements will have stricter rules around how you collect and report your emissions. We can see this in regulations such as SB 253 and 261 within CSRD that will affect businesses in California. There's a new focus on mandatory reporting as opposed to voluntary, so you will need to ensure your data is in a good place to be audited when this starts to effect other organisations globally. [07:30] What are the requirements for CSRD in California? There are two main climate bills coming into effect in California in 2026, these are SB-253 and SB-261, which are supported by CARB (California Air Resources Board). These two regulations affect businesses who are either doing business in, have employees located in, or selling products over a certain revenue threshold in California. Affected businesses will be required to report on their scope 1, 2 and 3 emissions. There isn't anything new in these regulations that we ...
    Más Menos
    44 m
  • #235 PUBLIC's 3-Month Journey towards ISO 9001, ISO 14001 and ISO 20000-1

    #235 PUBLIC's 3-Month Journey towards ISO 9001, ISO 14001 and ISO 20000-1
    Nov 12 2025
    An ISO project can typically be completed within 6 – 12 months depending on an organisations size and complexity. Anyone who's been through the process of ISO Implementation knows that there is a lot of work involved in that time span, from coordinating teams, gathering and creating documentation to auditing your processes. Now imagine doing that for 3 ISO Standards simultaneously within 3 months! Which is exactly what today's guest, PUBLIC, have achieved. While it's not a timeframe we recommend, their efforts deserve to be celebrated, and displays what good project management with dedicated individuals can accomplish. In this episode, Ian Battersby is joined by Biba Gonzalez, Senior Associate of Business Operations at PUBLIC, to discuss their 3-month dash to implement ISO 9001, ISO 14001 and ISO 20000-1, and explore the challenges and benefits experienced during the process. You'll learn · Who is Biba Gonzalez? · Who are PUBLIC? · What was the main driver behind ISO 9001, ISO 14001 and ISO 20000-1 Implementation? · What was the biggest gap identified during the Gap Analysis? · What did Biba learn from the experience of implementing 3 standards at once? · What are the main benefits of ISO 9001, ISO 14001 and ISO 20000-1? · Biba's top tip Resources · PUBLIC · Isologyhub In this episode, we talk about: [02:05] Episode Summary – Ian is joined by Biba Gonzalez, Senior Associate of Business Operations at PUBLIC, to learn more about their 3-month whirlwind journey towards ISO 9001, ISO 14001 & ISO 20000-1 implementation. [02:30] Jumping in at the deep end: Biba was tasked with obtaining certification to 3 ISO Standard on returning from maternity leave in July 2025. PUBLIC already held ISO 27001 certification, but were looking to achieve ISO 9001 & ISO 14001 before Christmas of 2025. This was quite the task, especially since Biba had no previous experience with ISO Standards! [04:15] Who is Biba? Biba is the Senior Associate of Business Operations at PUBLIC. She has been the driving force behind PUBLIC's ISO 9001, ISO 14001 and ISO 20000-1 implementation. One fact that not many people might know about her is that she has had a private audience with the pope, by complete accident! Simply a case of wrong queue at the right time while on a family vacation. [06:50] Who are PUBLIC? PUBLIC are a digital transformation partner. They work within the private sector to help improve public services, by providing procurement services, online safety programmes and other digitally enabled services. [08:00] What were the main drivers behind achieving ISO 9001, ISO 14001 and ISO 20000-1?: PUBLIC work with a number of Government departments, and while bidding for various frameworks they noticed a trend in requests for bidding companies to have ISO 9001 and ISO 14001 certification. While not always a strict requirement, it was certainly a desirable trait that was preferred of bidding companies. There's also an increasing number of tenders asking for more environmental requirements, such as carbon emission reporting. What used to be a 'nice to have' is now becoming a requirement, and PUBLIC sought to have these requirements met via the relevant ISO Standards. [09:40] A tight timescale: When Biba had arrived back from maternity leave in July, PUBLIC has already booked in assessment dates with a Certification Body. This left quite a tight timeline of just 3-months to get all 3 Standards implemented to a level that could pass a Stage 1 Assessment. They already had an ISO 27001 system in place, but there was still a lot of work to do. A lot had been discussed about the implementation of additional standards in Biba's absence, but no practical steps had been taken aside from booking the audit dates. She certainly had her work cut out for her as most ISO project typically last between 6 – 12 months! Due to all her hard work, and some assistance from Blackmores, PUBLIC passed their Stage 1 assessment with flying colours and are in a good place to tackle their Stage 2 Assessment in late November 2025. [11:40] What was the biggest gap identified during the Gap Analysis? Thankfully PUBLIC didn't have any huge gaps to fill. Due to their previous work with Government departments, they had a lot of the pieces just not together in a cohesive system. They did identify early on that they wanted a system that worked for them in the long term and were conscious of creating something that fit their way of working. With so many ISO Standards, the upkeep alone would have been overwhelming so they aimed to combine as much as they could into one Business Management System rather than opting to silo each individual Management System. [13:00] What were the benefits of Implementing ISO 9001, ISO 14001 & ISO 20000-1? Biba states that the implementation of these ISO Standards took their business to the next ...
    Más Menos
    26 m
  • #234 Finding The Root Cause In ISO Management

    #234 Finding The Root Cause In ISO Management
    Oct 30 2025
    Continual Improvement is at the heart of ISO Management, a large part of which is dedicated to ensuring issues don't reoccur. This is more than just putting a plaster on it and calling it a day, it's about finding the root cause. This not only eliminates wasted time, effort and money with firefighting repeated mistakes, but also drives meaningful improvement. Over the years, many techniques have been developed to help with finding cause. In this episode, Ian Battersby explores the need to find the root cause of issues in ISO Management and explains some key techniques for root cause analysis that you can put into practice to help stop recurring issues. You'll learn · What is meant by 'finding cause'? · Why do you need to find the cause? · Where is finding cause specified in ISO Standards? · Finding cause in practice · What are the 5 Why's? · What is the fish bone / Ishikawa? · What is FMEA? · What is fault tree analysis? · How do these techniques work in practice? Resources · Isologyhub In this episode, we talk about: [02:05] Episode Summary – Ian dives into finding cause within ISO Management, explaining various techniques to help you prevent recurring issues. [03:15] What is meant by 'Finding cause'? When an output from a process is not what was expected, then it is classed as a non-conformity which will need to be addressed through corrective action. Before you can put that action into place, you need to identify the root cause for the issue. It's about putting right what went wrong. [04:00] Why do you need to find cause? Ian gives an example of a reactive response to resolving an issue, it didn't get to the root of why the mistake happened in the first place. Finding cause is necessary to stop issues from repeating, rather than simply firefighting issues as they occur. ISO terminology has updated to reflect this over the years. There used to be a term called 'Preventive action', but this has since been changed to 'Corrective action' following on from the 2015 Annex SL update to many ISO Standards. This reflects the new risk-based approach to ISO management. The terms are largely the same in nature, but preventive action was widely misunderstood and so this was renamed and clarified following 2015. [05:55] Where is finding cause specified in ISO Standards? As with many aspects of ISO, the need for finding cause can be found in a few places within a Standard, including: - Clause 6.1.1 Planning: It specifies the need to determine risks and opportunities that need to be addressed. This is because they will affect the desired outcome of your Management System. It's also a good place to start thinking about how to reduce those risks. Evaluating your strengths and weaknesses also gives you the chance to contemplate whether your existing processes are good at delivering what you want. Clause 10 Improvement: The Standard states something to the effect of 'the organisation shall determine and select opportunities for improvement and implement any necessary actions to address those opportunities' These opportunities will focus on improving products and services, which includes correcting, preventing or reducing undesired results. Also included under clause 10 is a subclause that directly addresses non-conformities and corrective action. These specify not only the need to resolve issues as they arise, but to evaluate the need for action to eliminate the root cause. Additional requirements include the need to review these actions and determine if they are actually effective. Ian goes into Clause 10 in more detail in a previous podcast specifically looking at opportunities for improvement. [14:20] Finding cause in practice – Why a methodology is necessary: Ian provides an example where an employee may lack confidence completing a certain activity. Their lack of competence could lead to a process being delivered incorrectly. That adverse quality outcome would then likely end up with the customer who would raise a complaint, in this instance that could be a damaged product. The damaged product is what needs correcting, from your perspective you would be looking at what caused that to prevent recurrence. Without knowing the initial cause, you would need to determine whether it's a production issue or a human error. These types of scenarios can branch out further than the initial quality issue. For example, if that damaged product causes harm, then it turns into a health & safety risk. If products need to be scrapped, then there's an environmental factor. Complaints related to product quality may also not be recorded in a standard non-conformity system, and could easily be missed for a full investigation to find root cause. This is why it's important to have a consistent approach, in both logging issues and evaluating them to determine cause. [18:10] What ...
    Más Menos
    37 m
Todavía no hay opiniones