The round reading
TodayWritten in a large A3 logbook during the round, keyed in later at a desk. If at all.
With MobapiEntered once only, on a phone, during the round.
Digital operator rounds and shift log
Your field readings, entered once, read by everyone.
Your teams do their rounds on a phone and keep the shift log in the same tool. Every round is time-stamped and carries the operator’s name. Its readings join the history of your equipment, alongside sensor measurements. Nothing left to copy out.
What changes, round after round.
Who recorded what, and at what time
TodayHandwriting to decipher, initials, rarely a time.
With MobapiEvery round carries the operator’s name, its start time and its end time.
Shift handover
TodayA logbook left at the workstation, which the next shift only sees when it arrives.
With MobapiA shared shift log: every entry is time-stamped, with the asset, the location and the operator.
Readings and sensors
TodayManual readings on one side, automatic measurements on the other.
With MobapiRound readings join the same history as sensor measurements, on the same screens.
A round prepared once, followed every time.
Every round follows a template prepared in advance. In the field, the operator only has to answer, checkpoint by checkpoint.
A template for every round
One template per piece of equipment, or one for the whole site. Checkpoints are grouped into sections, for example “Turbine running”, and an Observations block closes the round.
Progress at a glance
During the round, the operator sees what is left to do and what is done. Once finished, the round carries its validation status.
Even with no network
The app works offline, even inside buildings that act as a Faraday cage. Readings sync by themselves as soon as the network is back.
Every round, easy to find
The list of rounds can be filtered by operator, by template and by validation status. Each one opens reading by reading.
Five answer types.
Sample readings, illustrative data.
-
Text
Observations
All OK
-
Number and unit
Air cooler, inlet temperature
74 °C
-
Yes or no
Turbine running
Yes (answer not selected: No)
-
Choice from a list
HMI alarms
None (other possible answers: Oil Ventilation Other)
-
Photo
Genset condition
One shift log, the same for the whole site.
Every event becomes a time-stamped entry, with its type, the asset concerned, the location and the operator. The incoming shift reads what the previous shift wrote down, in the same place.
- Search
- across all entries, with a filter by asset
- Export
- of entries, for a report or an archive
Filed with your sensor measurements.
The same history.
A round reading joins the history of its equipment, just like a measurement sent by a sensor. Both can be viewed on the same screens.
The readings you already keep.
Readings tracked in a spreadsheet? They can be imported from a CSV or Excel file and join the same history.
Frequently asked questions.
What is lost when rounds are kept on paper?
Time, context, the trend and proof. Between the reading and the re-keying, the value exists only in the logbook: an abnormal pressure noted at 10 am may wait until the next day to be seen from the office. Entered on a phone in Mobapi, it joins the history straight away, with its time and the operator’s name.
What can be entered during a round?
Text, a numerical value with its unit, a yes or a no, a choice from a list of answers, or a photo. Readings are grouped into sections, followed by an Observations block.
Does the app work with no network?
Yes. The rounds app works offline, for example inside a building that acts as a Faraday cage. It syncs automatically as soon as the network is back.
How do we know how far along a round is?
Every round shows its progress and its validation status. The list of rounds can be filtered by operator, by template and by status, and each round opens reading by reading.
What is a digital shift log?
It is the record of a shift’s events, kept in a shared tool rather than in a logbook left at the workstation. Every event becomes a time-stamped entry, with its type, the asset concerned, the location and the operator. In Mobapi, the incoming shift reads what the previous shift wrote down, and finds an entry with a search.
What does a shift log entry contain?
What happened, with the date, the entry type, the asset concerned, the location and the operator. Entries can be found with a search or a filter by asset, and can be exported.
Our readings are already in Excel files. Do we have to key everything in again?
No. Readings kept in a CSV or Excel file can be imported into Mobapi. They join the same history as round readings and sensor measurements.
How do you move from paper rounds to digital rounds without disrupting the teams?
By changing nothing but the medium to begin with: the same route, with no extra checkpoint and no extra field. A tool that does away with re-keying is quickly taken up, and a tool that adds some will be worked around. At a thermal power plant operator equipped by Mobapi, shift logs went digital before rounds.
Show us your round sheets.
Paper, spreadsheet or shift logbook: tell us how your readings are kept today. We’ll show you what they become in Mobapi.
See also: For operations · For maintenance · And if your fleet mixes generations…