A short check at the start of each shift catches problems early. A camera that went offline last night is easy to fix today. It is much harder to explain after an incident, when the video you need is missing. This routine takes about 10 to 15 minutes. Print the table near the end and keep it by the console.
Before you start
- Make sure you can open the SSMS console the way you were shown at handover.
- Have the shift log and the notes from the last shift.
- Know who to report problems to, such as your supervisor and the IT admin.
The start-of-shift routine
- Read the last shift log. Look for open issues, cameras reported offline, and any incident still being handled.
- Open the console. Check that it opens normally and that the live wall shows every site.
- Count the cameras with no picture. Compare the number with yesterday. A newly offline camera must be reported today.
- Spot-check picture quality. Look for the problems in the table below.
- Do a playback test. Pick one camera at each site. Play back the last 15 minutes on the timeline. This proves the camera is recording, not just showing live video.
- Check the time. Compare the time shown on screen with a trusted clock, such as your company's official time. If they do not match, report it.
- Check your priority cameras. These are the cameras your site cares about most, such as main entrances, cash points and loading bays. Make sure each one shows a clear and correct view.
- Write everything in the shift log. Note what you checked, what you found and who you told.
- Report problems straight away to the person your procedure names.
Picture problems to look for
| What you see | Likely cause | What to do |
|---|---|---|
| Blurry or misty picture | Dirty lens, spider web or condensation | Report it for cleaning |
| Part of the view is blocked | Boxes, signs, plants or parked vehicles | Report it to the site team |
| The view has moved | The camera was knocked or has come loose | Report it so the camera can be re-aimed |
| Very dark at night | Night mode not working, or lights are out | Report it to IT and the site team |
| Strong glare | Sun or a lamp pointing into the lens | Report it; the camera may need re-aiming |
| Frozen picture or no picture | Camera, power or network problem | Treat it as offline and follow the offline guide |
For a camera with no picture, follow what to do when a camera goes offline.
Console-room basics
- The procedures binder is in its place.
- The contact list is up to date, with names and phone numbers.
- Blank incident forms and the footage access register are at hand.
- Nobody else is using your sign-in.
- Nobody uses a phone to film the screens.
End-of-shift handover
- Update the shift log with anything still open.
- Tell the next operator about offline cameras and any incident in progress.
- Hand over items, such as footage copies waiting for collection, against a signature.
- Lock the screen or sign out, as your procedure says.
Printable checklist
Print this table for each shift. Tick each line and add short notes.
| Check | OK? | Notes |
|---|---|---|
| Last shift log read | ||
| Console opens, every site visible | ||
| Offline cameras counted and compared with yesterday | ||
| Picture quality spot-checked | ||
| Playback test done, one camera per site | ||
| Screen time matches a trusted clock | ||
| Priority cameras clear and correct | ||
| Issues logged and reported | ||
| Console-room basics in place |
Where to go next
- Weekly and monthly SSMS health checks
- What to do when a camera goes offline
- Watching live cameras on the SSMS live wall
- Training new SSMS operators
Quick checklist
- I read the last shift log before doing anything else.
- Every site shows on the live wall.
- Any newly offline camera is reported today.
- Playback works at every site.
- The time on screen is correct.
- Everything I found is written in the shift log.
Comments
0 total · 0 threads