Substation Anomaly Detection Agent Implementation Brief

Role: Senior Utility Reliability Engineer and Industrial IoT Agent Specialist with deep expertise in transmission asset health management.

Context

• Infrastructure operator: {{utility_operator}}
• Asset class under monitoring: {{substation_class_type}}
• Primary sensor telemetry modalities: {{sensor_telemetry_streams}}
• Allowable false-positive error rate: {{false_positive_tolerance}}
• Maintenance dispatch workflow: {{incident_escalation_protocol}}
• Hardware deployment environment: {{edge_compute_envelope}}

Task

Formulate an operational implementation brief defining the agent architecture, edge inference rules, alert suppression logic, and work-order dispatch protocols for an anomaly-detecting maintenance agent monitoring {{substation_class_type}} assets.

Method

1. Analyze {{sensor_telemetry_streams}} ingestion requirements against compute constraints defined by {{edge_compute_envelope}}.
2. Design the agent's multi-sensor fusion reasoning loop to evaluate physical degradation signals without saturating edge bandwidth.
3. Formulate signal confidence thresholds that satisfy the stringent {{false_positive_tolerance}} requirements.
4. Define the tool execution contracts the agent uses to query historical asset maintenance records and SCADA logs.
5. Establish automated work-order generation rules adhering strictly to {{incident_escalation_protocol}}.
6. Detail self-monitoring diagnostics ensuring the agent flags its own degraded sensor inputs or edge hardware failures.
7. Map the handoff protocol between autonomous agent diagnosis and field inspection crew dispatch.

Constraints

• MUST keep edge inference processing within the computational limits of {{edge_compute_envelope}}.
• MUST NOT grant the agent direct write-access to primary protection relays or breaker trip circuits.
• All maintenance recommendations must cite specific sensor signature anomalies.
• Output must use unambiguous industrial utility maintenance terminology.

Output format

Produce a structured implementation brief organized as follows:

• Section 1: Edge Operational Objectives & Hardware Constraints
• Section 2: Multi-Modal Telemetry Ingestion & Fusion Pipeline
• Section 3: Diagnostic Logic & False-Alarm Suppression Rules
• Section 4: CMMS Integration & {{incident_escalation_protocol}} Workflow
• Section 5: Risk Analysis and Fail-Safe Telemetry Fallbacks Word count must fall between 650 and 950 words.

Self-review

• Confirm that direct protection relay tripping is explicitly forbidden in the brief.
• Validate that all items listed in {{sensor_telemetry_streams}} are integrated into the diagnostic method.
• Ensure clear distinction between local edge inference and upstream utility cloud synchronization.