Skip to main content

Maintenance

Maintenance staff start their day from Today's Tasks on the Ask home screen and Suggestions › To-do › Sudden Issues (anomaly to check · incident). Below are common uses for fault response and preventive maintenance.

Diagnosing equipment with a flurry of alarms​

  • Who Maintenance staff · equipment engineer
  • When Alarms repeat on one piece of equipment or suddenly spike
  • You type this "Why are there so many alarms on injection molder #2? Narrow down the cause"
  • You get this Candidate causes narrowed down from five angles — alarm frequency, duration, sensor correlation, trend prediction, and statistics — plus tags that moved together. If an order is visible, such as "vibration rises 5 minutes after temperature rises," that is mentioned too.
  • Caution Results are weak if the time series has only accumulated over a short period or alarm history is sparse. These are «candidate» causes, not confirmed ones. If the same thing keeps happening, you can hand it off to the automation templates «Clean up repeated alarms» · «Repeated failure cause», and «Nag on unassigned incidents» can take care of chasing incidents no one has claimed → Use Cases — Automation

Finding out how it was handled last time​

  • Who Maintenance staff — especially someone new to that equipment
  • When The same symptom has appeared again
  • You type this "How was this equipment's issue handled last time?" — this is also available as a question chip on the Ask home screen.
  • You get this Action and outcome records left in Suggestions, plus the matching procedure (with grounds) found in the equipment manual and work standard documents. For installations with video/audio enabled, that segment of the maintenance video showing the procedure is attached too. The Grounds section of the suggestion detail also shows past cases of the same equipment and same symptom along with documents, and Open Related Procedure opens the work procedure.
  • Caution Actions without a recorded outcome don't exist in the record. Making it a habit to leave a result record after taking action is what makes this use case work. → Suggestions · Ask with Video · Audio

Reading part information from nameplate/label photos​

  • Who Maintenance staff · materials staff
  • When You need to order a replacement part but would otherwise have to copy the nameplate by hand
  • You type this Attach a photo of the nameplate and say "Summarize this motor's nameplate information"
  • You get this A summary of the text on the nameplate (including Korean), read and organized.
  • Caution If the same photo is read multiple times and results disagree, it is rejected. Cross-check against the original nameplate before ordering parts. Photos are not stored. → AI Chat

Getting confirmation that a repair actually worked​

  • Who Maintenance staff
  • When After executing an action in the suggestion detail and leaving a result record (done · not applicable)
  • You type this No separate task needed.
  • You get this During the recurrence verification period after the result, the AI watches to see if the same problem happens again — the detail shows «watching for recurrence of the same problem · until ○ days» and, if it recurs, it returns to in-progress as a recurrence. For incident actions, the system automatically checks one hour after execution (default) whether the issue has recurred on the same equipment.
  • Caution No recurrence is not a guarantee the cause is gone — it only means it did not reappear within the verification period. → Anomaly Detection · Incident Response

Submitting a maintenance request draft to the source system​

  • Who Someone authorized to approve drafts — who holds this is set per installation → Access Control
  • When A maintenance request is attached to a card raised by a failure-risk suggestion or automation
  • You type this Opening that card in Suggestions shows the equipment, priority, title, due date, assignee, and content in the Draft Created on Approval field. Enter an Approval Reason and click Approve and Create Draft.
  • You get this One draft maintenance request is created in the connected MES, and a request number is shown. The same approval will not create it twice. Actually sending it is done by a person in that system.
  • Caution An MES connector that issues maintenance requests to the digital thread must be connected — otherwise you'll see «Cannot create draft: no connected system». Depending on the installation, approval from two different people may be required, and the first approver cannot also give the second approval. This does not change confirmed records. → Suggestions — Draft Created on Approval · Digital Thread