Write your awesome label here.
Measure a real AI workload end to end, and record every number so it can be checked.
A hands-on measurement lab covering SCI and SCI for AI, four measurement approaches: research estimates, provider data, your own or third-party estimation models, and direct measurement, plus intensity, embodied impact, boundaries and reporting.
11h 10m
14
30 question
80%
Certification
SCI for AI Practitioner: The Measurement Lab
How the course works
A lab, not a lecture
You measure a real workload end to end, then compare the approaches against each other.
Evidence recorded as you go
Method, level, boundary and date on every number, which is what makes a figure defensible later.
Built on the ratified specification
SCI (ISO/IEC 21031) and SCI for AI, cited precisely, with pathway status stated.
What this course helps with
Answer the second question
"What does it include?" is where most footprint figures come apart. The boundary discipline is the core of the course.
Interpret provider data
What a vendor figure covers, what it omits, and how to use it without overstating what it says.
Explain why tools disagree
Four approaches, different results, and a way to reconcile and explain the gap. The energy and carbon figure you publish is the one that holds when a reduction is claimed against it.
Who this is for
- Engineers, architects and sustainability practitioners producing AI footprint figures
- Practitioners preparing figures for disclosure
- Anyone answering customer, audit or regulatory questions about AI impact
Related courses:
To govern measurements rather than produce them, Green AI for Executives covers the leadership view.
What you will work with
One score, four inputs
The SCI structure applied to AI, with the functional unit treated as the decision it is.
The reconciliation
Why four approaches disagree, and how to explain the difference.
Boundaries and the register
What is in, what is out, and where it is recorded for the next person.
What you will be able to do
Course Lessons
The full course
01
Why Water, and Why You
Software feels dry, but the buildings it runs in use water for cooling, the electricity it consumes was made using water, and the hardware was manufactured with it. This module shows those three connections and closes the gap between the people who can see the water and the people who change the software.
module-01
02
The Four Layers: building, electricity, hardware, and the stress conversion
This module gives the three ways software uses water their proper names, as the draft SWI specification uses them, and adds a fourth layer that converts litres into how much each litre matters. It ends with the only line of arithmetic in the course.
module-02
03
Consumption and Withdrawal: used up vs borrowed
Water figures come in two kinds, and confusing them is the most common mistake in reading them. This module teaches the distinction between water used up and water borrowed and returned, and the rule that the two are never added together.
module-03
04
Reading a Water Number
This module teaches no calculations. It teaches how to look at any water figure, whether a provider report, a news headline or a colleague’s slide, and know what it does and does not say.
module-04
05
Stress-Adjusted Water: a liter is not a liter
The same liter counts for more where water is scarce and for less where it is plentiful. This module turns that idea into arithmetic using a published factor per place, giving the conversion layer its full treatment at foundation depth.
module-05
06
Small Things That Save Water
The earlier modules built a vocabulary; this one turns it into actions small enough to take this week, organised by role. None of them needs a water meter, a budget or permission to run a project.
module-06
07
Final Assessment
A final assessment of 12 questions - 80% to pass, 30 minutes, retake available.
Final Assessment
Assessment & Certification
Time to complete