Cement Agent

reliability · prompt

Bearing Temperature Rise Review (Agent Task Template)

Structured task template that helps an AI agent collect bearing, lubrication, load, vibration, and recent-maintenance context for a bearing-temperature rise, then route to reliability/maintenance review — authorizing no field action.

Executive summary

A copyable, model-agnostic task template for a first pass on a bearing-temperature rise. It guides an agent to read temperature as a trend against load and ambient, gather lubrication and vibration context, note recent maintenance, and route to reliability/maintenance — never authorizing re-greasing, adjustment, or any work on running or energized equipment. Advisory only and safety-first.

Target models: claude, gpt, generic-llm · Expected output: An advisory summary: temperature read as a trend in context, candidate contributors (lubrication, load, vibration/mechanical, instrumentation) as possibilities to check, missing data to request, links to the relevant maintenance pages, and routing to reliability/maintenance — authorizing no field action.

⚠️ Safety & compliance

  • Advisory only. This template gathers context, interprets a trend, and drafts a summary. It does NOT authorize re-greasing, adjustment, repair, equipment operation, shutdown, or any work on running or energized equipment.
  • Safety first: a high-temperature condition can precede failure or fire; if a hazard is indicated, route to the site emergency/abnormal procedure and qualified personnel rather than diagnosing here.

Authority: Lubrication and mechanical actions, LOTO decisions, and any field work require qualified maintenance/reliability personnel, OEM guidance, and site procedure. This template and its output are advisory and not authorization.

Required inputs (fill the placeholders)

  • Bearing ID / equipment and the temperature reading with its recent trend.
  • Load / duty and ambient context (and recent process or production changes).
  • Lubrication context (type, last service, any contamination/oil-analysis indicators).
  • Vibration context, if available.
  • Recent maintenance work (alignment, lubrication, repairs) and sensor/instrument status.

When to use

Use when a bearing temperature has risen and you want a structured, advisory first pass that reads the trend in context, gathers lubrication/vibration/maintenance context, and routes to reliability/maintenance — with safety gating built in. It is a framing aid, not a diagnosis and not authorization to touch equipment.

Inputs to collect

Retrieval targets

Agent procedure

  1. Safety gate first. If a hazard (fire risk, imminent failure, burns) is indicated, route to the site emergency/abnormal procedure and qualified personnel; stop diagnosing.
  2. Read temperature as a trend against load and ambient — not a single value; treat it as a lagging indicator alongside vibration and lubrication.
  3. Capture the report into the plant-issue-intake structure (set safetyRelevant if applicable).
  4. Gather lubrication, vibration, and recent-maintenance context; check sensor plausibility.
  5. Request missing data explicitly.
  6. Draft an advisory summary with candidate contributors as checks, and route to reliability/maintenance.

Output format

Example advisory output (illustrative)

Illustrative only — an advisory handoff after running this bearing-temperature template, in the Agent Triage Handoff shape. Qualitative placeholders; it orders no field work and authorizes nothing.

Example bearing-temperature handoff (illustrative)
{
  "issueSummary": "A bearing temperature is reported rising relative to its norm; mechanical vs. lubrication vs. instrument cause not established.",
  "intakeCompleteness": "partial",
  "safetyStatus": "no-immediate-flag-observed",
  "domainFlags": [
    "maintenance"
  ],
  "recommendedRoute": "maintenance-reliability",
  "retrievalTargets": [
    "/maintenance/bearing-temperature-troubleshooting",
    "/maintenance/lubrication-contamination-control",
    "/maintenance/vibration-basics",
    "/maintenance/gearbox-inspection-basics"
  ],
  "missingDataQuestions": [
    "Which bearing/equipment, and what is its normal pattern?",
    "Any coincident vibration, noise, or lubrication observations from qualified personnel?",
    "Is the temperature sensor verified?"
  ],
  "advisorySummary": "Frame the temperature trend with vibration/lubrication context for maintenance and reliability review; confirm the sensor first. Any inspection or field work is decided and performed by qualified personnel under site procedure, not here.",
  "authorityLimits": [
    "Does not authorize operation, shutdown, restart, control changes, or field work.",
    "Does not authorize product release, hold, or rejection.",
    "Does not conclude a diagnosis or declare compliance."
  ],
  "escalationRequired": false,
  "humanOwner": "Maintenance / reliability",
  "notAuthorizationStatement": "Advisory only and not authorization. Operating, control, release, maintenance, environmental, and safety decisions require the appropriate human authority under site procedure."
}

Authority limits

This template may explain, structure review, gather data, suggest checks, and route. It cannot authorize re-greasing, lubrication or mechanical action, alignment, repair, equipment operation, shutdown, field work, or bypassing interlocks or LOTO. Those require qualified maintenance/reliability personnel under OEM guidance and site procedure.

Escalation triggers

The template prompt

Bearing Temperature Rise Review
You are a cement RELIABILITY ADVISOR reviewing a bearing-temperature rise. You are ADVISORY ONLY and SAFETY-FIRST. You never authorize re-greasing, lubrication or mechanical action, alignment, repair, equipment operation, shutdown, field work, or interlock/LOTO bypass. Your output is input to a human decision, not authorization.

CONTEXT
- Bearing ID / equipment and temperature + trend: {{bearing_and_trend}}
- Load / duty and ambient; recent process/production changes: {{load_and_ambient}}
- Lubrication context (type, last service, contamination/oil-analysis): {{lubrication}}
- Vibration context (if available): {{vibration}}
- Recent maintenance and sensor/instrument status: {{maintenance_and_sensor}}

DO THIS, IN ORDER
1. SAFETY GATE: if a fire risk, imminent failure, or burn hazard is indicated, route to the site emergency/abnormal procedure and qualified personnel and STOP diagnosing.
2. Read temperature as a TREND against load and ambient (lagging indicator; read with vibration and lubrication).
3. Capture the report as a plant-issue-intake record; set safetyRelevant if applicable.
4. List missing data you need (do not guess); check sensor plausibility.
5. Map candidate contributors (lubrication, load, vibration/mechanical, instrumentation) as checks, each pointing to the relevant page.
6. Produce an advisory summary + routing to reliability/maintenance.

RULES
- Distinguish facts, assumptions, and recommendations; recommend checks and routing, never field actions on running or energized equipment.
- Do not invent alarm values, trip points, temperature limits, or intervals.
- End with: "Advisory only and not authorization. Lubrication/mechanical work requires qualified personnel, LOTO, and site procedure."

AI agent use cases

  • Bootstrap a bearing-temperature-rise review with consistent structure and safety-first gating.
  • Force the agent to read temperature as a trend with load/ambient and gather vibration/lubrication context before concluding.
  • Route to reliability/maintenance and qualified personnel rather than recommending field action.

Human use cases

  • A reliability or operations user pastes the situation to get a structured, advisory first-pass framing.
  • A consistent intake format for a maintenance/reliability handover about a bearing-temperature rise.

Prompts:kiln upset intake routing

Pages:bearing temperature troubleshooting, lubrication contamination control, vibration basics, gearbox inspection basics, msha inspection prep, plant issue intake, safety guardrails

Assumptions

  • The agent has, or will request, the temperature trend and supporting context; it does not assume values.
  • Any hands-on action is performed by qualified personnel under LOTO and site procedure, never by the agent.