Jarvis Access Control System

Integrated an Amazon AWS IoT Button

How do you design a system that authenticates different types of users without having users logged into the system? This was one of the more challenging aspects of the project. I decided on using Access Keys with unique id's to identify and connect users to cards, pins, locations, etc. Everything is stored in Firebase as lookups.

• Access Keys
  • ID
  • Name
  • Type (admin, user, temp)
  • Location (lookup)
  • Expiration Date
  • Deleted
  • Registered
  • Enable
• Location
  • ID
  • Name
  • Mode (used for provisioning cards)
• Pins
  • ID
  • Access Key (lookup)
  • Location (lookup)
  • PIN
• Cards
  • ID
  • Access Key (lookup)
  • Location (lookup)
  • Card Number
• Doors
  • ID
  • Access Key (lookup)
  • Location (lookup)
• Logs
  • ID
  • Access Key (lookup)
  • Location (lookup)
  • PIN or Card or Door

The Access Control System comes with an Android app used to manage access keys, create pins, provision cards, select boom music, open the door and more.

Admin: Usually the owner(s) of the company.

• Has the ability to create new Access Keys for their specified location.
• Can provision new cards for their specified location and attach them to a different Access Key (of same location)
• Can provision new pin for their specified location and attach them to a different Access Key (of same location)
• Can provision new temp pin for their location (creates an Access Key of type ‘temp’)
• Can enable/disable Access Keys for their location
• Can create their own pin
• Can provision their own card
• Can apply boom music
• Can view logs
• Can open door

User: Usually the employees of the company

• Can create new pin for their location
• Can apply boom music
• Can open door

Temp: Used for pins (and card?) only

• Has an expiration date and time
• Set by the Admin