|
<< Click to Display Table of Contents >> Setting Up SiteMaster |
  
|
|
<< Click to Display Table of Contents >> Setting Up SiteMaster |
|
SiteMaster may be installed on a single stand-alone computer, or set up to work with multiple computers running concurrently across a network. You need to decide what method works best for you. In this topic, we touch upon some different set up strategies and provide the Pros and some possible Precautions to consider.
End Users
Pros:
| • | All transactions are accomplished locally by one or more users sharing the same computer. |
| • | Personnel are issued keys and/or Key Rings centrally by the SiteMaster user(s). |
| • | Good for smaller sites that do not require a large amount of data entry and maintenance. |
Precautions:
| • | Do the various responsibilities of the SiteMaster user(s) provide enough time for quality data entry? |
| • | Is your IT Group aware of SiteMaster, and how is SiteMaster data and the PC being maintained? |
| • | Who fills in for the user when away or when no longer employed by your site? |
| • | If keys are delivered to locations for personnel, the recorded transactions may not be reliable. |
| • | If keys are delivered to personnel, are there recorded key issuance transactions? |
Property Managers
Pros:
| • | Update and maintain the data for multiple properties. |
| • | Maintain a separate dataset for each individual property or tenant, or maintain all property data in one dataset. |
| • | Provide your properties with hard copy printouts. |
| • | Provide your sites with data export files that are imported by your properties that also own SiteMaster. |
| • | Issue keys centrally to tenants, for pick up or delivery. |
| • | By having additional SiteMaster software at the properties, keys can be issued locally at those properties. |
Precautions:
| • | Are there others, who can access your PC and customer data if necessary? |
| • | Is your PC well maintained and can you set up a way to properly back up customer data? |
| • | May be difficult to account for key issuances if keys are simply delivered. |
| • | Don't use multiple datasets for properties where Key Systems cross or where Personnel require keys across properties. |
| • | Export files do not include Personnel, Departments, or Assets, so just building and key information. |
End Users
Additional Pros:
| • | Locksmiths can use their own computers to work on data entry simultaneously. |
| • | Data entry tasks can be shared by various users at different locations. |
| • | Specific tasks can be performed by specific users. |
| • | User rights to SiteMaster can be set up to control users' access to screens and objects. |
| • | Provides department or building users' access to the information about their own personnel's key issuances and building information. |
| • | Keys can be delivered to locations where those keys may be issued to personnel from those locations. |
| • | Your data is maintained and backed up by your IT Group. |
| • | Other users can help with data entry when the regular user is away. |
| • | Department or building users can manage the Assets in Rooms. |
Precautions:
| • | Networks and multiple users may slow down the reaction time of the Program. |
| • | Networks may be susceptible to disconnects and increases in traffic. |
| • | Make sure that you understand your IT Group's policies for data backups and maintenance. |
| • | The various users must keep secure any SiteMaster data, so log off for example, when not using SiteMaster. |
Property Managers
Additional Pros:
| • | Multiple SiteMaster users in your company can work on the same data or use multiple datasets. |
| • | Your users can be given different rights to the same or different datasets in order to perform different tasks. |
| • | Backup users can be added temporarily to work on customer data while you're away. |
| • | If your network extends to your properties, there's no need to perform data exports and imports. |
| • | All of the data is maintained and backed up on the server. |
Precautions:
| • | Networks and multiple users may slow down the reaction time of the Program. |
| • | Networks may be susceptible to disconnects and increases in traffic. |
| • | Make sure that you can properly maintain and backup the data. |
| • | Your various users must keep secure any SiteMaster data, so log off for example, when not using SiteMaster. |
Some Setup Examples for a Network
1. SiteMaster installed on a single PC with dataset on network share - This may be an improvement over just stand-alone, as the data is maintained and backed up on server.
2. Install SiteMaster on a Tablet(s) - Besides a PC, this would allow users to take SiteMaster directly to the doors using your wireless network.
3. Set up Department or Building Users - Users can be set up to only access data pertaining to their department(s) and/or building(s). For example, these users can only look up key issuance and building information that's limited to their rooms and personnel.
4. Provide access as needed to other related Users - For example, Security personnel can access specific data for risk assessment. Your Authority Having Jurisdiction for Fire Door compliance, can add, edit, and/or look up door information for fire inspection status and repair. A department user can manage and maintain any Assets located in that department's rooms.
5. Building Management can provide Tenants quality Key Control - Depending upon your network, your service personnel can maintain the key and door hardware data, while building staff issue keys to tenants in the buildings you manage.
6. When using a Single or Multiple Datasets - If your Key Systems and/or Personnel cross multiple buildings, such as locations or properties, then you don't want to use multiple datasets. However, if Key System and Personnel data is unique to those locations or properties, then you may want to set up separate datasets. This allows you to manage and maintain these sites independently.