As discussed, an “incident” this weekend has led us to revisit the idea of sending alerts to Logistics to eliminate the need to be constantly scrolling the rig board and potentially missing something urgent. Right now we rely on Ops to give us a heads up.
The “incident” in question was a job that came up, first call, with less than 24 hours notice. By the time Matt noticed it on the RB he was at the end of day shift, with only 18 hours before the job, testing that needed to be completed and an houred out lab tech.
Obviously we don’t want/need an alert for every job that comes up, so I was thinking we could have some rules to determine what needs an alert:
To start, I have put together this short list.
Any jobs that enter pending stage within 48 hours of expected job time (With Testing Required)
Any jobs that are up within the next 12 hours, 6 hours in the SE, not having "ALL" cement on location
A change in blends where a load is already scheduled
If surface requires testing, alert within 48 hours (same as other blends)
If batch surface, do not send alert after the first job.
All other surfaces follow same rules as other jobs (6 hours east, 12 hours west)
Notifications to be sent, via teams, to Logistics and Dispatch
As discussed, an “incident” this weekend has led us to revisit the idea of sending alerts to Logistics to eliminate the need to be constantly scrolling the rig board and potentially missing something urgent. Right now we rely on Ops to give us a heads up.
The “incident” in question was a job that came up, first call, with less than 24 hours notice. By the time Matt noticed it on the RB he was at the end of day shift, with only 18 hours before the job, testing that needed to be completed and an houred out lab tech.
Obviously we don’t want/need an alert for every job that comes up, so I was thinking we could have some rules to determine what needs an alert:
To start, I have put together this short list.
Notifications to be sent, via teams, to Logistics and Dispatch