Example Scenario: We change the state of a piece of equipment to clean and we want it to change back to dirty in exactly 8 hours from “now”. Automatons are limited to run at 1 hour minimum cycles which doesnt support the fidelity that this scenario would require. However adding the ability to schedule an automation at a specific date and time from a trigger within an app would support this functionality perfectly (and replicate functionality on “old” MES systems that is currently missing from Tulip).
There are additional ramifications from this - there would need to be a way to remove a scheduled automation if, for instance in this scenario equipment was cleaned again - which would push out the date and time. So being able to “clear” scheduled events somehow would also be required - inferring a way of naming events may be in order.
Finally a way of viewing scheduled events would be useful (in Emerson Syncade a calendar view can be displayed to show scheduled equipment events - this could be achieved within a Tulip app using info from a data table, but a “Built in” viewer may be in order
Hi Andy,
Please see my prior response for your question around automations.
I think the point of confusion is that each scheduled automation can fire once per hour. That is true but you can set up a few scheduled automations to be offset from each other to achieve the cadence that works for your case.
I hear your desire to tie scheduled automations to a schedule and that’s valuable feedback.
Thanks,
Jake
Thanks
I saw the response but for life sciences I don’t think it would be acceptable, and I didn’t want to “dis” the response publically!. We would need one on every minute to achieve the fidelity required – cleaning is just an “easy” example to explain the concept – scale/probe standarisations which often work on a shift basis would be similar. My feature request is how it is achieved in Syncade and opcenter (and I think Werum too) and would be a lot less loading on the system (think of it like the old windows AT command or cron in unix)
I’m out next week but happy to keep the conversation going when I am back
Andy
Hi @andybmac
I agree that cascading multiple automations is a bit ugly. The automations could get better at that point.
As a valid Workaround, you could think of a node-red solution, where you can set other intervals as well…