WINLAB

1
WINLAB • Design an Enterprise-based Automation system that will provide centralized control and monitoring of devices virtually from anywhere • EZ-Access introduces a simple and secure way for students and faculty at Rutgers to control the environment around them. • From opening locked doors, to controlling the temperature, to altering students , EZ-Access provides a way for one to become more in charge of their Rutgers Experience. with any mobile device. The EZ-Access architecture is essentially made up of series of main controllers all linking back to a centralized server, which acts as the decision maker. The main controllers can be thought of all having control over their own little local network of devices, and main controller act as the moderators between the server and the automation devices. Shown below is our project at a Local Scale: Main Controller Automation Device Users have the option of accessing our system through either our desktop website, or our mobile site, which can access devices through a QR-code . Through the use of multiple centralized servers, we are able to make an Ez-Access network, which has the capability of handling the whole university. Server Device Privileges Locations Properties Website User Name Password Roles Devices Status Database Interne t Main Controller Automation Devices Main Controller Automation Devices The Users communicate with the server through either wired Rutgers Network or RU-Wireless. The main controllers have been provided with static IP’s, which allows them to be connected directly to the Rutgers Network. The Main controllers communicate to the server via Rutgers network, and communicate with their attached devices via Zig-Bee. QR-Codes located at each automation device, redirects user to mobile site. Sites have ability to store passwords. Guest Twitter Access Supervisors have ability to assign permission to other users. Main Controller regularly updates devices status, and relays info to server. . LDAP Authentication Session Management for all websites, which prevents access to vital information SQL injection prevention measures All packets between main controller and server encrypted using AES encryption Zigbee packets encrypted using Users assigned privileges based on university roles Hardware - Arduino Mega/Uno Microcontroller - Zbee Radios Software - PHP - MySQL - HTML/CSS Development Tools - Netbeans - Adobe Dreamweaver Arduino Environment Siddharth Paradkar, Michael Montemarano, Kush Patel , Neipaul Angad EZ-Access Automation Systems Instructor : Dr. Christopher Rose Objective Introduction System Architecture System Architecture Network Architecture Security Framework Enhancements LCD Light Lock

description

Main Controller. EZ-Access Automation Systems. Automation Device. Internet. Website. Instructor : Dr. Christopher Rose. Server. Siddharth Paradkar, Michael Montemarano, Kush Patel , Neipaul Angad. Devices Status Database. User Name Password Roles. Device Privileges Locations - PowerPoint PPT Presentation

Transcript of WINLAB

Page 1: WINLAB

WINLAB

• Design an Enterprise-based Automation system that will provide centralized control and monitoring of devices virtually from anywhere

• EZ-Access introduces a simple and secure way for students and faculty at Rutgers to control the environment around them.

• From opening locked doors, to controlling the temperature, to altering students , EZ-Access provides a way for one to become more in charge of their Rutgers Experience. with any mobile device.

•The EZ-Access architecture is essentially made up of series of main controllers all linking back to a centralized server, which acts as the decision maker.

•The main controllers can be thought of all having control over their own little local network of devices, and main controller act as the moderators between the server and the automation devices.

• Shown below is our project at a Local Scale:

Main Controller Automation Device

• Users have the option of accessing our system through either our desktop website, or our mobile site, which can access devices through a QR-code .

• Through the use of multiple centralized servers, we are able to make an Ez-Access network, which has the capability of handling the whole university.

 

ServerDevice

PrivilegesLocationsProperties

Website

User NamePassword

Roles

DevicesStatus

Database

Internet

Main Controller

Automation Devices

Main Controller

Automation Devices

• The Users communicate with the server through either wired Rutgers Network or RU-Wireless. The main controllers have been provided with static IP’s, which allows them to be connected directly to the Rutgers Network.

• The Main controllers communicate to the server via Rutgers network, and communicate with their attached devices via Zig-Bee.

• QR-Codes located at each automation device, redirects user to mobile site.

• Sites have ability to store passwords.• Guest Twitter Access• Supervisors have ability to assign

permission to other users.• Main Controller regularly updates devices

status, and relays info to server. .

• LDAP Authentication• Session Management for all websites,

which prevents access to vital information• SQL injection prevention measures• All packets between main controller and

server encrypted using AES encryption• Zigbee packets encrypted using DES• Users assigned privileges based on

university roles

Hardware- Arduino Mega/Uno Microcontroller- Zbee RadiosSoftware- PHP- MySQL- HTML/CSSDevelopment Tools- Netbeans- Adobe Dreamweaver- Arduino Environment

Siddharth Paradkar, Michael Montemarano, Kush Patel , Neipaul Angad

EZ-Access Automation Systems Instructor : Dr. Christopher Rose

Objective

Introduction

System Architecture

System Architecture

Network Architecture

Security

Framework

Enhancements

LCD Light Lock