
One aspect of Designing a System is the initial
footprint. How the system is started can affect how
efficiently it grows in a
logical and organized manner. These brief overviews will
try to show several examples of initial application
footprints based
on system size and growth expectations.
Small to Medium System with moderate growth.
In this application there is typically 1 computer to start
with. This one Host PC operates the entire system. In some cases
this may increase to include one to three client PCs. There is
typically one location to start with comprised of one master
controller which operates the first two doors. As more secure doors
are required additional controllers are simply added to the existing
location. In some cases there may be a few more buildings that are
added to the system. Each of these is added as a new location more
than likely in the same location group sharing the existing card
holders.
Large system such as Hospitals, College Campuses, or Large
Facilities with major growth.
In this application there is a Comm Server PC for system
communications, a SQL Server PC for the shared database, and one or
more Client PCs for the actual users of the system such as security
and database administrative personnel. Typically these applications
start with 10 - 20 doors and grow to 3 - 400 doors or more easily.
In these situations there should be a multiple location approach
starting at the beginning of the system construction. There should
be at least one location for the Parking Structures, one for the
Elevators (if performing elevator control) and one for each
architectural division of the property. This is typically determined
by how the customer refers to their building; by floor or by wing or
other. This
allows for future growth to be efficient and simple. With this
approach each location has major growth potential, quick response,
distributed intelligence and operability, and certainly
organizational efficiency. When designed in this manner it easy to
find a door or alarm point amongst hundreds or thousands of others.
Its easy to build and maintain access levels and perform other
system support.
Widely disbursed system with Hundreds of buildings such as
sub/relay stations or stores with few doors in each.
In this application there are many locations scattered
around the country or state. Each location may have just a few
doors. The emphasis is there are many locations and not so many
doors in each location. In this situation instead of having hundreds
or thousands of Locations we would deploy PC Master. PC Master would
communicate with up to 63 different buildings and keep them all
under one location. So there could be a separate PC Master for each
region, district, county or state. All controllers in that area
would all operate under one location through its respective PC
Master. This keeps the system processing requirements distributed
but organized.