Browse Skills

EnMS Energy Review Author

    Get Started with This Skill

    Overview

    Guided elaboration of EnMS documentation for ISO 50001: energy review, baseline, EnPIs, objectives and action plans. Ensures baseline and EnPIs have scope and units and flags objectives without measurement method or review period.

    Getting Started

    Add your source materials to the project workspace, then activate the EnMS Energy Review Author skill. The agent will guide you through the process step by step.

    Example Conversation

    You: We’re setting up our EnMS for ISO 50001. I have energy data for the last 12 months. I need an energy baseline with scope and units, EnPIs, and objectives with a measurement method and review period.

    Agent: I’ll draft the energy review and baseline section (scope, period, units e.g. MWh or GJ) and run check_enpi_baseline on the document to ensure baseline and EnPIs have scope/units and objectives have measurement and review.

    Agent: The tool reported that the energy baseline section should include scope (boundaries, period) and units, and that EnPIs should have scope and units. It also flagged that energy objectives need a measurement method and review period. I’ve added a baseline definition (scope: Site A, period Jan–Dec 2024, unit MWh) and an EnPI table (e.g. MWh per tonne product; kWh per m² for buildings). For objectives I’ve added a “Measurement” and “Review” column (e.g. monthly data; management review quarterly).

    You: Add one more objective for renewable share.

    Agent: Done. Re-run check_enpi_baseline to confirm all warnings are cleared.

    Sample Output Excerpt

    Excerpt from EnMS documentation: baseline, EnPIs, and objectives.


    Energy baseline (6.4)

    • Scope: Site A (manufacturing and offices). Boundaries: meter points M1–M3.
    • Baseline period: January 2024 – December 2024.
    • Unit: MWh (electricity and gas converted to MWh).
    • Baseline value: 12,450 MWh (2024 total). Used as reference for EnPIs and objectives.

    Energy performance indicators (6.5) — excerpt

    EnPIDefinitionUnitNormalization
    Site energy intensityTotal energy / production outputMWh/tonneBy product line
    Building energyElectricity for officeskWh/m²/yearBy building

    Energy objectives (6.6) — excerpt

    ObjectiveTargetMeasurementReview
    Reduce site energy intensity−5% vs. 2024 baseline by 2026Monthly MWh and tonnes; EnPI calculated monthlyManagement review quarterly
    Increase renewable share30% of electricity by 2025Monthly green tariff / total electricityAnnual

    Built-in Validation Tools

    The skill includes an extension tool that checks EnMS documentation for baseline, EnPI, and objective coverage.

    What the tool checks

    Checkcheck_enpi_baseline
    Energy baselineDetects baseline, 6.4; looks for scope, boundary, period, unit, MWh, GJ, kWh
    EnPIsDetects EnPI, energy performance indicator, 6.5; looks for scope, unit, normalization
    ObjectivesDetects objective, target, 6.6, action plan; looks for measurement, review period, metric, KPI
    FindingsWARNING if baseline lacks scope/units, EnPIs lack scope/units, or objectives lack measurement/review; INFO when complete

    Example validation output

    ======================================================================
    EnMS ENPI & BASELINE COVERAGE REPORT
    ISO 50001:2018
    ======================================================================
    Document: docs/enms-manual.md
    
    --- FINDINGS ---
      [WARNING] Energy objectives should have a measurement method and review period. Define how progress will be measured and when objectives are reviewed.
      [INFO] Document includes baseline, EnPIs, and objectives; verify scope, units, and review periods are complete.
    
    --- SUMMARY ---
      Errors: 0
      Warnings: 1
    ======================================================================
    

    Run the tool on your energy review, baseline, EnPI, or objectives document after drafting or updating.

    Ready to let your expertise drive the workflow?

    Stop wrestling with rigid templates and complex tooling. Write your process in markdown, let the agent handle the rest.

    Get Started