Purpose:
To enable the execution of the inspection process and content in a digital format.
Click on walk-through link for Preview Inspection: https://app.storylane.io/share/hnxm8us5n2kh
Click on walk-through link for Start Inspections: https://app.storylane.io/share/ptc8g3ra6850
Click on walk-through link for Checked Out Inspections: https://app.storylane.io/share/oxkg6egms82k
Click on walk-through link for Adding and Editing Images in Defects https://app.storylane.io/share/1btmr0uqbine
Note: the walk throughs are from ZoneMaintenance. The features and functionality is the same just a change of terms.
Process:
1. Log In
Log in using your provided username and password
2. Inspection List
Inspection list provides all the inspections that have not been completed for the models and roles that the person has log in can perform
Scheduled
- Inspections not yet started
Stopped
- Inspections stopped for what ever reason
In Progress
- Inspections is in progress by someone else
Checked Out
- Inspections has been checked out by someone else
3. Preview Inspection
Enables the user to look into the inspection without having to start the timer or save any details.
4. Begin Inspection
Begin the inspection to start.
Complete the following screens to get to the tasks.
Check off parts and tools required.
Check off any permits that maybe required within the inspection.
Complete the start questions every time the inspection is started.
5. Preparation
Check them off to ensure that they are on the job before you start.
This is designed to be prepared and not having to leave the service for either of these items.
If there is an issue with these items, provide a reason why in the dropdown list when the missing box is ticked.
Or tick all to progress to the next screen.
6. Start Questions
To be filled in at each start of the job. Regardless if it have been stopped, the new person on the job needs to answer these start questions again.
The Process
The process can be shared with the field personnel to help them understand what they are doing and where they are going.
7. Tasks
Tasks are set in an order to promote an efficient flow within the stage or area.
Content is presented in the right panel to define what is expected with the task and specific information is provided to benefit the inspector assigned to complete.
Click on the image to open larger and flick to the right to see more if available.
Complete the task using the green button top right of the panel.
The user can look at previous or next tasks with freedom.
You cannot complete other tasks unless the task with the blue dot is not completed first.
If you complete a task by mistake, just click on the "Task Completed" button to undo the change.
8. Skip Tasks
Skip the next task feature enables the user to progress through the service if a task is not able to be completed.
The user can click on the skip this task button and give a reason why the task is to be skipped.
This will be recorded in ZoneMaintenance Analysis in the service impacts screen.
9. Documents and Questions
If the button is highlighted then the user can view a document or answer a questions.
A question could be compulsory meaning that the user needs to answer it to complete the task.
Questions are designed to determine the condition of the component by giving it a value or selecting from a dropdown list or other question formats.
10. Condition Monitoring Questions
A question might be to provide a value that is being trended.
A minimum or maximum range is provided and a specification is listed.
A value outside of the min/max range will trigger a defect.
If there are more than one CM question and all are out of range then a defect will be raised for each question.
11. Findings
A finding can be raised either by
1. clicking on the Finding button on the main screen
2. answering a question that triggers the finding feature
If a finding is registered then the user has to completed the fields, add further details about the finding and take images for future inspection.
A finding is raised against a task but a finding can be raised but not assigned to the task. Click on the x in the task box removes the task from the registered finding.
Click on the icon on the top left of the thumbnail to mark up the photo.
12. Existing Findings
Existing findings are findings that have been reported during the inspection or that were reported during previous inspections that are still outstanding.
This list is only for the stage or area the user is currently in.
The user can click on these findings and change the status or risk rating. Take more images to outline the changes that has occurred.
It is important for users to change findings to completed if the finding looks to have been rectified.
13. Notes
User can leave a note to provide some information relevant to the service which is not.
- A finding
- A feedback
Example might be another person has been added to help the user with the inspection. The new person is not assigned any task but the signed on user is accountable to indicate if they have been completed. The user might like to add which tasks the new person completed for future reference.
14. Pause
User can pause the inspection and provide a reason.
As the inspection is being timed any impact that causes the user from performing his or her duties should be captured by pausing the inspection.
If the person is taken off the inspection then the job must be stopped.
15. Stop or Completed Inspection
Stopping a inspection is designed to enable the user to log off to be handed over to someone else to complete.
User is to give a reason and sign.
Prior to stopping the inspection the user can view recorded findings to show the supervisor or make changes prior to the sync.
Additionally, the user can stop and log out with one button. This will sync the data and log the user off with the one click.
16. Menu
Current Task - task the user to the last task completed.
Skipped Tasks - gives the user a list of the skipped tasks to be completed.
They can be completed in any order
Notice boards - information that might be useful to share with all users.
Feedback - provides the user the option to offer ideas or suggested changes to content, flow or issues.
17. Feedback
Adding feedback will help you to share your ideas on how to improve the content and process.
Assign the feedback to your supervisor so it can be actioned by the right person to make the change.
Add images as well can be very helpful.
18. Check Out/Check In Process
If a service is being performed in an area without wifi, it is important to check out the inspections being performed.
One or more can be checked out by the user. But this means no one else can access these inspections.
19. Check In
A user that has checked out a inspection must check the inspection back in when they get to wifi range.
Click on the button to check the inspection back in.
This gives others access to the inspection information or are able to start a stopped inspection.
If this is not followed then the user that has checked out the inspection will lock the inspection from anyone else.
This is like taking the paper based inspection sheet home with you.
20. In Progress
If a user does not stop a inspection, signs off and sync’s the inspection when in wifi range, the inspection remains in progress.
This stops anyone else from starting the inspection as it has been assigned to that person that has started the inspection.
If the person leaves site, it is like taking the inspection sheet with them.
The supervisor can reset the inspection via the web application Inspections but the risk is that data could be lost and the inspection
would need to be performed again.
21. Register Service
A inspection can be registered from the iPad if necessary.
The user needs the information to complete the compulsory fields to register a inspection.
They also need to be within wifi range to complete this process.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article