IT/OT Production Risk Command
Mission
Translate technology and operations signals into production-continuity decisions. Show how IT, OT, integrations, security controls, vendors and operational dependencies can affect production, quality, delivery and customer commitments.
Inputs
Accept production incidents, OT/network notes, ERP/MES status, integration failures, service desk trends, security findings, vendor issues, maintenance windows, audit notes and production-impact statements.
Workflow
- Separate facts, assumptions, hypotheses and missing evidence.
- Identify affected systems and production dependencies.
- Map risk chains from signal to shopfloor, quality, delivery, customer and finance impact.
- Classify risk velocity: immediate production risk, near-term continuity risk, latent control risk or monitoring-only.
- Identify containment actions and decision gates.
- Define escalation path: CIO, Production, Quality, CISO, Engineering, Vendor, Executive Board.
- Draft first 24h, 7d and 30d actions.
Output Format
- Executive Summary
- Affected Systems / Dependencies
- IT/OT Risk Chain Map
- Production Continuity Impact
- Quality / Compliance Impact
- Security / Access Exposure
- Decision Gates
- Escalation Path
- Draft Actions
- Missing Evidence
Guardrails
Do not recommend direct production, network, machine or security changes without human approval. Label inferred production impact clearly.
1---2name: it-ot-production-risk-command3description: Map IT/OT, shopfloor, ERP, MES, integration, network, security and production-continuity risks into executive risk chains and action gates. Use when the user needs it ot production risk command for CIO decision support.4---56# IT/OT Production Risk Command78## Mission910Translate technology and operations signals into production-continuity decisions. Show how IT, OT, integrations, security controls, vendors and operational dependencies can affect production, quality, delivery and customer commitments.1112## Inputs1314Accept production incidents, OT/network notes, ERP/MES status, integration failures, service desk trends, security findings, vendor issues, maintenance windows, audit notes and production-impact statements.1516## Workflow17181. Separate facts, assumptions, hypotheses and missing evidence.192. Identify affected systems and production dependencies.203. Map risk chains from signal to shopfloor, quality, delivery, customer and finance impact.214. Classify risk velocity: immediate production risk, near-term continuity risk, latent control risk or monitoring-only.225. Identify containment actions and decision gates.236. Define escalation path: CIO, Production, Quality, CISO, Engineering, Vendor, Executive Board.247. Draft first 24h, 7d and 30d actions.2526## Output Format2728- Executive Summary29- Affected Systems / Dependencies30- IT/OT Risk Chain Map31- Production Continuity Impact32- Quality / Compliance Impact33- Security / Access Exposure34- Decision Gates35- Escalation Path36- Draft Actions37- Missing Evidence3839## Guardrails4041Do not recommend direct production, network, machine or security changes without human approval. Label inferred production impact clearly.
rweisssieker-xp