One system. Several signals. One coordinated decision.
A solution combines several observations into one condition decision. It starts with the asset and credible failure modes, then selects complementary methods so one ambiguous indicator is not allowed to drive the conclusion.
For generator condition assessment solutions, that means beginning with stator and rotor indicators, working in the context of industrial synchronous generators, and preserving enough evidence to support generator condition overview.
Engineering boundary
A condition assessment supports maintenance decisions; it does not replace protective systems, code compliance, original-equipment-manufacturer limits, or an engineering study required by the site.
Condition record
What should support the system-level conclusion.
The asset, audience, or system boundary and the decision being supported
The relevant operating state, access conditions, source records, and known limitations
The observations or results related to insulation and discharge behavior
The comparison, technical reasoning, confidence, priority, and alternative explanations
The owner, timing, verification method, and trigger for escalation or follow-up
Challenge the diagnosis
What reviewers should test before action.
Was the evidence collected under a representative and documented condition?
Does another indicator support—or conflict with—the first conclusion?
Could access, setup, data quality, environment, or operating state explain the result?
Is the proposed action proportionate to condition, consequence, and uncertainty?
What new evidence would confirm that the action worked?
Evidence architecture
How the signals are assembled into a defensible conclusion.
The value comes from the relationship between evidence—not the number of technologies used.
01
Review duty, machine design, history, and outage constraints