Back to prompt library
Build a Plant Subnet Isolation and Automation State Recovery Drill Engine — implementation
Linked challenge: Build a Plant Subnet Isolation and Automation State Recovery Drill Engine
Prompt source
implementation83 lines11 sectionsNo variables1 code block
## Build
Analyze simulated open62541 network connectivity timeouts. Generate plant floor drill plans to verify backup automation safety interlocks when primary SCADA connections drop.
## User
Factory Automation Infrastructure Engineer
## Workflow
1. Ingest simulated open62541 connection timeout events and heartbeat failures from factory floor PLCs.
2. Map connection drops to affected production zones and primary SCADA blind spots.
3. Formulate an operator drill sheet to physically verify fail-safe shutdown states on isolated machines.
4. Export a drill report template to capture verification times and manual override activation.
## Interface
Drill simulation console showing active SCADA connection drops and operator physical checklist assignments.
## Data
Create synthetic JSON files simulating open62541 heartbeat failures and connection status variables. Host locally.
Starter examples below are synthetic. They are not downloaded records.
## Source
[open62541 OPC UA](https://raw.githubusercontent.com/open62541/open62541/master/README.md)
Network connection status variables and heartbeat monitoring defined within the open62541 OPC UA architecture.
## Tools
semantic-kernel, pydantic, fastapi.
Semantic Kernel enables structured prompt chaining to translate communication timeout events into sequential physical verification drills.
Instruction-tuned reasoning model capable of technical procedure formulation and dependency validation.
## Deliverables
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
## Acceptance
- Correctly maps connection timeouts to affected production zones.
- Identifies required fail-safe conditions based on isolated machines.
- Validates that the drill tasks explicitly require physical verification of isolated states.
## Starter Examples
```json
[
{
"input": {
"zone": "PRESS_LINE_1",
"plc_nodes": [
{
"node_id": "ns=1;s=Press_Master",
"status": "TIMEOUT",
"last_heartbeat": "10s_ago"
}
],
"fail_safe_required": [
"Clutch_Disengaged",
"Power_Isolated"
]
},
"expected_output": {
"isolation_detected": true,
"affected_zone": "PRESS_LINE_1",
"drill_tasks": [
"Dispatch operator to PRESS_LINE_1",
"Verify Clutch_Disengaged indicator is active",
"Verify Power_Isolated padlock point is secured"
],
"estimated_drill_duration_min": 10
}
},
{
"input": {
"zone": "PRESS_LINE_2",
"plc_nodes": [
{
"node_id": "ns=1;s=Press_Slave",
"status": "CONNECTED",
"last_heartbeat": "1s_ago"
}
],
"fail_safe_required": [
"Clutch_Disengaged",
"Power_Isolated"
]
},
"expected_output": {
"isolation_detected": false,
"affected_zone": "PRESS_LINE_2",
"drill_tasks": [],
"estimated_drill_duration_min": 0
}
}
]
```
## Safety
Procedure rehearsal only. No live machine operations, network changes, or interlock overrides are executed.
Use mock external writes. Require human review before any real deployment.