Understand the interface decision

The controller influences rotor acceleration and operating speed through generator torque or power demand. The suitable relationship depends on the turbine and generator configuration and on the control architecture. A table copied from another rotor may therefore produce a different operating trajectory even when both machines share a rated power.

Control performance depends on signal meaning, timing and the approved operating limits. Keep normal optimization separate from protective constraints, and identify which function owns each decision. The selected turbine and controller documentation must define the actual settings.

Put these inputs in the review record

Use a project-specific worksheet to capture the following information. For each entry, name the document, revision and person responsible for resolving any uncertainty.

• The approved turbine and generator configuration behind the curve. Identify the exact configuration and the supporting document.
• The independent and commanded variables, units and sign conventions. Keep the design assumptions visible in the project record.
• Startup, normal optimization and limiting regions of the map. Name the responsible reviewer and resolve any missing information.
• The version and validation evidence for the implemented relationship. State how this entry will be verified during acceptance.

Define the acceptance boundary

Accept the map only when its definitions and configuration match the system being integrated. Keep protective limits distinct from the optimization curve. An apparently smooth power trend does not establish that rotor loading stays within every mechanical or electrical limit.

The useful deliverable is a versioned relationship with clear axis definitions and region boundaries. It should allow reviewers to distinguish a change in optimal loading from a change in an independent protection limit.