How Site-Specific Forms in KYRO AI Run Monthly Inspections at 10 LS Power Substations | KYRO Case Study

October 27, 2026
5 min read
November 4, 2026
Team KYRO
Team KYRO
Content Team @ KYRO AI

Substations operate on a strict, fixed inspection schedule. However, no two sites ever have the exact same equipment. When field teams rely on a single generic checklist, program managers immediately lose visibility in three critical areas.

  • Tracking the equipment that is unique to each site
  • Finding the actual problems since they get buried in messy free text
  • Generating a report in the specific format each site requires.

At LS Power, KYRO AI runs comprehensive monthly inspections across 10 substations using forms built specifically for each site's unique equipment. Inspectors only write detailed notes when something is actually wrong. Known equipment values automatically fill in from the asset record, and every site generates reports in its own required format.

Ten Sites, Ten Sets of Equipment

LS Power is a transmission owner currently running three major field programs in KYRO AI: vegetation management and structure upkeep, transmission line construction, and substation inspections. Their substation program covers 10 sites across four different operating groups, with each location requiring a thorough monthly inspection.

Since every substation houses its own specific set of equipment, a generic checklist simply does not work. Certain sites require specialized inspections that others do not need at all. LS Power needed inspection forms mapped directly to each site. They also needed a system where inspectors only document details when a physical problem exists, ensuring every final report comes out in the exact format that specific site requires.

What Site-Specific Forms in KYRO AI Made Visible

Inspectors now complete forms built exclusively for the substation they are standing in. KYRO AI fills in what is already known directly from the asset record and produces each site's final report from its own custom template.

  • A Project per Substation: Each substation is set up as its own project in KYRO AI, holding all of its specific assets. Every inspection becomes a task with a custom form. Task names use a short site prefix, letting managers instantly see which site and inspection they are looking at.
  • The Right Inspections at Each Site: All 10 substations use the standard Front and Back, Battery, and Pre-Task Analysis forms. Sites that need extra checks get what they need. Six sites run an SPCC (Spill Prevention, Control, and Countermeasure) inspection, and two sites run a Defensible Space checklist with its own custom form and report.
  • Findings That Stand Out: If an inspector marks an item "OK" on the Front Inspection, notes are just optional. But if they mark it "Not OK," the system requires them to log the specific issues, actions taken, priority level, and affected assets. This keeps real problems from getting lost in long blocks of free text.
  • Values Pre-Filled From the Asset Record: The system pulls known information directly from the asset record so inspectors don't have to retype it. Battery inspections automatically fill in the bank type, manufacturer, and a default 60-cell count, while Back Inspections automatically pull in breaker serial numbers.
  • Reports in Each Site's Format: Front and Back and SPCC reports are generated using a custom template unique to each substation, while Battery and Pre-Task Analysis reports share a common layout. Front and Back reports always highlight the exact problems and actions taken, and they only show extra notes and affected assets if the inspector logged them.

What the Data Showed

  • Monthly inspection forms and reports successfully running at 10 substations, with each form built entirely around that site's actual equipment.
  • Inspectors writing detailed notes only for items marked "Not OK", ensuring every finding in a report is something that genuinely requires attention.
  • Battery and breaker details pulled instantly from the asset record instead of being manually re-typed on every single visit.
  • Every site's final report produced automatically in its own exact format, pulling from either a per-site or shared template.

Why This Matters

Substation inspections are highly routine by design. The primary risk is that this routine devolves into mindless box-ticking. A form might get filled out perfectly every month, but the one critical finding that actually matters fails to stand out from the noise.

LS Power's new approach keeps the routine extremely light while making the exceptions highly visible. Inspectors easily confirm what is working fine and write detailed notes only where something is actually broken. In turn, each site's report automatically puts those specific exceptions right up front.

Across 10 substations, every monthly visit now ends with a clean, accurate record built specifically for that site and focused entirely on what needs attention.

Are you tired of trying to force generic checklists onto highly unique substations? Let us show you a better way. Register for a Webinar to see how KYRO AI handles site-specific inspections and reports.

Frequently Asked Questions

How does KYRO AI handle substations with different equipment?‍

Each substation operates as its own project with its own specific assets and forms. Every site runs the core inspections like Front and Back, Battery, and Pre-Task Analysis. Sites that require them simply add an SPCC Inspection or a Monthly Defensible Space Inspection Checklist to their workflow.

How does KYRO AI keep substation inspections short?‍

Items marked "OK" need only optional notes, meaning full detail is required only for items marked "Not OK". Furthermore, known values like battery type, manufacturer, and breaker serial numbers fill in automatically from the permanent asset record.

Can KYRO AI produce reports in each substation's own format?‍

Yes. Front and Back and SPCC (Spill Prevention, Control, and Countermeasure) reports use a custom template tailored for each specific substation, while Battery and Pre-Task Analysis reports share one common template. Notes and affected assets only appear in a final report when the inspector explicitly enters them.

‍

Author

This blog was written by Team KYRO, bringing together the expertise of KYRO’s product, engineering, and industry teams. Our content is shaped by hands-on experience, offering practical insights grounded in real operational challenges.

View all posts

Discover more related blogs.