복잡한 공정 알람을 국제 표준(ISA-18.2)에 맞춰 효율적으로 정리
I want you to act as an alarm management specialist. Machine or process: ${Machine or process}. Below is the current alarm list, plus alarm history if I have it.
Rationalize it in the spirit of ISA-18.2 / IEC 62682. For each alarm give:
Alarm | Keep as alarm / Make it a status message / Remove | Cause | Consequence if ignored | Operator action | Relative priority | Reset condition | Reason
Rules:
1. If there is no operator action, it is not an alarm.
2. Use only equipment and causes in my list. Do not invent alarms.
3. Base priority on consequence and how much time the operator has to respond, and state the basis.
Then list:
- Duplicates: one root cause raising several alarms, with which one to keep.
- Chattering or nuisance alarms from the history, with the fix (deadband, on-delay, latch, suppression by state).
- Causes with no alarm at all.
- For each alarm kept, a one-line alarm text in the pattern: where, what, consequence, action.
=== ALARM LIST ===
${Paste alarm list}
=== ALARM HISTORY (optional) ===
${Paste history or write NONE}당신은 알람 관리 전문가입니다. 대상 장비/공정: [장비 또는 공정]. 아래 알람 리스트를 ISA-18.2 / IEC 62682 표준에 따라 합리화하십시오. 각 항목에 대해 다음을 제공하세요: 알람명 | 유지 여부(알람/상태 메시지/삭제) | 원인 | 무시 시 결과 | 운영자 조치 | 우선순위 | 리셋 조건 | 근거 [규칙] 1. 운영자의 조치가 필요 없는 것은 알람이 아닙니다. 2. 리스트에 있는 장비와 원인만 사용하고 알람을 지어내지 마세요. 3. 결과의 심각성과 대응 시간을 기준으로 우선순위를 정하세요. [추가 분석] - 중복: 하나의 원인으로 발생하는 여러 알람 중 남길 것 제안 - 노이즈 알람: 빈번하게 울리는 알람에 대한 수정 방안(지연시간 등) - 알람 텍스트: '위치, 현상, 결과, 조치' 패턴으로 한 줄 정리 === 알람 리스트 === [리스트 붙여넣기] === 알람 히스토리 === [히스토리 또는 NONE]
출처 · prompts.chat · Alarm Rationalization Assistant — 원문은 출처에 게시된 그대로이며, 권리는 원작자에게 있습니다.
Gemini로 실행한 결과입니다. 입력 항목에는 국내 환경의 예시값을 적용했습니다(AI 생성 — 사실 확인 필요).
I want you to act as an alarm management specialist. Machine or process: 반도체 웨이퍼 세정 설비 (Wafer Cleaning System). Below is the current alarm list, plus alarm history if I have it. Rationalize it in the spirit of ISA-18.2 / IEC 62682. For each alarm give: Alarm | Keep as alarm / Make it a status message / Remove | Cause | Consequence if ignored | Operator action | Relative priority | Reset condition | Reason Rules: 1. If there is no operator action, it is not an alarm. 2. Use only equipment and causes in my list. Do not invent alarms. 3. Base priority on consequence and how much time the operator has to respond, and state the basis. Then list: - Duplicates: one root cause raising several alarms, with which one to keep. - Chattering or nuisance alarms from the history, with the fix (deadband, on-delay, latch, suppression by state). - Causes with no alarm at all. - For each alarm kept, a one-line alarm text in the pattern: where, what, consequence, action. === ALARM LIST === 1. DI Water Supply Low Pressure (DIW_LP_01) 2. Chemical Tank A High Temp (CH_TA_TH_01) 3. Front Door Open (DOOR_01) 4. Recirculation Pump Running (P1_RUN) 5. Main DI Water Feed Pressure Low (MAIN_DIW_LP) === ALARM HISTORY (optional) === - CH_TA_TH_01: 10분 내 50회 발생 및 해제 반복 (임계값 근처 데이터 노이즈). - DIW_LP_01와 MAIN_DIW_LP는 항상 동시에 발생함.
ISA-18.2 지침에 따른 알람 합리화 분석 결과입니다.
[Alarm Text Pattern]
원문과 같은 언어로 보완한 프롬프트입니다. 점수는 명확성 · 구체성 · 출력 형식 · 재사용성 기준의 AI 평가입니다.
You are an expert alarm management specialist following ISA-18.2 / IEC 62682 standards. Target system: [Machine or process]. Rationalize the provided alarm list and history. For each alarm, provide: Alarm | Classification (Keep/Status/Remove) | Cause | Consequence | Operator Action | Priority (with basis) | Reset Condition | Reason. Rules: 1. No operator action means not an alarm. 2. Use strictly provided equipment/causes without invention. 3. Base priority on consequence and response time. Afterward, list: Duplicates (root cause and chosen alarm), Chattering/nuisance alarms with fixes (deadband, delay, latch, suppression), Uncovered causes, and One-line text for kept alarms formatted as [where, what, consequence, action]. Output in a clean markdown table and bullet points.
=== ALARM LIST ===
${Paste alarm list}
=== ALARM HISTORY (optional) ===
${Paste history or write NONE}