AI CCTVs are being developed by a lot of companies throughout the world. Most of them follow one of the two structures below.
.png)
| Pros |
Cons |
| Best for domestic usage |
Expensive |
| 24/7 Service |
Not Centralized |
|
More power consumption |
|
Inefficient |
|
Slow comprehension |
.png)
| Pros |
Cons |
| Personal usage only |
not 24/7 support |
| Centralized |
less secure |
|
Slow |
Our Approach
.png)
| Pros |
Cons |
| Commercial Usage |
Requires a centralized mainframe |
| Centralized Access |
|
| Secure |
|
| Efficient |
|
| Fast |
|
some other important points regarding why the others can not be used by us
- the 1 approach can not be presented by us as it needs a specialized camera. the 2 can’t be done as it seems immature of us to dump everything together in one thing.
- we also can’t make a full-fledged CCTV-connected system, as there will be no way for us to showcase it at the actual hackathon
- the 3 approach is the closest we can get to the actual CCTV implementation while letting us showcase the system.
AI model
- ActionXPose model from the Newcastle University
- Continual learning - this will allow the AI to become more and more familiar with the place it is stationed at with time
Dashboard
- Statistical analysis of the anomalies detected in the following periods
- 1 day
- 1 week
- 1 month
- 6 months