Setting up a job profile
A profile is the template a job is recorded from. Because it is configured once, every job on the same machine captures the same readings — which is what makes two jobs comparable.
Go to Jobs → Job profiles → New profile.
Name and machine
Give the profile the machine's name, as the people using it would say it — "Drilling Rig 1", not an asset code no one recognises. It appears on every report this machine produces.
Machine (gateway) links the profile to the gateway on the machine. This is optional but worth setting: it is how Synacl notices the machine has gone offline mid-job, so a job whose end never arrives still gets closed instead of running forever.
Devices in scope
Select every device that belongs to this machine. Only tags on the selected devices can be captured, and only alarms and rule fires from those devices are counted toward the job.
Getting this wrong in the generous direction is the more common mistake: including a device that is not part of the machine inflates the alarm count of every job with alarms that had nothing to do with the work.
Choosing readings
Two separate lists, because they answer different questions.
Record throughout the job becomes the charts and the reading table — the readings you want a history of. Oil temperature, air pressure, leveling. These are averaged into one point per interval.
Turn on limits for any of these to draw that tag's configured alarm band on its chart. The band comes from the tag's own threshold settings, so what the report prints is provably the limit the hardware is actually alarming on — not a second copy that can drift out of step.
Capture before and after is read once when the job starts and once when it ends. The report shows both values and the change. Use it for anything where the difference is the point: oil level consumed, hour-meter readings, tank contents.
A reading can be in both lists.
Interval
How often the "throughout" readings are recorded. Every minute suits most machines.
This cannot be finer than the devices themselves report. If a device publishes every 30 seconds and you pick every 10 seconds, most intervals will simply be empty.
GPS device
If the machine has a GPS device, select it here and its position is captured when the job starts. The report shows the coordinates and links them to a map.
Job numbering
Job numbers are assigned automatically — the operator never types one. Set the prefix and the
number of digits: DRL with 5 digits produces DRL-00001, DRL-00002, and so on.
The counter belongs to the profile and only moves forward. Job numbers are unique within your account and are never reused, including after a job is aborted.
Length limits
- Min length — an automatically started job shorter than this is discarded as a false start. A job you end yourself is always honoured, however short.
- Max length — a job running longer than this is closed automatically and marked approximate.
- Offline grace — how long the machine can be unreachable before an open job is closed automatically.
Set max length a comfortable margin above your longest realistic job. Too tight and genuine long jobs get cut short and flagged approximate; too loose and a forgotten job stays open for days.
Deleting a profile
You cannot delete a profile while one of its jobs is running — end the job first. Deleting a profile keeps every job already recorded with it, and their reports keep working.