1. Access Control System Final Report Presenting: Ehud Bahat Amir Levy Instructor: Erez Zilber March 2003

2. Project Goal The system will remotely control and administrate devices in a CAN network. The system will manage users and their privileges in the network.

3. Specifications Receive events from devices and act accordingly: –Send events to other devices on local network. –Send events to other devices on remote network. –Send email messages. Administration of the users and devices in the network: –Components and Component groups. –Users and user groups. –Authorize users to use components. Produce reports of the system activity: –Event log. –Component and user administration actions log.

4. High Level Design Web app. Control CANOpen Interface DB CAN Network Remote Server

5. ACSWebApp

6. ACS Application ACS Service ACS Server ACS Thread Socket Listener CAN Engine BusOD Networ k

7. Architectural Dilemmas and Chosen Solutions Grouping users and components. Static vs. dynamic information storage. –Serial numbers, Index, Sub index. –Cob_id, component states. Authorization mechanism. –Default ‘deny’ for users. –Default ‘allow’ for component times. Number of administrators for groups. –Unlimited.

8. Architectural Dilemmas and Chosen Solutions – Cont. Performance issues –Each event is handled in a separated thread. –Thread for each bus. –Thread for events from remote hosts.