An OT-focused risk framework is already defined for water-plant entities. What should the administrator do so statements participate in that framework?

When an OT-focused risk framework already exists for water-plant entities, administrators must associate the relevant risk statements with that OT framework so generation and assessment follow the OT methodology. Statement-to-framework association is what places library content under the correct scoring, workflow, and scoping rules for industrial civic assets.

Publishing statements only as knowledge articles with no framework link leaves content informational and outside risk generation. Duplicating every statement into a spreadsheet named for the framework creates an unmanaged shadow library. Attaching statements exclusively to SIR playbooks misfiles risk library content into incident response constructs.

Exam caveat: knowledge articles and SIR playbooks are not risk-framework associations. CIS-RC configuration items expect statements linked to the intended risk framework.

Operational check: open OT statements; verify framework association to the water-plant OT risk framework; generate a risk for a plant entity and confirm the OT methodology drives scoring; remove any spreadsheet shadow copies from the operating procedure.

In civic OT programs, framework association also determines which appetite rules, assessment questionnaires, and reporting categories apply when water-plant risks generate. Treat statement-to-framework linkage as a release gate before mass generation: if the OT framework is missing, stop and fix association rather than generating under a generic IT methodology that mis-weights industrial impact. Document the association in the municipal IRM runbook so future statement imports inherit the same OT playlist automatically.