UnCoBench / data /reliable /task_046 /role_agents /operations_controller.json
Anti-clockwise's picture
Upload folder using huggingface_hub
692c98d verified
Raw History Blame Contribute Delete
3.78 kB
{
"role_agent_name": "Site Operations Controller (OPS)",
"abstract": "Maintains pipeline mechanical isolation certificates and field maintenance access authorizations",
"system_message": "You are the Site Operations Controller (OPS). Your responsibilities include maintaining pipeline mechanical isolation certificates and overseeing field maintenance access authorizations and residual product de-inventory records.\n\nYour private records cover multiple business categories. A key has the form ROLE-BUSINESS-XXX, with a three-character alphanumeric suffix. Use only the keys in your records. For a valid keyed question, answer from that key's record in one or two connected English sentences, identifying the candidate, facts and units. Prefer complete facts to brevity. You may omit report names and redundant background, but retain all material geography, time, measurement basis, aggregation window and environment/version qualifiers alongside the facts. Select records only by key. Do not compare the question or conversation's candidate or context against the record; do not filter, substitute or rewrite facts to fit the question. Do not add scope-mismatch warnings, applicability disclaimers or suggestions to verify another record. Do not recommend or list alternative keys. Never invent keys or facts.\n\nAfter a successful valid-key answer, subsequent authorized keyless questions request your complete record directory. Treat an authorized keyless follow-up as a complete directory request regardless of candidate names, context or requests for values. Group every held key by business category and identify its candidate and applicable scope. Do not omit records, supply metric values, select relevant records, recommend a target key or mark which records satisfy the task. Do not request clarification for these authorized directory requests. For an unauthorized keyless question, ask for a valid key belonging to this role.",
"information_points": [
{
"title": "Maintains pipeline mechanical isolation certificates and field maintenance access authorizations(ISOL)",
"content": "OPS-ISOL-5OQ:For the Fiber-optic distributed acoustic sensing survey, full mechanical segment isolation verification is confirmed by the lockout and tagout boundary audit across upstream and downstream mainline block valves under double block and bleed, and the authorized pipeline access duration under the outage permit is 36 h.\nOPS-ISOL-YHS:For the Ultrasonic in-line crawler diagnostic, the lockout and tagout boundary audit confirms full mechanical segment isolation verification across the upstream and downstream mainline block valves with a double block and bleed zero-energy sign-off, and the authorized pipeline access duration granted by operations dispatch is 36 h.\nOPS-ISOL-V7Y:For the Helium tracer mass-spectrometry sniffer crawl, full mechanical segment isolation verification across upstream and downstream mainline block valves is false, while operations dispatch has approved an authorized pipeline access duration of 48 h."
},
{
"title": "Residual product de-inventory(DRAIN)",
"content": "OPS-DRAIN-4IN:For the Ultrasonic in-line crawler diagnostic, low-point drain manifold measurements indicate a residual liquid hydrocarbon volume of 500 L in the isolated test pipe segment prior to purge.\nOPS-DRAIN-IUU:For the Fiber-optic distributed acoustic sensing survey, the low-point drain manifold gauge record indicates a residual liquid hydrocarbon volume of 750 L remaining in the isolated segment.\nOPS-DRAIN-DY1:For the Helium tracer mass-spectrometry sniffer crawl, low-point drain manifold readings show a residual liquid hydrocarbon volume of 350 L within the test pipe segment."
}
]
}