1. Security and Digital Recording System Students: Gadi Marcu, Tomer Alon Supervisor: Erez Zilber Semester:Spring 2004 Characterization Presentation

2. Project Goals Designing and implementing a management system for data, originating from cameras, sensors and possibly other devices. This system will enable viewing the data and storing it.

3. System Specifications Real – Time Data Access Stored Data Access Device Configuration Dynamic Response Configuration Users Hierarchy & Permission Management

4. Real – Time Data Access Controlling cameras in real – time:  Issuing commands (turn on, turn off, zoom, etc…)  Viewing live broadcast Optional:  Displaying live broadcasts from several cameras, at the same time (split screen / automatic rotation)

5. Stored Data Access Providing a user – friendly access:  Filtered / sorted by: Time & Date Devices / Device Groups Alarms & Severity

6. Device Configuration Adding / removing devices Grouping devices into device-groups Setting working profile:  Device activity periods  Data storing policy  Stored data classification (alarm severity)

7. Dynamic Response Configuration Assigning responses to signals received from other devices / systems:  Camera activation  Data recording and classification  Sending E-mail / SMS

8. Users Hierarchy & Permission Management Authorized users access only Different permission levels: a)Real – Time data view only b)Viewing stored data + a c)Deleting stored data + b d)Device configuration + c e)Users management + d

9. Users Hierarchy & Permission Management (cont.) Adding / removing users Setting permission levels Grouping users into user-groups

10. System Design Server End User Device Other System

11. System Design Considerations Communication Protocols:  TCP / UDP  Structure of different messages sent among the different devices Network Traffic:  Video & data compression  Multiple network adapters Database Storage:  Compression  Quota alert

12. System Implementation Microsoft.NET Microsoft SQL Server 2000

13. Project Schedule Estimated End Date Phase May 1 st Analysis April 25 th  Devices working profile  Communication with devices  Familiarizing with the CANOpen system May 1 st  Communication protocols  Network traffic  Data storage handling

14. Project Schedule (cont.) Estimated End Date Phase May 15 th Design May 8 th  Basic GUI design  Database schemas  Class design May 15 th  Class design (cont.)  Mid-semester presentation

15. Project Schedule (cont.) Estimated End Date Phase End of June Implementation (1 st Iteration) End of July Implementation (2 nd Iteration)

16. Thank You