Goals and Road Map: Difference between revisions
(18 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
__NOTOC__ | |||
== Project Goals and Roadmap== | == Project Goals and Roadmap== | ||
The goal of this project is to provide excellent Access Control and Security solutions based on open-source hardware and software. | |||
[[File:v3_refererence_arch.jpg|right|400px]] | |||
=== Commodity Hardware and Software Focus === | === Commodity Hardware and Software Focus === | ||
Open Access Control takes advantage of commodity items from many sources such as: | |||
* Electric Door hardware | * Electric Door hardware | ||
* Power supplies and enclosures | * Power supplies and enclosures | ||
* Alarm Sensors | * Alarm Sensors | ||
* IP video cameras | * IP video cameras ([http://www.onvif.org/ ONVIF Standard]) | ||
* Small-format PCs | * Small-format PCs | ||
* Open-source software for many common tasks | * Open-source software for many common tasks | ||
** Serial monitoring and logging | ** Serial monitoring and logging | ||
** Secure e-mail and SMS alerting | ** Secure e-mail and SMS alerting | ||
** Video processing | ** Video processing ([http://en.wikipedia.org/wiki/OpenCV OpenCV]) | ||
** Basic video archiving ([http://www.zoneminder.com/ Zone Minder)] | |||
** Home Automation ([http://wiki.linuxmce.org/ Linux MCE]) | |||
** Storage management and archiving | ** Storage management and archiving | ||
** Encryption | ** Encryption | ||
** Basic embedded systems development | ** Basic embedded systems development | ||
Our goal became to develop a fully open-source security solution made from commodity parts. This would enable anyone to write in support for new hardware, customize the work-flow for their systems, and | Our goal became to develop a fully open-source security solution made from commodity parts and open-source designs. This would enable anyone to write in support for new hardware, customize the work-flow for their systems, and leverage the pool of existing open-source software for monitoring, processing, alerting, database storage and other tasks. | ||
===Initial Project Goals=== | ===Initial Project Goals=== | ||
The initial [http://code.google.com/p/open-access-control/ Open Access Control] project had the following goals in mind: | The initial [http://code.google.com/p/open-access-control/ Open Access Control] project had the following goals in mind: | ||
*Control 2 doors with electric hardware | *Control 2 doors with electric hardware and Form C relays | ||
*Support 2 Wiegand-format | *Support 2 Wiegand-format reader inputs | ||
*Support 2 additional relays for chimes, sirens, etc. | *Support 2 additional Form C relays for chimes, sirens, etc. | ||
*Have 4 supervised alarm zones | *Have 4 supervised alarm zones | ||
*Support a real-time clock (RTC) | *Support a real-time clock (RTC) with battery backup | ||
*Run independently of a PC, with internal database | *Run independently of a PC, with internal database | ||
*Support attachment to a Linux PC for monitoring and alerting, remote access | *Support attachment to a Linux PC for monitoring and alerting, remote access | ||
Line 50: | Line 41: | ||
As a result, we formed [http://www.accxproducts.com ACCX Products] as a way to provide open-source designs for the system, and pay for the project with by selling consulting, commercially-produced boards, starter kits and other items. | As a result, we formed [http://www.accxproducts.com ACCX Products] as a way to provide open-source designs for the system, and pay for the project with by selling consulting, commercially-produced boards, starter kits and other items. | ||
==== Latest Project | === Evolution of the Project === | ||
[[Project Evolution]] | |||
=== Latest Project === | |||
The current project is a ground-up revision of the Open Access Control. This has been tentatively called "Open Access v3.0" Check out the [[Open Access 3.0]] Project Page for details. | The current project is a ground-up revision of the Open Access Control. This has been tentatively called "Open Access v3.0" Check out the [[Open Access 3.0]] Project Page for details. | ||
Line 56: | Line 50: | ||
*Develop a set of physical, electrical and logical interface standards to allow anyone working on open-source hardware and software for security applications to be compatible. | *Develop a set of physical, electrical and logical interface standards to allow anyone working on open-source hardware and software for security applications to be compatible. | ||
*Develop a framework for end-to-end encryption of security transactions using AES and other industry-standard algorithms | *Develop a framework for end-to-end encryption of security transactions using AES and other industry-standard algorithms | ||
* | *Develop new bi-directional protocol fors [http://en.wikipedia.org/wiki/MIFARE Mifare], [http://en.wikipedia.org/wiki/Near_field_communication Near Field Communication], and other devices that support challenge-response. | ||
*Produce a set of development kits to facilitate development by others. This may include: | *Produce a set of development kits to facilitate development by others. This may include: | ||
**Wiegand break-out boards | **Wiegand break-out boards |
Latest revision as of 11:15, 14 May 2012
Project Goals and Roadmap
The goal of this project is to provide excellent Access Control and Security solutions based on open-source hardware and software.
Commodity Hardware and Software Focus
Open Access Control takes advantage of commodity items from many sources such as:
- Electric Door hardware
- Power supplies and enclosures
- Alarm Sensors
- IP video cameras (ONVIF Standard)
- Small-format PCs
- Open-source software for many common tasks
- Serial monitoring and logging
- Secure e-mail and SMS alerting
- Video processing (OpenCV)
- Basic video archiving (Zone Minder)
- Home Automation (Linux MCE)
- Storage management and archiving
- Encryption
- Basic embedded systems development
Our goal became to develop a fully open-source security solution made from commodity parts and open-source designs. This would enable anyone to write in support for new hardware, customize the work-flow for their systems, and leverage the pool of existing open-source software for monitoring, processing, alerting, database storage and other tasks.
Initial Project Goals
The initial Open Access Control project had the following goals in mind:
- Control 2 doors with electric hardware and Form C relays
- Support 2 Wiegand-format reader inputs
- Support 2 additional Form C relays for chimes, sirens, etc.
- Have 4 supervised alarm zones
- Support a real-time clock (RTC) with battery backup
- Run independently of a PC, with internal database
- Support attachment to a Linux PC for monitoring and alerting, remote access
We achieved this goal with the current design. Assembled boards, kits and readers are available in the ACCX Products Store.
Current Development Effort
Following the success of the original Open Access Control, many people have asked us to continue development of the project.
As a result, we formed ACCX Products as a way to provide open-source designs for the system, and pay for the project with by selling consulting, commercially-produced boards, starter kits and other items.
Evolution of the Project
Latest Project
The current project is a ground-up revision of the Open Access Control. This has been tentatively called "Open Access v3.0" Check out the Open Access 3.0 Project Page for details.
Project Roadmap
- Develop a set of physical, electrical and logical interface standards to allow anyone working on open-source hardware and software for security applications to be compatible.
- Develop a framework for end-to-end encryption of security transactions using AES and other industry-standard algorithms
- Develop new bi-directional protocol fors Mifare, Near Field Communication, and other devices that support challenge-response.
- Produce a set of development kits to facilitate development by others. This may include:
- Wiegand break-out boards
- RS-485 shields for Arduino
- Low-cost single-door boards
- Full featured Ethernet-capable boards
- CAN BUS boards
- Standardize an SDK for others to create exciting new devices and software for home automation, security and access control