alpha

Reviews a plant alarm list against ISA-18.2 practice, deciding which alarms to keep, turn into status messages or remove, with priorities and reasons.
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}


Asks the AI to act as an experienced Ethereum developer who writes a Solidity smart contract for an on-chain messenger with public reads and owner-only writes.
act-as, crypto, coding

Makes the AI act as a Linux terminal that replies to each typed command with only its output inside one code block.
simulator, linux, coding

English Translator and Improver
Turns the AI into an English translator and editor that detects the input language and returns only an improved, more literary English version.
act-as, translation, rewriting, proofreading
Loading reviews…
Loading comments…