The module has two permission levels: the inspector sees and manages only their own inspections; the administrator sees all of the company’s inspections and, in addition, manages the checklist definition, locks / unlocks inspections, returns them to in progress and sends the protocol to the carrier. A new inspection can be created by anyone who has the module; editing and deleting is allowed for the author on their own inspection and for the administrator on any of them. A locked inspection cannot be edited by anyone until the administrator unlocks it.
Inspection state
- A new inspection is In progress - you can come back to it and add to it.
- The Complete inspection button closes it and the state changes to Completed. A protocol can only be issued for a completed inspection.
- The administrator returns a completed and unlocked inspection with the Return to in progress action.
- An inspection in progress is saved continuously to the server on the web, whereas in EDISONKA it is saved locally in the phone. An inspection started on the phone therefore appears on the web only once it is saved.
- An inspection in progress that you no longer need can be discarded.
Carrying out an inspection in the field (EDISONKA)
- Inspection of both buses and trains - a new inspection begins by selecting the mode of transport, Bus / Train.
- Bus: searching for a line and service and pulling in the timetable (route of stops + carrier) from the bus timetable.
- Train: searching by train number or name and pulling in the route (stations) from the national timetable. Instead of line, service, plate number and driver, the train, train category (R, Os, EC, …), trainset and train driver are recorded.
- Inspection section from–to - after selecting the service / train you can choose a section of the route (the default is the whole route); the tally sheet then contains only the stops / stations of the selected section. Only stops where you can actually board or alight are offered.
- Tally sheet - a record for each stop / station (boarding / alighting / occupancy + note). The “completed” flag distinguishes a checked stop (even with a zero) from an unchecked one.
- Expandable stop cards - the inspector need not travel the whole route (they can board part-way through).
- Checklist (one for the whole inspection) - checklist items with notes. Buses and trains have a separate definition of the checklist.
- Inspection result - a summary text for the whole inspection; it also appears in the protocol.
- The vehicle plate number / trainset and driver / train driver are entered manually.
- Attachments: photographs, audio recordings and video (max. 10 attachments per inspection, each file up to 50 MB; videos max. 3, up to 60 s each, audio recording up to 5 minutes). Attachments are uploaded to the server immediately after capture, in the background.
- Recording of the GPS position with the option of repeated updates - an inspection can be prepared in advance at the office and the position updated only once on the service. An incorrectly recorded position can be deleted in the form.
- Continuous local saving of an inspection in progress - it survives even closing the app between stops. There can be several inspections in progress at once; the overview offers each of them to be continued or discarded.
- Saving the completed inspection into the portal.
- A locked inspection (the “Locked” label) opens read-only; the administrator can unlock it directly in the app, or lock a saved inspection.
Overviews and protocols (web)
- The web has two faces: My inspections (only your own) and Carrier inspection administration, where the administrator sees the inspections of the whole company. You switch between them with a single button.
- Overview filters: search, Transport type (Bus and train / Bus / Train) and Inspection state (In progress / Completed). The administration view also has a Lock filter (locked / unlocked).
- Inspection detail - tally sheet, checklist, attachments, location and sharing history.
- The Location tab - a map of the recorded positions in the order they were captured, with the accuracy of each record. Unsuccessful attempts (position denied, location services switched off) are listed as well, so it is clear that someone did try.
- Creating, editing and deleting an inspection - creation follows the same procedure as in EDISONKA, including selecting the from–to section.
- Deleting an incorrectly recorded GPS position (administrator) - using the button next to a specific position in the detail of an unlocked inspection.
- Inspection protocol - PDF print and Excel export (basic data, inspection result, tally sheet, checklist, links to attachments, GPS position). A protocol can be issued only for a completed inspection.
- Sending the protocol to the carrier by e-mail (administrator) - only for an inspection that is completed and unlocked. The protocol is inserted directly into the body of the e-mail; you can enter multiple addresses and add a message for the carrier. Sending automatically locks the inspection; the sending history is visible both in the overview and in the detail.
- Public links to attachments - they are created automatically, by sending the protocol or by printing it; the carrier opens them without logging in. The “Revoke links” button lets the administrator invalidate them at any time.
- Locking inspections (administrator) - a locked inspection is read-only in both apps; the overview shows who locked it and when.
- Managing the checklist definition (administrator) - separately for buses and for trains.
Differences between the phone and the web
- The mobile app serves primarily for carrying out the inspection in the field. Protocols (PDF / Excel), sending to the carrier, public links to attachments and the checklist definition are web-only.
- An inspection in progress lives on the server on the web, and in the phone in EDISONKA.
Carrier settings
How long the links to attachments sent to the carrier remain valid is set by your organisation (the transport organiser).
- Validity of links sent to the carrier (days) - how long the carrier can open the attachments from the protocol that was sent. Empty = 90 days, 0 = the links are valid without any limit. They can also be invalidated manually at any time with the “Revoke links” button.