On our 36 m tunnel oven, I run flame-signal dropout and gas valve tightness tests every Friday at 6 a.m. under LOTO with a calibrated manometer; QA is pushing for daily checks — are you aligning to NFPA 86 and the OEM’s weekly spec or moving to 24-hour intervals, and how are you documenting it without killing uptime?
least privilege — do you enforce a strict 1:1 binding between change-key levels and I do, and every exception is a 4-hour overlay group that auto-expires at end of shift; no contractor submasters, just one sealed GM for break-glass. With 11 tiers across 4 buildings, we rebuild card groups nightly from HR roles and require a ticket ID to mint an overlay — can your ACS (LenelS2/Openpath) handle expiring groups?
Short answer from my side: I’m seeing the same pattern — one concrete thing that helped was writing down the exact handoff and timebox it to 15–20 min. Does that match what you’re running into?
We stuck with NFPA 86/OEM for the full LOTO leak‑tight test weekly, and added a 60‑second daily “beep test” at shift start: trend flame‑signal µA and manifold pressure, verify POC/interlocks, and drop a manometer photo into a CMMS checklist for auto‑timestamping. It preserves uptime and gives QA daily evidence; any drift outside a set band auto‑triggers an unscheduled full test. If the push is insurer‑driven (e.g., FM Global), align the scope to their wording; reference: https://www.nfpa.org/codes-and-standards/all-codes-and-standards/detail?code=86.
It helps to highlight any relevant lab experience on your resume, even if it’s just coursework or internships — i landed my first lab tech job in part because I showcased my lab projects — definitely worth mentioning those details.