Prepare useful information for the local request route

This page helps you describe a concern; it does not submit or track work.

Before using your site's approved work-request process, gather enough factual context for the receiving team to identify the equipment and understand what was observed. This page does not create a request, approve work, set priority, or show request status. For urgent or safety-sensitive concerns, follow the local approved escalation route and consult the responsible site role.

What to capture

Record what you know; do not infer a cause.

  1. 1

    Identify the asset and location

    Record the asset identifier if known, plant, line or area, and the equipment component involved. If identification is uncertain, say so.

  2. 2

    Describe the observation

    State what happened in specific terms, such as an intermittent stop, unusual indication, or visible condition. Avoid presenting an unverified explanation as fact.

  3. 3

    Add timing and operating context

    Note when the condition was observed, whether it recurred, and relevant operating context. Do not direct or attempt work outside approved procedures.

  4. 4

    Use the local handoff

    Enter the information through the locally approved work-request route. If the issue is urgent, safety-sensitive, or outside your role, follow the site's approved escalation process.

Worked example: describe the symptom, not the cause

Fictional Northstar Components example; it illustrates work coordination, not an equipment diagnosis.

Clear observation

“PKG-CV-204, Packaging Line 2: the conveyor stopped intermittently during product changeover on the second shift. The stoppage was observed twice; the equipment identifier and line are recorded for the local team to verify.”

  • Names an example asset and location.
  • Describes the event and timing context.
  • Does not claim why the stoppage occurred.

Unverified conclusion to avoid

“The changeover caused the conveyor failure.” This states a cause that has not been established by the observation alone.

  • Keep a hypothesis clearly labeled as a hypothesis.
  • Let the appropriate local review process assess cause.

Handoff and escalation

Use the work-request route approved for your location. The receiving local role determines the applicable intake, prioritization, and follow-up process. For urgent or safety-sensitive concerns, use the locally approved escalation route rather than relying on this general coordination page.